Microsoft Knowledge Base Email Alertz

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

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 926378 - Last Review: February 7, 2007 - Revision: 1.2

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

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  (http://kbalertz.com/Feedback.aspx?kbNumber=256986/ ) Description of the Microsoft Windows registry

SYMPTOMS

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.

CAUSE

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.

RESOLUTION

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:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Inetinfo\Parameters
  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:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ASP\Parameters
  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.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

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:
http://www.microsoft.com/downloads/details.aspx?FamilyID=80a1b6e6-829e-49b7-8c02-333d9c148e69&DisplayLang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=80a1b6e6-829e-49b7-8c02-333d9c148e69&DisplayLang=en)

APPLIES TO
  • Microsoft Internet Information Services 6.0
Keywords: 
kbtshoot kbprb KB926378
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate