> I have created an asp.net application and successfully installed it on 
two 
t> est servers - my development machine which is XP and a test bed server 
w> hich is .NET Server Beta 3.  When I installed it on the production 
m> achine - a 2k box with the .Net framwork installed it no longer runs.  
I 
r> eceive the following error message:
H> ttpException (0x80004005): Server cannot access application 
d> irectory '<directory here>'. The directory does not exist or is not 
a> ccessible because of security settings.]
 >   System.Web.HttpRuntime.EnsureAccessToApplicationDirectory() +72
 >   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +256

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

> 
T> he application is set up in as an IIS virtual directory.  The web 
server 
o> n the production machine is not configured to use the IUSER_machine 
name 
u> ser as the anonymous web user, however.  It is set to use another local 
u> ser on the machine.  I've tried giving that user all the permissions I 
c> an in the application directory.  Nothing works.  Any help would 
a> ppreciated.  Thank you in advance.

I encountered the same problem. The issue with my production machine was 
that Sharepoint Team Services was installed. Some how this messes up the 
loading of ASP.Net apps. The fixed described previously did not work for 
me. The owsadm.exe utility found in \Program
Files\Common Files\Microsoft Shared\Web Server Extensions\50\bin fixed my 
problem. Run it as follows with the fully qualified name of the ASPNET 
account:
owsadm -o roleusers -w / -c add -n browser -u <host_name>\ASPNET