Article ID: 826820 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows Registry
When the Microsoft Message Queuing (also known as MSMQ) service is reading the security descriptor from the local queue storage (LQS) file in the Mqmq\storage\lqs directory, an access violation may occur. The following message may be logged in the event log when the service does not start:
Event Type: Error
The queue properties are stored in .ini files in the Msmq\storage\lqs directory. The queue properties are read from the queue files by using the GetPrivateProfileString function. The security descriptor can be hundreds of kilobytes (KB) long, but the GetPrivateProfileString function is limited to 64 KB.
Hotfix InformationA 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:
PrerequisitesNo prerequisites are required.
Restart RequirementYou must restart your computer after you apply this hotfix
File InformationThe English version of this hotfix 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 -------------------------------------------------------------- 14-Aug-2003 23:07 126.96.36.1998 281,360 Mq1repl.dll 17-Jun-2003 14:33 188.8.131.528 14,096 Mq1sync.exe 14-Aug-2003 16:02 184.108.40.2062 76,144 Mqac.sys 14-Aug-2003 23:07 220.127.116.112 217,360 Mqads.dll 30-Oct-2002 13:43 18.104.22.1681 25,360 Mqbkup.exe 14-Aug-2003 23:07 22.214.171.1248 76,560 Mqdscli.dll 14-Aug-2003 23:07 126.96.36.1993 42,256 Mqdssrv.dll 21-Oct-2002 17:31 188.8.131.529 98,064 Mqmig.exe 14-Aug-2003 23:07 184.108.40.2069 265,488 Mqmigrat.dll 14-Aug-2003 23:07 220.127.116.110 222,480 Mqoa.dll 14-Aug-2003 23:07 18.104.22.1682 8,464 Mqperf.dll 14-Aug-2003 23:07 22.214.171.1242 429,328 Mqqm.dll 14-Aug-2003 23:07 126.96.36.1998 102,672 Mqrt.dll 14-Aug-2003 23:07 188.8.131.526 70,928 Mqsec.dll 14-Aug-2003 23:07 184.108.40.2061 400,656 Mqsnap.dll 14-Aug-2003 23:07 220.127.116.112 23,824 Mqupgrd.dll 14-Aug-2003 23:07 18.104.22.1682 110,864 Mqutil.dll 14-Aug-2003 23:07 22.214.171.1248 64,784 Msmq.cpl
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
Message Queuing uses the GetPrivateProfileString function to read properties from the LQS files. This API is limited to 64 KB. Because the security descriptor of public queues can be tens and hundreds of kilobytes long, Message Queuing now uses the file API to read larger files. With this fix, the default setting is to use the file API for files that are longer than 4 KB. The following example changes the default setting from 4K to 64K. Follow these steps, and then quit Registry Editor:
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 Naming Schema for Microsoft Windows Hotfix Packages
Contact us for more help
Connect with Answer Desk for expert help.