Home/ Questions/Q 7976073
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T08:49:20+00:00

Background: I support a classic ASP environment. I have a development setup locally on

  • 0

Background: I support a classic ASP environment. I have a development setup locally on my machine as part of that support. I am running IIS7.

To access my environment, I use “http://localhost:99999/” (port # faked for privacy purposes). I have not had a problem with this — until today.

I built an application that is intended to run in this environment. The app is ASP.NET v.4.0 (for sake of example, I’ll say it’s called “http://localhost:99999/DotNetApp/”). Of course, in order to run this, I had to set up my environment application pool to support it (which it now does).

Problem: after configuring this, I am now getting:

Server Error in ‘/’ Application.

Access is denied.
Description: An error occurred while accessing the resources required to serve this request. You might not have permission to view the requested resources.

Error message 401.3: You do not have permission to view this directory or page using the credentials you supplied (access denied due to Access Control Lists). Ask the Web server’s administrator to give you access to ‘[filepath]\SourceFiles’.

I did NOT get this before I set my IIS configuration. Why am I getting this now?

Note: this ONLY happens with “http://localhost:99999/”; this does NOT happen if I try “http://localhost:99999/default.asp” (the page comes up with no problem).

Anyone have any insight?

Thanks in advance . . .

Edit: Additional symptoms: I tried playing with the application pool settings. The problem goes away if I change the .NET Framework version to either 2.0.50727 or to “No Managed Code.” Changing it to 4.0.31319 breaks it. Of course, if I use any of the other two versions, my ASP.NET app won’t run.

Edit #2: This problem occurs on ALL links that go to a folder or directory (e.g. “http://localhost:99999/somefolder/”), not just the web root.

Edit #3: I have a workaround: set “http://localhost:99999/” and “http://localhost:99999/DotNetApp/” in separate application pools. The first runs in .NET 2.0, while the latter runs .NET 4.0. (I’ll post this as an answer once my 8 hour limit is up.) Probably not the best answer — I’d prefer something that isn’t as much of a kludge — but for the time being, it’ll get the job done. However, if anyone has a solution that enables me to run everything in the same app pool, by all means, post away!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You probably must specify “default.asp” as allowed in your “Default Document” settings in IIS7

    EDIT: Check if ASP has been installed: Control Panel -> Programs and features -> Windows Features -> Internet Information Services -> Www services ->Application Development Features-> ASP

    enter image description here

    EDIT Final solution: The IUSR account is missing from the folder the website is in.

    • 0