Displaying a handler for Classic Asp.asp extension pages giving errors in IIS Integrated Pipe Line Mode

Question

Displaying a handler for Classic Asp.asp extension pages giving errors in IIS Integrated Pipe Line Mode

I am trying to run classic Asp pages in IIS 7 Integrated line mode . So I added the following Handler mapping to Web.Config.

add name="ASPClassic" 
path="*.asp" 
verb="GET,HEAD,POST" 
modules="IsapiModule" 
scriptProcessor="C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll" 
requireAccess="Script"
resourceType="Unspecified"

But, when the .asp pages are requested, the message Unacceptable server application appears , and a detailed application event log says that:

A request mapped to aspnet_isapi.dll was made in an application pool running in Integrated.NET mode. Aspnet_isapi.dll can only be used when working in Classic.NET mode. Please either specify preCondition = "ISAPImode" in the handler mapping so that it runs only in application pools running in Classic.NET mode or move the application to another application pool running in Classic.NET mode to use this handler mapping.

Where am I wrong?

+5

asp.net iis-7.5 asp-classic

Pyae phyo aung Mar 12 '13 at 8:30

source share

2 answers

Kev · Answer 1 · 2013-03-18T01:08:24+0000

The script processor for classic ASP is not:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll

and

%windir%\system32\inetsrv\asp.dll

Here is the correct record for displaying the handler from the IIS7 file applicationHost.configwhen installing Classic ASP:

<add name="ASPClassic" 
     path="*.asp" 
     verb="GET,HEAD,POST" 
     modules="IsapiModule" 
     scriptProcessor="%windir%\system32\inetsrv\asp.dll" 
     resourceType="File" />

It looks like you did not install Classic ASP on your server or workstation.

Windows 7 → , " Windows". , , , "ASP" :