FIX: Blue screen error message occurs on local computer when you try to purge journal queue on a remote computer (307928)
The information in this article applies to:
- Microsoft Message Queuing 2.0
This article was previously published under Q307928 SYMPTOMS
When you try to purge the journal queue on a remote computer, you may receive an error message on a blue screen on your local computer.
CAUSE
This behavior occurs when the Queue Manager does not identify this action as a remote read and tries to associate a local journal queue driver object for the remote journal. Because this object does not exist, the Queue Manager gains access to a section of memory that is not valid, which causes the error.
RESOLUTIONTo resolve this problem, obtain the latest service pack for 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
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
---------------------------------------------------
17-Dec-2001 15:16 5.0.0.742 71,184 Mqac.sys
17-Dec-2001 15:58 5.0.0.735 214,288 Mqads.dll
17-Dec-2001 15:58 5.0.0.735 41,744 Mqdssrv.dll
17-Dec-2001 15:58 5.0.0.740 222,480 Mqoa.dll
17-Dec-2001 15:58 5.0.0.742 418,576 Mqqm.dll
17-Dec-2001 15:58 5.0.0.742 91,920 Mqrt.dll
17-Dec-2001 15:58 5.0.0.738 70,416 Mqsec.dll
17-Dec-2001 15:58 5.0.0.738 108,304 Mqutil.dll
WORKAROUND
To work around the problem, use the following sample code in your application:
MQOpenQueue(lpszwFormatName, MQ_RECEIVE, MQ_DENY_NONE, &hQueue);
MQPurgeQueue(hQueue);
STATUSMicrosoft 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 Windows 2000 Service Pack 3.
Modification Type: | Major | Last Reviewed: | 4/21/2005 |
---|
Keywords: | kbbug kbfix kbWin2000sp3fix KB307928 |
---|
|