Consider the following scenario. A Microsoft Active Server Pages (ASP) page is located in a virtual directory. The virtual directory is hosted on a server that is running Microsoft Internet Information Services (IIS) 6.0 or 5.0. When you try to view the ASP page, you receive an HTTP error message.
If the ASP page is hosted on a server that is running IIS 6.0 or 5.0, and if the Execute permissions are set to
Scripts and Executables for the virtual directory, you may receive an error message that resembles the following:
HTTP 404 - File not found
If the ASP page is hosted on a server that is running IIS 5.0, and if the Execute permissions are set to
Scripts only for the virtual directory, you may receive an error message that resembles the following:
HTTP 403.1 - Forbidden: Execute access forbidden
Note This issue does not occur when the ASP page is located in the root directory for the Web site.
This issue can occur if the name of the virtual directory contains ".com". For example, the issue occurs if the name of the virtual directory is "adatum.com" or "www.adatum.com."
This issue occurs because the ".com" part of the file name is recognized as the extension for an executable file. Therefore, IIS cannot correctly parse the name of the virtual directory.
To resolve this issue in IIS 6.0, create a new virtual directory whose name does not contain ".com."
To resolve this issue in IIS 5.0, rename the existing virtual directory. Make sure that the new directory name does not contain ".com."