Hi Dave,
Welcome to ASPNET newsgroup.
From your description, the error you encountered is likely caused by the
asp.net application's physical path. Since ASP.NET application is a service
app which running in a non-interactive session, so it won't be able to
access those resources that are user specific. So for your scenario, I'd
suggest you move the application out of the "Document settings..." and
its sub dir, put them into a normal public location like:
d:\folders... or just beneath "inetpub\wwwroot...."
Also, to get the exact cause of the accessing problem, you can consider
using filemon to trace the file accessing during your application's startup.
Thanks,
Steven Cheng
Microsoft Online Support

Signature
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
--------------------
| From: "Dave" <davefrick@newsgroup.nospam>
| Subject: Virtual directory error: "directory does not exist or is not
accessible because of security settings"
| Date: Sun, 23 Oct 2005 01:55:18 -0700
| Lines: 40
[quoted text clipped - 8 lines]
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP14.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.dotnet.framework.aspnet:133305
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
|
[quoted text clipped - 30 lines]
|
| What do I need to do to set permissions for the virtual directory?