Article ID: 821144 - View products that this article applies to.
Applications that are written to use Microsoft Message Queuing may stop responding (hang) because of a deadlock. There are no event errors, no error messages, or any other evidence that helps identify the problem.
A deadlock situation may occur in Mqsec.dll. This problem occurs because Mqsec.dll makes indirect remote procedure calls (RPCs) in the DLLMain function. The deadlock occurs when several threads load Mqsec.dll at the same time.
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:
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.
PrerequisitesNo prerequisites are required.
Restart RequirementYou must restart your computer after you apply this hotfix
Hotfix Replacement InformationThis hotfix supersedes all previous Message Queuing fixes.
File InformationThe 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 ------------------------------------------------------------------ 13-May-2003 22:29 188.8.131.52 988,712 Q821144_w2k_sp5_x86_en.exe 13-May-2003 19:59 184.108.40.2066 281,360 Mq1repl.dll 04-Feb-2003 15:51 220.127.116.116 14,096 Mq1sync.exe 26-Mar-2003 16:27 18.104.22.1684 75,536 Mqac.sys 13-May-2003 19:59 22.214.171.1243 217,360 Mqads.dll 30-Oct-2002 16:43 126.96.36.1991 25,360 Mqbkup.exe 13-May-2003 19:59 188.8.131.520 76,560 Mqdscli.dll 13-May-2003 19:59 184.108.40.2063 42,256 Mqdssrv.dll 21-Oct-2002 20:31 220.127.116.119 98,064 Mqmig.exe 13-May-2003 19:59 18.104.22.1689 265,488 Mqmigrat.dll 13-May-2003 19:59 22.214.171.1240 222,480 Mqoa.dll 13-May-2003 19:59 126.96.36.1992 8,464 Mqperf.dll 13-May-2003 19:59 188.8.131.526 428,304 Mqqm.dll 13-May-2003 19:59 184.108.40.2066 102,672 Mqrt.dll 13-May-2003 19:59 220.127.116.116 70,928 Mqsec.dll 13-May-2003 19:59 18.104.22.1689 400,656 Mqsnap.dll 13-May-2003 19:59 22.214.171.1242 23,824 Mqupgrd.dll 13-May-2003 19:59 126.96.36.1997 110,352 Mqutil.dll 13-May-2003 19:59 188.8.131.528 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.
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/EN-US/ )New Naming Schema for Microsoft Windows Hotfix Packages