PRB: "Failed to Start Monitoring Directory Changes" Error Message When You Browse to ASP.NET Page (316721)
The information in this article applies to:
- Microsoft ASP.NET (included with the .NET Framework 1.1)
- Microsoft ASP.NET (included with the .NET Framework) 1.0
This article was previously published under Q316721 SYMPTOMS When you browse to an ASP.NET (.aspx) page, you may receive
the following error message Access denied to
'C:\Inetpub\Wwwroot' directory. Failed to start monitoring directory changes.
with the stack trace: [HttpException (0x80004005): Access denied to 'C:\Inetpub\Wwwroot' directory. Failed to start monitoring directory changes.]
System.Web.NativeDirMonCompletion..ctor(String dir, Boolean watchSubtree,
Boolean renamesOnly, NativeFileChangeNotification callback)
System.Web.FileChangesMonitor.StartMonitoringDirectoryRenamesAndBinDirectory(String dir,
FileChangeEventHandler callback)
System.Web.HttpRuntime.StartMonitoringDirectoryRenamesAndBinDirectory()
System.Web.HttpRuntime.FirstRequestInit(HttpContext context)
[HttpException (0x80004005): ASP.NET Initialization Error]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context)
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
Alternatively, you may receive the following error
message Server cannot access application directory
'C:\Inetpub\Wwwroot\Virtual Directory Name\'. The
directory does not exist or is not accessible because of security settings.
with the stack trace: [HttpException (0x80004005): Server cannot access application directory 'C:\Inetpub\Wwwroot\Virtual Directory Name. The directory does not exist or is not accessible because of security settings.]
System.Web.HttpRuntime.EnsureAccessToApplicationDirectory()
System.Web.HttpRuntime.FirstRequestInit(HttpContext context)
[HttpException (0x80004005): ASP.NET Initialization Error]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context)
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) CAUSE
By design, in
Microsoft Windows 2000 and in Microsoft Windows XP, ASP.NET requires read,
execute, and list access for the ASPNET account (the Aspnet_wp.exe process
account) on the root Web site or on any virtual directory. Similarly,
in Microsoft Windows Server 2003, ASP.NET requires read, execute, and list access for the
NETWORK SERVICE account (the W3wp.exe process account) on the root Web site or
on any virtual directory. This is necessary so that
ASP.NET can access the content files and can monitor file changes.
RESOLUTION To add read, execute, and list access for the ASPNET
account on the root Web site or on any virtual directory, follow these steps:
- In Windows Explorer, browse to the folder that contains the
root Web site (which is C:\Inetpub\Wwwroot by default) or the virtual
directory.
- Right-click the folder, and then click
Properties.
- On the Security tab, click
Add.
- Type
ComputerName\ASPNET (for
example, on a computer named Webdev, type
Webdev\ASPNET), and then click
OK.
- Allow the following permissions for the ASPNET account:
- Read & Execute
- List Folder Contents
- Read
- Click OK to close the
Properties dialog box and to save the changes.
NOTE: You do not need to perform these steps if the Everyone group or
the Users group has read access to the root Web site or virtual directory.
REFERENCESFor additional information about ASP.NET security
issues on a domain controller, click the article number below to view the
article in the Microsoft Knowledge Base: 315158 PRB: ASP.NET Does Not Work with a Non-Administrator Domain Account on a Domain Controller
Modification Type: | Minor | Last Reviewed: | 7/8/2005 |
---|
Keywords: | kbConfig kbHttpRuntime kbprb kbSecurity kbWebForms KB316721 |
---|
|