FIX: RegConnectRegistry() Leaves Pipe Open

Last reviewed: October 29, 1997
Article ID: Q171261

The information in this article applies to:

Microsoft Win32 Application Programming Interface (API) included with: - Microsoft Windows NT versions 3.51, 4.0

SYMPTOMS

The Remote registry API, RegConnectRegistry(), allows a Win32 application to make registry API calls across the network. When an application calls this API, a named pipe connection between the two machines is created. Registry information is communicated between the machines through this named pipe connection. When the application is finished with the remote connection, it must call RegCloseKey() to close the registry handle.

A problem occurs when the named pipe connection, through which the registry information is communicated between the two machines, stayed open after RegCloseKey closed the connection handle.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug has been corrected in Windows NT 4.0, Service Pack 2.

Additional query words: nt5 winnt regapi
Keywords : BseRegistry kbprg
Version : 3.51 4.0
Platform : NT WINDOWS
Issue type : kbbug
Solution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.