PRB: Rpc Name Space Functions Are Not Thread Safe

 Last reviewed: June 2, 1997
Article ID: Q169439
The information in this article applies to:
  • Microsoft Win32 Software Development Kit (SDK)

SYMPTOMS

The RPC Name Service functions are not thread safe. If an application uses these functions in a multithreaded environment, you may see indeterminate results.

RESOLUTION

To avoid this problem, simply synchronize calls to the Rpc Name Service functions by either using a Critical Section or a Mutex.

STATUS

Microsoft is researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

This problem applies to the following Rpc functions:

RpcIfIdVectorFree RpcNsBindingExport RpcNsBindingImportBegin RpcNsBindingImportDone RpcNsBindingImportNext RpcNsBindingLookupBegin RpcNsBindingLookupDone RpcNsBindingLookupNext RpcNsBindingSelect RpcNsBindingUnexport RpcNsEntryExpandName RpcNsEntryObjectInqBegin RpcNsEntryObjectInqDone RpcNsEntryObjectInqNext RpcNsGroupDelete RpcNsGroupMbrAdd RpcNsGroupMbrInqBegin RpcNsGroupMbrInqDone RpcNsGroupMbrInqNext RpcNsGroupMbrRemove RpcNsMgmtBindingUnexport RpcNsMgmtEntryCreate RpcNsMgmtEntryDelete RpcNsMgmtEntryInqIfIds RpcNsMgmtHandleSetExpAge RpcNsMgmtInqExpAge RpcNsMgmtSetExpAge RpcNsProfileDelete RpcNsProfileEltAdd RpcNsProfileEltInqBegin RpcNsProfileEltInqDone RpcNsProfileEltInqNext RpcNsProfileEltRemove

Note that there is no problem with executing these functions simultaneously from separate processes.

Keywords : kbnetwork NtwkRPC
Platform : NT WINDOWS
Issue type : kbprb

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