This article has been archived. It is offered "as is" and will no longer be updated.
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.
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:
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.
No prerequisites are required.
You must restart your computer after you apply this hotfix
Hotfix Replacement Information
This hotfix supersedes all previous Message Queuing fixes.
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.