Click here to Skip to main content
13,793,019 members
Click here to Skip to main content
Add your own
alternative version

Stats

64.6K views
2 bookmarked
Posted 4 Mar 2015
Licenced CPOL

Fix : HTTP Error 404.17 : The requested content...

, 4 Mar 2015
Rate this:
Please Sign up or sign in to vote.
Fix : HTTP Error 404.17 : The requested content appears to be script and will not be served by the static file handler

Introduction

You may got following error while browsing your ASP.NET website (in IIS 7/7.5/8/8.5), which reads, "HTTP Error 404.17 : The requested content appears to be script and will not be served by the static file handler"

see below error snap

Causes

 There are many causes behind this problem
1.  HTTP Handler configured to handle the request has certain preconditions set, but its Application pool does not meet some or all of these preconditions, in simple words Application pool's .NET framework is not set properly to the application in which it is compiled (If my application developed in 4.5 and I am attaching application pool with framework 2.0)

2. If application is migrated from IIS 6 then My Application pool should running in Classic Mode, with enable 32 bit mode options

3. Required .NET framework has restriction in 'ISAPI and CGI restrictions' in IIS

Resolution

Problem can be resolved by following steps
1. Open IIS manager (Go to start - Run - type 'INETMGR')

2. Select the Server Name (System Name)

3. Select ISAPI and CGI restrictions in right side pane

4. Allow the Not Allowed restrictions for required framework

see below snippet, to know how to allow ISAPI and CGI restrictions

 

5. If your required framework will not exist in ISAPI and CGI restrictions  then you need to re-registered framework with following command

6. Go to Start - Run put following command in Run window

C:\Windows\Microsoft.NET\Framework\v4.0.30319 \aspnet_regiis -i

 

see below snippet to know how to run command from Run window

run command here i have given example for .NET fremework 4.0, you cna use same command for any .NET framework

7. Set required .NET version in application pool

8. Enable 32-bit Application in application pool

9. Restart IIS

That's all, Now try to browse the same website, we have resolved the bug.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

koolprasadd
Software Developer (Senior)
India India
MCP,MCTS.
Microsoft MVP 2014 [ASP.NET/IIS]
Click here for more .NET Tips

You may also be interested in...

Pro
Pro

Comments and Discussions

 
Questionfor installing ASP.net 4.5 on windows server 2012 Pin
Member 45905793-May-17 5:08
memberMember 45905793-May-17 5:08 
QuestionMy vote of 1 Pin
supernorb29-Oct-15 21:23
membersupernorb29-Oct-15 21:23 
AnswerRe: My vote of 1 Pin
koolprasadd1-Nov-15 18:07
professionalkoolprasadd1-Nov-15 18:07 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Permalink | Advertise | Privacy | Cookies | Terms of Use | Mobile
Web01 | 2.8.181207.3 | Last Updated 4 Mar 2015
Article Copyright 2015 by koolprasadd
Everything else Copyright © CodeProject, 1999-2018
Layout: fixed | fluid