Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Here's my situation - I've had an ASP.NET application running in production for a long time now (Framework 2.0) and recently migrated from one root directory to another by switching the app's home path in IIS. Everything is running just fine, except any classic .asp scripts. When you hit them with a browser, they start to download like a standard text file.

The application config has not been changed, just the root home directory. Also, I have other applications on the same machine that do allow .asp to execute within them.

Before answering, keep in mind: 1 - this was all working in my ASP.NET app before I changed the home directory 2 - classic ASP is enabled 3 - classic ASP pages run from other virtual directories, so the extension mapping seems fine

share|improve this question
1  
Which version of Windows and IIS? –  Massimo Sep 29 '09 at 13:15
add comment

3 Answers

up vote 2 down vote accepted

OK, after an AHA! moment, I found the problem. Maybe this will benefit someone else since I haven't seen this mentioned anywhere in all of my searches.

It looks like another developer added an HTTPHandler to the web.config that was responding to all requests.

This prevented the asp.dll from processing the request for .asp files. I'm still a bit stumped on why IIS is hitting the ASP.NET app before processing the ISAPI extension first.

share|improve this answer
    
Because ASP.NET actually is an ISAPI extension, so it probably had greater priority than the developer's one. –  Massimo Sep 29 '09 at 15:14
add comment

Check if classic ASP pages are enabled at the virtual directory level; having them enabled globally or at the web site level could just be not enough.

share|improve this answer
    
Active Server Pages are enabled globally, and .asp is mapped to the asp.dll under ISAPI extensions at the virtual directory level. –  jtalarico Sep 29 '09 at 13:40
add comment

Does it even try to execute the vbscript in your .asp source file or is it returning the contents of the file to your browser as text/plain? Maybe you are missing some include file or something?

share|improve this answer
    
No, it doesn't execute. Script contents are returned to the browser. –  jtalarico Sep 29 '09 at 13:36
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.