Handle Leak Occurs When Using RasDial API

ID: Q197517

The information in this article applies to:

Microsoft Windows NT Workstation version 4.0
Microsoft Windows NT Server version 4.0

SYMPTOMS

A handle leak may occur while using the RasDial API. After the connection is closed using RasHangUp, you may notice that the handle count of the application does not return to the value before the RasDial call. This is more noticeable on applications that continually make connections using RasDial and then close them using RasHangup.

CAUSE

RasDial opens a handle to the process token and does not close it, which causes the handle count to increase every time RasDial is called.

RESOLUTION

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:

http://www.microsoft.com/Windows/ServicePacks/

Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack

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:

http://www.microsoft.com/support/supportnet/overview/overview.asp

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:

Q154871 Determining If You Are Eligible for No-Charge Technical Support

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5.

Additional query words: 4.00

Keywords : kbbug4.00 kbfix4.00 nt4sp5fix
Version : WinNT:4.0
Platform : winnt
Issue type : kbbug