The information in this article applies to:
SYMPTOMSWindow 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. CAUSEThis occurs in GetCurrentUserSid because the Open (Thread/Process) Token call was not paired with a CloseHandle call. RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows NT 4.0. For additional information, please see the following article in the
Microsoft Knowledge Base: Q152734 How to Obtain the Latest Windows NT 4.0 Service PackThis problem has been corrected in Windows NT 4.0 SP6 with the addition of CloseHandle calls to match Open (Thread/Process) Token calls. STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed
at the beginning of this article. Additional query words: msmq window handle leak
Keywords : kbMSMQ kbMSMQ100 kbMSMQ100bug kbMSMQ100fix NT4SP6Fix kbDSupport |
Last Reviewed: October 28, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |