Select the product you need help with
FIX: IsWorldReadable and MSMQ Window Handle LeaksArticle ID: 241771 This article was previously published under Q241771 On This PageSymptoms
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.
ResolutionWindows NT Server or Workstation 4.0To 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:
http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Windows NT Server 4.0, Terminal Server EditionTo 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 the Microsoft Knowledge Base:152734
(http://support.microsoft.com/kb/152734/EN-US/
)
How to Obtain the Latest Windows NT 4.0 Service Pack
StatusMicrosoft 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.
PropertiesArticle ID: 241771 - Last Review: June 12, 2013 - Revision: 5.0
|


Back to the top








