Microsoft KB Archive/894923

= The W3SVC service stops when the Exchange virtual server fails over to another node in Exchange Server 2003 Service Pack 1 =

Article ID: 894923

Article Last Modified on 10/30/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Service Pack 1

-





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



SYMPTOMS
If you are using Microsoft Exchange Server 2003 Service Pack 1 on a computer that is part of a server cluster, the W3SVC service stops when the Exchange virtual server fails over to another node. When the W3SVC service stops, this causes all Web sites that are running on the cluster node to stop.



CAUSE
This problem occurs because of a function call that is made when the Exchange virtual server group is moved to the other cluster node. This function call stops the W3SVC service itself instead of just stopping the instance that is associated with the Exchange virtual server.



Service pack information
To resolve this problem, obtain the latest service pack for Exchange Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

836993 How to obtain the latest service packs for Exchange Server 2003

Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
To install this hotfix, you must be running Exchange Server 2003 SP1.

For more information about where to obtain Exchange Server 2003 SP1, click the following article number to view the article in the Microsoft Knowledge Base:

836993 How to obtain the latest service packs for Exchange Server 2003

Restart requirement
You do not have to restart the computer after you apply this hotfix. However, you must manually shut down the Cluster service and all the dependent resources before you install this hotfix. For more information, see the &quot;Hotfix installation instructions&quot; section.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.   Date         Time   Version       Size     File name --  30-Mar-2005  10:12  6.5.7232.99   133,632  Exres.dll

Hotfix installation instructions
You must install this hotfix on each node of the server cluster. Additionally, you must add and configure the DoNotStopW3SVC registry entry to enable the hotfix. To install this hotfix, follow these steps.

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 the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.  Using the Cluster Administrator program, move the cluster group or groups from the cluster node where you want to install this hotfix. Stop the Cluster service on the cluster node. To do this:  Click Start, click Run, type cmd in the Open box, and then click OK. Type the following command, and then press ENTER:

net stop clussvc

 </li> Install the hotfix on the cluster node.</li> After you install the hotfix, you must add and configure the DoNotStopW3SVC registry entry to enable the hotfix. To do this, follow these steps:  Click Start, click Run, type regedit in the Open box, and then click OK.</li> Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Cluster

</li> On the Edit menu, point to New, and then click DWORD Value.</li> Type DoNotStopW3SVC as the entry name, and then press ENTER.</li> Right-click DoNotStopW3SVC, and then click Modify.</li> In the Value data box, type a value of 1 to enable the hotfix, and then click OK.

Note To return the node to its default behavior, type a value other than 1.</li> Quit Registry Editor.</li></ol> </li> Restart the W3SVC service. To do this, follow these steps:  Click Start, click Run, type cmd in the Open box, and then click OK.</li> Type the following commands, pressing ENTER after each command:

net stop w3svc

net start w3svc

</li></ol> </li> Restart the Cluster service. To do this, follow these steps:  <li>Click Start, click Run, type cmd in the Open box, and then click OK.</li> <li>Type the following command, and then press ENTER:

net start clussvc

</li></ol> </li> <li>Use the Cluster Administrator program to move the cluster group or groups back to the cluster node where you installed the hotfix.</li> <li>Stop the Cluster service on the second node.</li> <li>Repeat steps 2 through 6 on the second cluster node.</li></ol>

<div class="workaround_section">

WORKAROUND
To work around this problem, you can manually start the Web sites. To do this, follow these steps:
 * 1) Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
 * 2) Expand your server name, and then expand Web Sites.
 * 3) Right-click the Web site that you want to start, and then click Start.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section. This problem was first corrected in Exchange Server 2003 Service Pack 2.

<div class="moreinformation_section">

MORE INFORMATION
For more information about how to install Exchange hotfixes on a clustered server, click the following article number to view the article in the Microsoft Knowledge Base:

328839 How to apply Exchange service packs and hotfixes

For more information about the terminology that is used for software updates, click the following article numbers to view the articles in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

817903 New naming schema for Exchange Server software update packages

Additional query words: XADM

Keywords: kbqfe kbhotfixserver kbexchcluster kbexchange2003presp2fix kbfix kbbug KB894923

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.