asked on

IIS 7.5 404.3 Error when using .asp pages with asp.net installed

Hello all,

I seem to be having an issue with serving asp pages on our new virtual (VMWare) server. It is running Windows Server 2008 R2, SQL Server 2008 R2, IIS 7.5. When ever we try to view an ASP page on the server we receive a 404.3 HTTP Error "The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the page should be downloaded, add a MIME map."

There are currently 4 handlers installed for ASP when looking at the server overview...
ASPClassic - *.asp - IsapiModule
PageHandlerFactory-Integrated - *.aspx - System.Web.UI.PageHandlerFactory
PageHandlerFactory-ISAPI-2.0 - *.aspx - IsapiModule
PageHandlerFactory-ISAPI-2.0-64 - *.aspx - IsapiModule

If I click on the virtual directory in IIS of the website that is experiencing issues I have these 2 handlers showing up as inherited...
PageHandlerFactory-ISAPI-2.0 - *.aspx - IsapiModule
PageHandlerFactory-ISAPI-2.0-64 - *.apsx - IsapiModule

I have tried uninstalling ASP.net and reinstalling it. I have tried manually registering the ASP client through the command prompt which says it is successful. I am out of ideas shorting of creating a new SQL/webserver which is not an option as this server is currently hosting our document management software.

If anyone can give me some more insight as to what might be happening it would be greatly appreciated.

Thank You,
jaeIT

pateljitu

Try this article please on EE:

https://www.experts-exchange.com/questions/27029683/Migrating-ASP-site-HTTP-Error-404-3.html

jaeIT

ASKER

pateljitu - Thanks for the reply. I have 3 items in the ISAPI and CGI Restrictions page.
Active Server Pages - Allowed - %windir%\system32\inetsrv\asp.dll
ASP.NET v2.0.50727 - Allowed - %windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll
ASP.NET v2.0.50727 - Allowed - %windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll

The only other thing this article mentions is something called Plesk Panel which I have never heard of and therefore can say we are not using.

Anything else I can check?

Thanks,
jaeIT

pateljitu

You can ignore Plesk details in that article, it was prior post that explained the ISAPI setting.

It looks like from your post ASP is installed just to make sure:

1. did you install ASP as steps explained in this article:
http://learn.iis.net/page.aspx/562/classic-asp-not-installed-by-default-on-iis-70-and-iis-75/

2. Could you provide with more details on 404.3 error, for e.g. in Detailed Error information on error page whats the Requested URL and Physical Path

3. IIS Handler Mapping can you print which executable is ASP mapped to.

jaeIT

ASKER

1. Yes

2. Requested URL: http://localhost:80/mc_web/Default.asp
Physical Path: D:\Maintenance Connection\mc_iis\Default.asp
Module: StaticFileModule
Notification: ExecuteRequestHandler
Handler: StaticFile
Error Code: 0x80070032

3. Server Level Handler Mapping...
ASPClassic - *.asp - %windir%\system32\inetsrv\asp.dll
PageHandlerFactory-Integrated - *.aspx - System.Web.UI.PageHandlerFactory
PageHandlerFactory-ISAPI-2.0 - *.aspx - %windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
PageHandlerFactory-ISAPI-2.0-64 - *.aspx - %windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll

Default Website Level...
PageHandlerFactory-Integrated - *.aspx - System.Web.UI.PageHandlerFactory
PageHandlerFactory-ISAPI-2.0 - *.aspx - %windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
PageHandlerFactory-ISAPI-2.0-64 - *.aspx - %windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll

Virtual Directory Level...
PageHandlerFactory-Integrated - *.aspx - System.Web.UI.PageHandlerFactory
PageHandlerFactory-ISAPI-2.0 - *.aspx - %windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
PageHandlerFactory-ISAPI-2.0-64 - *.aspx - %windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet_isapi.dll

As you can see only the server level Handler Mapping contains the ClassicASP Handler, but all 3 have the PageHandlerFactory versions. I have tried manually adding the ASPClassic Handler to the other ones with no change in error message.

Thanks,
jaeIT

ASKER CERTIFIED SOLUTION

pateljitu

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

jaeIT

ASKER

Thank You!! After I did that I was getting a new error 404.17 but I was able to clear that up by changing the handler bitness from bitness64 to bitness32.