ASP-Site Stopped Running??!!!

[JackD4ME]

Hi All,
I have an asp site that was working as of 3 weeks ago. I changed dev machines and have done no work on it as it was running fine. I checked to see if it was still going well and it will not run any asp's in the site. The error is responding:

"You have attempted to execute a CGI, ISAPI, or other executable program from a directory that does not allow programs to be executed."

I assumed this was because I had not setup the folder to be a virtual directory, so I did that. But it is still not able to open any of the pages. Does anyone have an insite on this?

Thanks,
Jack D.

 

[mwolf00]

It sounds like you need to change the setting in IIS to:

Execute Permission: Scripts And Executables


on the virtual directory tab of the properties dialog box...

 

[JackD4ME]

I have the 1)read 2)run scripts 3)execute permissions set for this folder. I am confused and still fairly new to asp. Is there something else I am missing?

Thanks,
Jack D.

 

[maxpower1]

1. In IIS, right click the web site that you currently have and go to home directory tab. IIS assumes all files reside in this directory unless you use path statements in the asp pages to point to different directories. Hence, MAKE SURE all the files are in there.

2.on the same tab(as suggested before), make sure Execute Permissions option is set to Scripts and Executable.

3. Stop the web service. Restart IIS if necessary by right clicking on the machine name in IIS -> All Tasks -> Restart IIS. Then restart the web service.

4. To test, on the same machine point to the file.

5. if still does not work, on the Document tab (you get to it as step 1 but choose Document tab instead), try and add the default web page for the application.

Good luck,
max p.

 

[JackD4ME]

I have 3 subdirectories in the main folder. I added the execute option to the 3 folders so they now have read, run scripts, and execute permissions but the site still does not run. Do I need to remove the subdir. and put all pages into one folder?

Jack D.

 

[maxpower1]

If the asp pages in the first folder has code like
Response.redirect("\secondfolder\main.asp"
then it would be useless to put all the files in one folder.

Check this excerpt (I read from this site

http://www.windowswebsolutions.com/Articles/Print.cfm?ArticleID=16224)

Application mappings. If you don't understand the difference between the ways that IIS 5.0 and IIS 4.0 handle application mappings, you can create problems for your server. IIS uses application mappings to map file extensions to executables. For example, application mappings direct ASP files to asp.dll. You can add mappings to let IIS use almost any kind of scripting, such as Perl, Rexx, or PHP.

To access the App Mappings tab in IIS 5.0 or IIS 4.0, select the Default Web Site Properties' Home Directory tab. Click Configuration, and in the resulting dialog box, click App Mappings. You can also reach App Mappings through a virtual directory set up as an application.

Figure 2 shows the IIS 5.0 App Mappings tab, and Figure 3 shows the IIS 4.0 version. The labels on the rightmost columns in Figure 2 and Figure 3 show the big difference between IIS 5.0 and IIS 4.0. The IIS 5.0 label is Verbs, and the IIS 4.0 label is Exclusions. By default, IIS 5.0 disallows new verbs in the HTTP specification. When you map applications to executables, you need to specify which HTTP verbs the system allows. IIS 4.0 is the opposite, allowing new verbs by default. You need to specify which verbs the system disallows, or excludes.

If you ignore the App Mappings column headings and specify exclusive verbs such as DELETE and PUT instead of inclusive verbs such as GET and POST, the server will return the error message 403.1 ­ Execute Access Forbidden, with additional misinformation: You have attempted to execute a CGI, ISAPI or other executable program from a directory that does not allow programs to be executed. If you believe the error message, you'll never track down the problem. Auditing won't help you identify it, and neither will Filemon (a file-monitoring program available at

http://www.sysinternals.com)

or other troubleshooting techniques that search for executable NTFS permissions. Giving the Everyone group full control of the target files also won't solve the problem.