Registering Multiple RPC Server Interfaces

 Last reviewed: September 29, 1995
Article ID: Q129975
The information in this article applies to:
  • Microsoft Win32 Software Development Kit (SDK) for Windows NT, version 3.5

When registering multiple server interfaces from multiple threads or from a single thread under the same process, the RpcServerListen() function should be called only once.

An application process may register two completely separate Remote Procedure Call (RPC) server interfaces from two separate threads or from a single thread. However, when doing so, the RpcServerListen() function should be called only once from any thread.

RPC APIs are called on a per process basis. From the perspective of RPC run times, a process can register multiple interfaces using one or more protocol sequences, but must call the RpcServerListen() function only once from any one thread. Calling the RpcServerListen() function more than once results in the run time generating an exception called RPC_S_ALREADY_LISTENING.

Additional reference words: 3.50
KBCategory: kbnetwork kbnetwork
KBSubcategory: NtwkRpc

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: September 29, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.