Legacy ASP site issue

Question

I'm dealing with an issue where there was a site setup, and the default.htm used an iframe which pointed to an ASP directory. It seems like the ASP directory isn't readable and not processed - is there anything special that needs to be done to the ASP directory like permissions-wise?

wwwroot/sitename
<iframe src="ASP/file.asp"></iframe>

wwwroot/sitename/ASP/file.asp exists, and several other asp files but they aren't getting referenced by the iframe.

Update: I'm getting a 404..

The page cannot be found

I think I have to create a virtual directory and name it ASP. I never use IIS though - does anyone know how this works? And would I need to restart IIS after creating the virtual directory?

Update #2: More info..

Execute permissions: Scripts Only 
Application name: asp
For Authentication Methods, "Integrated Windows authentication" is checked
Local Path: Read

Update #3: I can access asp/file.htm file fine. Can anyone provide code for a simple test I could do to see if its working properly ( I have no ASP/VBScript experience )..

one of the top of the pages contains <%@ LANGUAGE="VBSCRIPT"%>

Answer 1

When you create a virtual directory for an ASP site in IIS, you have to make sure it is allowed to execute scripts. What version of IIS are you using? In 5.0 and 6.0, there should be a checkbox Run Scripts (such as ASP). Make sure that's checked.

Answer 2

Try putting a test.html file in the root directory of the site and then try to open it through wwwroot/sitename/asp/test.html - .html files won't be processed by asp.dll and so should display if the site is setup correctly even if there is some kind of asp.dll problem.

If you can't see a html file then I guess you will need to configure the website in IIS (not sure if a virtual directory is necessary from the information given) - check the 'home' tab to see if the path to the application is correct first.

If you can see the html file then I'd guess that asp is not properly installed (but that is a guess).

Answer 3

Is this IIS6 by any chance? In IIS, under Web Sites there is a folder called Web Service Extensions. Make sure Active Server Pages are set to Allow and not Prohibited!