Geek Answers Handbook

IIS 403.1 HTTP Error - Forbidden: Call Access Denied

I have an ASP.NET 1.1 application running on IIS 6 / Windows Server 2003. This is our application, but we are trying to specifically replicate the client installation so that the application folder is completely copied from the production server to our test computer, and then we created a virtual directory and Manual web application for IIS.

IIS Manager:

  • Application pools
  • Web sites
    • Default website
      • xxxxx (virtual directory)
        • yyyyy (web application)
  • Web Services Extensions

The problem is that when accessing the application, we get a standard IIS security error message:

The page cannot be displayed You have attempted to execute a CGI, ISAPI, or other executable program from a directory that does not allow programs to be executed. -------------------------------------------------------------------------------- Please try the following: •Contact the Web site administrator if you believe this directory should allow execute access. HTTP Error 403.1 - Forbidden: Execute access is denied. Internet Information Services (IIS)

Now this is pretty standard, unless I see nothing so simple.

I checked:

  • IIS user has read access to the directory
  • IIS User and Network Users Have Read / Write Access to the ASP.NET Temporary Files Folder
  • The virtual directory is configured to the correct version of ASP.NET
  • ASP.NET 1.1 Web Service Extension Enabled
  • The virtual directory has the correct mapping of file extensions and all verbs in the aspnet 1.1 dll
  • Virtual directory properties let you run scripts and executables
  • Anonymous access is enabled, and the username and password are correct.

What am I missing?

+7
iis
source share
2 answers

When you created the application in IIS, did you check the permission of the script? You need to enable the first two options to run any of this application, including the virtual directory you created.

Right click on the parent application> Home tab> Executive permissions set for scripting only ...

+13
source

You may also need to check the "Edit permissions ..." button on the right pane of the handler mapping settings for a specific application and enable "Run." This is what kept my colleagues and I for 3 hours with other fairly similar symptoms.

+1
source

More articles:


All Articles