RPC Problem: Locator Loses Exported Bindings

 Last reviewed: March 24, 1997
Article ID: Q149560
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.5 and 3.51
  • Microsoft Windows NT Server versions 3.5 and 3.51

SUMMARY

When a Remote Procedure Call (RPC) server application starts, it exports its characteristics to a name-service provider. Microsoft Locator is the default name-service provider. In some cases, the Locator will lose the information about the first exported bindings.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Windows NT Workstation versions 3.5 and 3.51 Microsoft Windows NT Server versions 3.5 and 3.51. This problem was corrected in Windows NT Workstation or Server version 4.0.

Additional query words: prodnt RPCLOCATOR DCE Name Service
Keywords : kbbug3.50 kbbug3.51 kbnetwork ntnetserv NTSrvWkst
Version : 3.5 3.51
Platform : WinNT

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: March 24, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.