FIX: Cannot Compile Code-Behind Files That Use Src Attribute on a UNC Share

This article was previously published under Q313105
This article has been archived. It is offered "as is" and will no longer be updated.
When you compile a Web form, the compilation may fail in ASP.NET, and you may receive the following error message (or similar):
Compiler Error Message: CS2001: Source file
'\\server\sharename\webform1.aspx.cs' could not be found.
This error can occur if the following conditions are true:
  • The code-behind model is being used.
  • The page uses dynamic compilation with the Src attribute, and the Src attribute points to a file on a remote computer by using a Universal Naming Convention (UNC) share.
  • Impersonation is enabled in the Web.config file.
This problem occurs because the compiler is started with the identity of a worker process, and the worker process may not be able to read the remote share. Because ASP.NET uses the impersonation token to read the page, ASP.NET reads the page successfully.
To resolve this problem, use one of the following methods:
  • Give the share access to the account that is used for the worker process. If you are using a system account or a network service, you can give access to the computer account.

    To give access to the computer account, follow these steps:
    1. Right-click the share, and then click Properties.
    2. On the Sharing tab, click Permissions, and then click Add.
    3. Type the name of the Web server, and then click Check Names. This displays as $machinename under Share Permissions in the Permissions dialog box for this share.
  • Use code-behind files with precompiled dynamic-link libraries (DLLs) instead of dynamic compilation.
  • Use single page files rather than code-behind files.
  • Run the worker process as an account that can access the share. To configure this, use the user name and password attributes of the processModel element of the Machine.config file.
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in ASP.NET (included with the .NET Framework) 1.1 and the .NET Framework 1.1.

Steps to Reproduce Behavior

  1. Create an .aspx page named Webform1.aspx.
  2. Use one of the following examples for the page directive:
    <%@ Page language="c#"  Codebehind="WebForm1.aspx.cs"  Src = "WebForm1.aspx.cs" %>					
    <%@ Page language="vb"  Codebehind="WebForm1.aspx.vb"  Src = "WebForm1.aspx.vb" %>					
  3. Create a code-behind page, and name it according to the page directive that you chose in step 2.
  4. Add a domain user (domain\user) as an Administrator to the computer.
  5. Create a share, and then give full permissions to the domain user only.
  6. In Internet Service Manager, create a Microsoft Internet Information Server (IIS) application, and then use the domain\user for connect-as.
  7. Create a virtual directory in the application that points to the share that you created earlier.
  8. Move the WebForm1.aspx and the code-behind file to the share.
  9. Create a new Web.config file, and then add the following code:
    <?xml version="1.0" encoding="utf-8" ?><configuration>  <system.web>    <authentication mode="Windows" />    <identity impersonate="true" userName="domain\user" password="password" />  </system.web></configuration>					
  10. Copy the Web.config file into the virtual directory for the Web application to add the file to the IIS application.
  11. Browse to the page.
kbreadme codebehind

Article ID: 313105 - Last Review: 02/27/2014 21:10:52 - Revision: 2.3

Microsoft ASP.NET 1.0, Microsoft .NET Framework 1.0

  • kbnosurvey kbarchive kbfix kbbug kbconfig kbdeployment kbnofix kbreadme kbsecurity kbweb KB313105