FIX: "Failed to start monitoring directory changes" error message when you browse to an ASP.NET page (317955)

RESOLUTION

Use either of the following methods to resolve this problem.

Method 1

Make sure that all of the directory names in the hierarchy of that file path are less than nine characters long.

For example: Note If you rename the directories so that the length of each directory name is now fewer than nine characters, after you make the required changes in the configuration of the Web site in Microsoft Internet Information Services (IIS) to deal with the directory renaming, you have to restart IIS.

Method 2

Grant the required permissions on all of the directories in that hierarchy to the ASP.NET process account (ASPNET by default) or to the impersonated account (if impersonation is turned on). To do this, follow these steps:

1. In Windows Explorer, browse to the application folder or to the virtual directory that contains the content (for example, D:\MyWeb\Users\MainDirectory\MyApplication).
2. Right-click the folder, and then click Properties.
3. On the Security tab, click Add.
4. Type ComputerName\ASPNET (for example, on a computer that is named Webdev, type Webdev\ASPNET), and then click OK. If impersonation is turned on, you must also add the impersonated accounts.
5. Allow the following permissions for the ASPNET account (and for the impersonated accounts if impersonation is turned on):
   • Read & Execute
   • List Folder Contents
   • Read
   
   
6. Click OK to close the Properties dialog box and to save the changes.
7. Repeat steps 2 through 6 for all of the folders in the hierarchy of the path. For example:
   
   
   • D:\MyWeb\Users\MainDirectory
   • D:\MyWeb\Users
   • D:\MyWeb
   • D:\
   
   If you want to grant more restrictive permissions to these folders, follow these steps after you complete step 5:
   
   
   1. Click Advanced.
   2. On the Permissions tab, click the permission entry for the ASPNET account (or another impersonated account), and then click Edit.
   3. Click Clear All, and then click to select the Allow check box for the List Folder / Read Data permission.
   NOTE: The application virtual directory (for example, D:\MyWeb\Users\MainDirectory\MyApplication) must have at least the permissions that are specified in step 5.
8. Restart IIS.

Method 3

If your computer is running IIS 6.0, grant the required permissions on all the folders in that hierarchy to the Network Service account. To do this, follow these steps:

1. In Windows Explorer, locate the application folder or the virtual directory that contains the content (for example, D:\MyWeb\Users\MainDirectory\MyApplication).
2. Right-click the folder, and then click Properties.
3. On the Security tab, click Add.
4. Type ComputerName\NETWORK SERVICE (for example, on a computer that is named Webdev, type Webdev\NETWORK SERVICE), and then click OK. If impersonation is turned on, you must also add the impersonated accounts.
5. Allow the following permissions for the Network Service account (and for the impersonated accounts if impersonation is turned on):
   • Read & Execute
   • List Folder Contents
   • Read
   
   
6. Click OK to close the Properties dialog box and to save the changes.
7. Repeat steps 2 through 6 for all the folders in the hierarchy of the path. For example:
   • D:\MyWeb\Users\MainDirectory
   • D:\MyWeb\Users
   • D:\MyWeb
   • D:\
   If you want to grant more restrictive permissions to these folders, follow these steps after you complete step 5:
   1. Click Advanced.
   2. On the Permissions tab, click the permission entry for the Network Service account (or another impersonated account), and then click Edit.
   3. Click Clear All, and then click to select the Allow check box for the List Folder / Read Data permission.
   Note The application virtual directory (for example, D:\MyWeb\Users\MainDirectory\MyApplication) must have at least the permissions that are specified in step 5.
8. Restart IIS.

Note These steps are only valid for Web applications that are hosted in IIS 6.0.

[HttpException (0x80004005): Access denied to 'D:\MyWeb\Users\MainDirectory\MyApplication\' directory. Failed to start monitoring directory changes.]
   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)
					

[HttpException (0x80004005): Access denied to 'D:\MyWeb\Users\MainDirectory\MyApplication\SamplePage.aspx'. Failed to start monitoring file changes.]
   System.Web.FileChangesMonitor.StartMonitoringFile(String fileName, FileChangeEventHandler callback)
   System.Web.Caching.CacheDependency.Init(String[] filenames, String[] cachekeys, CacheDependency dependency, DateTime start)
   System.Web.Caching.CacheDependency..ctor(String filename, DateTime start)
   System.Web.Caching.CacheDependency..ctor(String filename)
   System.Web.Security.FileAuthorizationModule.OnEnter(Object source, EventArgs eventArgs)
   System.Web.SyncEventExecutionStep.Execute()
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)