FIX: IsWorldReadable and MSMQ Window Handle Leaks

This article has been archived. It is offered "as is" and will no longer be updated.
Symptoms
Window handle leaks are seen when applications create queues with the option IsWorldReadable set to True. This only occurs with Windows NT computers. Security differences on Windows 95 and 98 do not support the creation of queues with IsWorldReadable set to True.
Cause
This occurs in GetCurrentUserSid because the Open (Thread/Process) Token call was not paired with a CloseHandle call.
Resolution

Windows NT Server or Workstation 4.0

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

Status
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition.

This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.
More information
This problem has been corrected in Windows NT 4.0 SP6 with the addition of CloseHandle calls to match Open (Thread/Process) Token calls.
msmq window handle leak
Properties

Article ID: 241771 - Last Review: 12/28/2014 20:52:05 - Revision: 6.0

  • kbnosurvey kbarchive kbbug kbfix kbmsmq100fix KB241771
Feedback