Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
You receive an access violation error message when the administration APIs request queue state information in Message Queuing
Article ID: 841721 - View products that this article applies to.
When the administration APIs request queue state information in Microsoft Message Queuing, you receive an access violation error message.
This problem occurs because a race condition causes the information that is returned to be misinterpreted.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote 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.
File informationThe 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 ---------------------------------------------------------- 13-Jul-2004 09:50 22.214.171.1242 291,088 Mq1repl.dll 22-Dec-2003 14:26 126.96.36.1991 14,096 Mq1sync.exe 11-May-2004 07:34 188.8.131.524 76,944 Mqac.sys 13-Jul-2004 09:50 184.108.40.2061 217,360 Mqads.dll 20-Sep-2003 11:23 220.127.116.111 25,360 Mqbkup.exe 13-Jul-2004 09:50 18.104.22.1685 76,560 Mqdscli.dll 13-Jul-2004 09:50 22.214.171.1243 42,256 Mqdssrv.dll 22-Dec-2003 14:26 126.96.36.1991 98,064 Mqmig.exe 13-Jul-2004 09:50 188.8.131.521 266,512 Mqmigrat.dll 13-Jul-2004 09:50 184.108.40.2063 222,480 Mqoa.dll 13-Jul-2004 09:50 220.127.116.114 10,000 Mqperf.dll 13-Jul-2004 09:50 18.104.22.1687 437,520 Mqqm.dll 13-Jul-2004 09:50 22.214.171.1248 102,672 Mqrt.dll 13-Jul-2004 09:50 126.96.36.1996 70,928 Mqsec.dll 13-Jul-2004 09:50 188.8.131.523 400,656 Mqsnap.dll 13-Jul-2004 09:50 184.108.40.2062 23,824 Mqupgrd.dll 13-Jul-2004 09:50 220.127.116.113 110,864 Mqutil.dll 13-Jul-2004 09:50 18.104.22.1688 64,784 Msmq.cpl
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/816915/ )New file naming schema for Microsoft Windows software update packages