How to run classic ASP scripts under IIS 5.1 (WinXP Pro) alongside .NET & CF

asp-classiciisisapi-extension

I'm running into a problem setting up my development environment. I've been working on ColdFusion and .NET applications up until recently I haven't needed to touch IIS. Now, I have to set up a classic ASP application for some one-off work.

I added a virtual directory in IIS and pointed it at the actual codebase on my local machine. I then set the security to low (for ISAPI extensions, i.e. ASP) and allowed for script execution. For some reason though, if I hit any .asp page it says the page cannot be found. However, HTML and static files load up just fine.

EDIT: URLScan fix seems to have done it. Fired up the app in another browser (i.e. not IE6), and I'm getting better error reporting. Looks like we're missing some includes, but it is executing the scripts. Thanks!

Best Answer

You need to make sure that the "Active Server Pages" web service extension is set to an allowed status.

Check out: http://classicasp.aspfaq.com/general/why-does-iis-hang-and/or-stop-serving-asp-pages.html

Also, you should be aware that a virtual directory may affect the include file paths in the asp pages themselves. If the original asp application does not use a virtual directory, then your local copy shouldn't either.

Related Solutions

C# – IIS6 Running a ASP.NET Virtual Dir under a classic ASP Website

Make sure that the ASP.NET worker process account (ASPNET on IIS5, IIS_WPG local group on IIS6 and higher) also has read access to the parent classic ASP site. The ASP.NET runtime looks in parent sites for web.config's.

Equally of course, ensure it has read access to your virtual directory, though it looks like it is a permissions issue on the parent folder.

It does not seem anything to do with your virtual directory not being an application as you would get a different error: "It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS."

For more details see this MS KB article.

IIS Express and Classic ASP

OK we've had this and this is how I've found a solution.. In our case I think it was linked to parent paths but could have been session state too...

Browse to C:\Documents and Settings\$your user name$\My Documents\IISExpress\config

Open applicationHost.config

Find the <system.webServer> section

Change the <asp> section to the following… By default it only had the cache and empty limits bits but feel free to adjust any parameters you don't want.

<asp 
     enableParentPaths="true" 
     bufferingOn="true" 
     errorsToNTLog="true" 
     appAllowDebugging="true" 
     appAllowClientDebug="true" 
     scriptErrorSentToBrowser="true">

     <session allowSessionState="true" />
     <cache diskTemplateCacheDirectory="%TEMP%\iisexpress\ASP Compiled Templates" />
     <limits />
</asp>

Save and restart iis express.

Best Answer

Related Solutions

C# – IIS6 Running a ASP.NET Virtual Dir under a classic ASP Website

IIS Express and Classic ASP

Related Topic