"Steven Cheng[MSFT]" wrote:

> Hello Sriram,
>
> From your description, you have an ASP.NET (2.0?) application hosted on
> IIS6/win2003 std server. And the IIS virtual directory is pointing to a
> remote file share. However, when you try browsing or opening the
> applciation in VS 2005, you got the following error, correct?
>
> "Server cannot access application directory 'T:\InetPub\wwwroot\'. The
> directory does not exist or is not accessible because of security settings."
>
> Based on my experience, there are some possible things that can cause this
> error:
>
> ** the virtual directory is not existing or accessible, for example, you
> create a virtual dir pointing to a folder under a given user's user
> profile(document_settings\userxxx\xxxx). Here is a web thread describe on
> this:
>
> http://blog.danbartels.com/archive/2005/04/22/579.aspx
>
> ** the IIS process doesn't have sufficient permission to access the
> physical path of the virtual directory.
>
> According to your scenario, you can check the two cases, if the virtual
> directory is a well accessible UNC share, it is likely that the permission
> is not correctly configured for the virtual directory's UNC share.
>
> Generally, we should take care of the following things when hosting an
> ASP.NET 2.0 web application in IIS which point to a UNC share
>
> 1.The UNC share is well accessible by the server machine(where the ASP.NET
> application is hosted in IIS)
>
> 2. The UNC shared folder has two permission settings:
> ** the NTFS access permission
> ** the UNC share folder's access permission
>
> You need to make sure a certain account(generally domain account for remote
> machines scenario) have sufficient perssion to read/modify that UNC
> share(and have sufficient permission on NTFS setting)
>
> 3. In the remote server's IIS virtual directory, when you set the home
> directory to a UNC share, you can configure a "Connect As..." account for
> it. This account is used by IIS to access the remove UNC share. As
> mentioned in #2, you need to select an account(commonly a powerful domain
> account) which has sufficient permission on the UNC share.
>
> I've performed some tests in my local environment and ASP.NET 2.0 web
> app(from a remove UNC share on a xp box) can works well in VS 2005(through
> both IIS hosted or VS 2005 test server hosted cases). There is no
> additional configuration requirement except the above things I mentioned.
>
> Here are some IIS UNC share mapping related KB articles:
>
> http://support.microsoft.com/kb/280383/en-us
>
> http://support.microsoft.com/kb/257174/en-us
>
> Hope this helps you.
>
> Sincerely,
>
> Steven Cheng
>
> Microsoft MSDN Online Support Lead
>
>
>
> ==================================================
>
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
>
>
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
>
> ==================================================
>
>
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>