Article ID: 323372
Article Last Modified on 2/22/2007
APPLIES TO
- Microsoft Message Queuing 2.0
This article was previously published under Q323372
SYMPTOMS
If the remote read connection is lost, Microsoft Message Queuing applications may receive errors that require you to restart the application and the local Message Queuing service to re-establish the connection. The following blue screen error may occur:
CAUSE
This behavior occurs because the remote procedure call (RPC) binding handle is shared among multiple remote read handles that are held by local applications on the client computer. When the Message Queuing service on the server that owns the queue is restarted, the RPC tries to re-establish the connection by using the old binding handle, which does not always work.
RESOLUTION
Service Pack Information
To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
Hotfix Information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Windows 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix has the file attributes (or later) 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
--------------------------------------------------------------
28-May-2002 20:37 5.0.0.746 279,824 Mq1repl.dll
22-May-2002 15:43 5.0.0.749 73,680 Mqac.sys
28-May-2002 20:37 5.0.0.746 215,312 Mqads.dll
28-May-2002 20:37 5.0.0.748 76,048 Mqdscli.dll
28-May-2002 20:37 5.0.0.735 41,744 Mqdssrv.dll
28-May-2002 20:37 5.0.0.746 264,976 Mqmigrat.dll
28-May-2002 20:37 5.0.0.740 222,480 Mqoa.dll
28-May-2002 20:37 5.0.0.748 8,976 Mqperf.dll
28-May-2002 20:37 5.0.0.749 417,552 Mqqm.dll
28-May-2002 20:37 5.0.0.748 92,944 Mqrt.dll
28-May-2002 20:37 5.0.0.746 70,416 Mqsec.dll
28-May-2002 20:37 5.0.0.748 109,840 Mqutil.dll
28-May-2002 20:37 5.0.0.748 64,784 Msmq.cpl
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
Additional query words: kbMSMQ MSMQ
Keywords: kbhotfixserver kbqfe kbwin2ksp4fix kbbug kbfix KB323372
