ASP.NET on IIS 6 security problem

[Leslie Costar]

I have a very simple ASP.NET app running on a newly installed Win 2K3 IIS
6 web server.

Everytime I try to run ASP.NET page, I get the following error

Server Error in '/' Application.
--------------------------------------------------------------------------
-----

Server cannot access application directory 'e:\domains\onlyonline\www\'.
The directory does not exist or is not accessible because of security
settings.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.Web.HttpException: Server cannot access
application directory 'e:\domains\onlyonline\www\'. The directory does not
exist or is not accessible because of security settings.

Source Error:

An unhandled exception was generated during the execution of the current
web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.

Stack Trace:


[HttpException (0x80004005): Server cannot access application directory
'e:\domains\onlyonline\www\'. The directory does not exist or is not
accessible because of security settings.]
System.Web.HttpRuntime.EnsureAccessToApplicationDirectory() +72
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +263

[HttpException (0x80004005): ASP.NET Initialization Error]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +964
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
+128

I have checked the www folder's permissions and IUSR had read/write and
ASPNET has read and execute on it. Impersonation is switched on in
machine.config.

Have I missed anything? The script would work fine in IIS 5/Win 2K.

Any help would be very much appreciated.

Thanks,

Leslie

 

[Guest]

Dear Leslie,

Go to the IIS Control Panel and check in the WebService extensions node.

By default ASP.Net would be prohibited. "Allow" It and then restart IIS.

It would work.

Hope it helps.

 

[Leslie Costar]

Dear Leslie,

Go to the IIS Control Panel and check in the WebService extensions node.

By default ASP.Net would be prohibited. "Allow" It and then restart
IIS.

It was already allowed. No difference.

I found the problem.

The machine is called SERVER6 and I added IWAM_SERVER6 with read
permissions to the www folder and that appeared to have fixed it, which is
what the IIS Application pool runs under.

Bizarre that this wasn't required in IIS 5.

Leslie Costar
ICUK Computing Services Limited
http://www.icuknet.co.uk
ADSL, Dial Up, Hosting