HTTP error 404.17 not found – Let’s fix it
Are you stuck with HTTP error 404.17 not found? We can help you fix it.
This error can occur due to different reasons. It includes an incorrect setting of the Application pool’s .NET framework, ISAPI and CGI Restrictions within IIS and so on.
At Bobcares, we often receive requests to fix HTTP errors as part of our Server Management Services.
Today, let’s analyze this error in detail and see how our Support Engineers fix it for our customers.
Causes for HTTP error 404.17 not found
Before getting deep into the error, let’s first see the root causes for HTTP 404.17 error.
1. Application pool’s .NET framework is not set properly
Usually, this error happens when the Application pool’s .NET framework is not set properly for the application in which it is compiled.
The .NET framework is a software development platform meant to create applications that would run on a Windows platform.
There are certain preconditions that are already set in the Application pool.
And, if these are not set properly there will be a mismatch within the frameworks of the Application Pools.
This lead to HTTP error 404.17.
2. Restriction in ‘ISAPI and CGI restrictions‘ within IIS
Another cause is that the required .NET framework has the restriction in ‘ISAPI and CGI restrictions‘ within IIS.
The ‘ISAPI and CGI restrictions‘ element allows ensuring that the malicious users cannot copy unauthorized CGI and ISAPI codes to the Web server and then run them.
And, if the restrictions are Not Allowed it leads to an error.
3. Change in Application Pool Settings
Similarly, when users try to migrate an application from IIS version 6, the Application Pool is set to run in Classic Mode with 32-bit mode options enabled.
And, if this option is not set correctly then it leads to HTTP 404.17 error.
How we fixed the HTTP error 404.17 not found?
Recently, one of our customers approached us with HTTP error 404.17.
HTTP Error 404.17 – Not Found. The requested content appears to be script and will not be served by the static file handler
Our Support Engineers had a precise look into the error.
We followed the below steps to resolve the error easily.
1. Firstly, we opened the IIS Manager.
2. Then, we selected the Server Name.
3. Next, we selected the ISAPI and CGI Restrictions option.
4. Then, we changed the Not Allowed restrictions for the required framework to Allowed.
5. Unfortunately, we couldn’t find the required framework in the ISAPI and CGI Restrictions. So, we re-registered the framework with the following command.
C:\Windows\Microsoft.NET\Framework\v4.0.30319 \aspnet_regiis.exe -i
To execute this command, we followed the below steps.
Go to Start -> Run -> and entered the above command in Run window.
We ran the above command for .NET framework 4.0.
We can also use the same command for any version of the .NET framework.
6. We then set the required .NET version in the application pool.
7. Then, we enabled a 32-bit Application in the application pool.
8. Finally, we restarted IIS.
Thus, it fixed the error and the ASP website started working efficiently.
[Need more assistance to fix ASP based errors? We are available 24/7]
In short, the HTTP error 404.17 not found occurs when the Application pool’s .NET framework is not set properly, restriction in ‘ISAPI and CGI restrictions‘ in IIS and so on. In today’s write up, we saw how our Support Engineers fixed the error for our customer.