This article has been archived. It is offered "as is" and will no longer be updated.
If you try to fail over a Message Queuing cluster node to another node on a computer that is running Microsoft Windows 2000, you may receive a stop error message on a blue screen. The bug check information is similar to the information in the following error message, but the addresses may vary:
Event Type: Error Event Source: MSMQ Cluster Resource DLL Event Category: None Event ID: 2017 Description: MSMQ service could not be stopped 0x3e5. Error 0x3e5 is ERROR_IO_PENDING.
The Message Queuing resource DLL waits five seconds for the Message Queuing service to stop and then waits five more seconds for the driver to unload. It then tells the cluster service that it is offline. However, it may not actually be offline because the Message Queuing service and the driver may require more time to stop and unload. For example, a long purge might require a longer time to stop the Message Queuing service and unload the driver.
Windows 2000 Update information
A resolution is available for computers that are running Windows 2000 Service Pack 3 or Windows 2000 Service Pack 4 as part of the security update that is documented in Microsoft security bulletin MS05-017. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
892944 MS05-017: Vulnerability in MSMQ could allow code execution
To view the security bulletin, visit the following Microsoft Web site:
A supported hotfix is 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 software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
No prerequisites are required.
You do not have to restart your computer after you apply this hotfix.
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 -------------------------------------------------------------- 04-May-2004 15:19 184.108.40.206 77,552 Windowsserver2003-kb824375-x86-enu-symbols.exe 04-May-2004 15:19 220.127.116.11 348,912 Windowsserver2003-kb824375-x86-enu.exe 04-May-2004 17:47 5.2.1725.170 76,288 Mqclus.dll 21-Apr-2004 16:35 271 Branches.inf 04-May-2004 17:55 9,766 Kb824375.cat 04-May-2004 17:50 354 Updatebr.inf 04-May-2004 17:50 6,540 Update_rtmqfe.inf
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New file naming schema for Microsoft Windows software update packages