Home > SQL and .NET Blog > HTTP errors in IIS 7.0

HTTP errors in IIS 7.0

Have you installed fresh IIS 7.0 into the server??

Yes, probably you could face this error at first time…

ERROR 1

HTTP Error 404.17 – Not Found

The requested content appears to be script and will not be served by the static file handler.

 

image

 

This is because ASP.net installation was not registered correctly. Try the following steps to register it.

run %windir%\Microsoft.NET\Framework\v4.0.21006\aspnet_regiis.exe –i

And the next possible error very often at first time is

ERROR 2

HTTP Error 404.17 – Not Found

The requested content appears to be script and will not be served by the static file handler.

 

image

This is because you have not enabled the permission for ISAPI and CGI restrictions

Just do the following steps and this will help

# Install the feature that handles this request. For example, if you get this error for an .ASPX page, you may have to install ASP.NET via IIS setup.
# Verify that the Web service extension requested is enabled on the server.

   1. Open the IIS Manager and navigate to the server level.
   2. In the Features view, double-click ISAPI and CGI Restrictions to verify that the Web service extension is set to Allowed.
   3. If the extension is not in the list, click Add in the Actions pane.
   4. In the Add ISAPI and CGI Restrictions dialog box, type the path of the .dll or .exe file in the ISAPI or CGI Path box, or click Browse to navigate to the location of the file.
   5. In the Description box, type a brief description of the restriction.
   6. (Optional) Check "Allow extension path to execute" to allow the restriction to run automatically. If you do not check this option, the restriction status is Not Allowed, which is the default. You can allow the restriction later by selecting it and clicking Allow on the Actions pane.
   7. Click OK.

 

Explore IIS with freedom..

-Yuva

http://Yuvahere.com

Advertisements
Categories: SQL and .NET Blog
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: