When you change the Global.asa file, an ASP Web application that is running on an IIS 6.0 Web server does not restart automatically

This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
Consider the following scenario:
  • You have an Active Server Pages (ASP) Web application on a Web server that is running Microsoft Internet Information Services (IIS) 6.0.
  • You locate the content for the ASP Web application on a remote Universal Naming Convention (UNC) share.
  • You set the AspEnableApplicationRestart property to true in the ASP Web application.
When you change the Global.asa file, the ASP Web application does not restart automatically. If you move the content of the ASP Web application to the local computer, the ASP Web application restarts automatically.
This problem occurs because the default settings for directory monitoring and for file change notification for UNC shares are not turned on in IIS 6.0.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, enable the directory monitoring and file change notification settings. To do this, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then right-click the following registry subkey:
  3. Point to New, and then click DWORD value.
  4. Type DoDirMonitoringForUNC as the name of the new registry entry.
  5. Double-click DoDirMonitoringForUNC, type 1 in the Value data box, and then click OK.
  6. Locate and then right-click the following registry subkey:
  7. Point to New, and then click DWORD value.
  8. Type EnableChangeNotificationForUNC as the name of the new registry entry.
  9. Double-click EnableChangeNotificationForUNC, type 1 in the Value data box, and then click OK.
  10. Exit Registry Editor.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about IIS settings, see the IIS 6.0 Resource Kit. To download the IIS 6.0 Resource Kit, visit the following Microsoft Web site:

Article ID: 926378 - Last Review: 12/09/2015 07:36:39 - Revision: 1.2

Microsoft Internet Information Services 6.0

  • kbnosurvey kbarchive kbtshoot kbprb KB926378
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)