Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium


Migrating .ASP site - HTTP Error 404.3

Posted on 2011-05-10
Medium Priority
Last Modified: 2012-05-11
Hi Everyone,

When migrating my .ASP site from IIS 6.0 > II 7.5 (I simply copied over all the folder contents, created the new site in IIS, pointed to the app pool and source files), I get the following error when loading the site).

HTTP Error 404.3 - Not Found
The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.

Most likely causes:
    - It is possible that a handler mapping is missing. By default, the static file handler processes all content.
    - The feature you are trying to use may not be installed.
    - The appropriate MIME map is not enabled for the Web site or application. (Warning: Do not create a MIME map for content that users should
      not download, such as .ASPX pages or .config files.)
    - If ASP.NET is not installed.

Any idea how I can fix this?  (I'm a sys admin, not a web dev guy).   Does the site need changing itself, or I can I set something on IIS?

Thanks in advance,

Question by:Theodosios
  • 3
  • 2
LVL 15

Expert Comment

ID: 35731961
Classic ASP is not installed by default on IIS 7.5, please follow the steps as provided in the link below.


Author Comment

ID: 35732004
It's installed, I selected all options for the IIS Role.


LVL 18

Accepted Solution

dj_alik earned 2000 total points
ID: 35732026
User Interface
Add ISAPI or CGI Restriction

 To use the UI 1.
Open IIS Manager and navigate to the level you want to configure. For information about opening IIS Manager, see Open IIS Manager (IIS 7). For information about navigating to locations in the UI, see Navigation in IIS Manager (IIS 7).

In Features View, double-click ISAPI and CGI Restrictions.

In the Actions pane, click Add.

In the Add ISAPI or CGI Restriction dialog box, type the path of the .dll or .exe file in the ISAPI or CGI path text box, or click the browse button (…) to navigate to the location of the file.

In the Description text box, type a brief description of the restriction.

Check Allow extension path of 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 in the Actions pane.

Click OK.

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why


Author Comment

ID: 35732117
Okay, thanks, I will try that.  But what .dll or .exe file am I browsing to in step 4?

LVL 15

Expert Comment

ID: 35732297
Under "ISAPI and CGI restrictions" what feature do you see.

Is Active Server Pages set to Allowed, if no add this path "%windir%\system32\inetsrv\asp.dll" andc heck "Allow extension path to execute.

Author Comment

ID: 35733280
Hi, I think the problem is resolved.  

We have Plesk Panel running on that web server.  Even though .NET, .ASP, and ISPI/CGI restrictions were set in IIS, it appears the settings in Plesk override everything for each site.  I changed them in Plesk, and the sites load fine now.



Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Possible fixes for Windows 7 and Windows Server 2008 updating problem. Solutions mentioned are from Microsoft themselves. I started a case with them from our Microsoft Silver Partner option to open a case and get direct support from Microsoft. If s…
For anyone that has accidentally used newSID with Server 2008 R2 (like I did) and hasn't been able to get the server running again because you were unlucky (as I was) and had no backups - I was able to get things working by doing a Registry Hive rec…
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

577 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question