Article ID: 177446 - View products that this article applies to.
This article was previously published under Q177446
This article describes how to test Microsoft Remote Procedure Call (RPC) performance, and how to troubleshoot RPC error messages.
RPC is compatible with the Open Software Foundation (OSF) design and interoperable with other Data Communications Exchange (DCE) standards. RPCs are industry standard Interprocess Communication (IPC) mechanisms for client-server communications that are network independent and can work over a variety of network protocols. RPC uses IPC mechanisms to establish communications between the client and server to call program functions on a remote computer. The complex programs that use this level of service require that there be a connection, or level of throughput, to adequately deliver this functionality. For example, when you are using Microsoft Exchange Server, a connection is needed to reliably maintain the flow of data.
RPC Error MessagesWhen you use RPC, you may receive any of the following error messages, which may or may not be caused by slow network connectivity:
Troubleshooting RPC Performance and Error MessagesThere are many tools you can use to determine if an RPC error message is being caused by a slow network connection. If you receive an RPC error message, eliminate slow network connectivity as the possible cause. Use one or more of the following methods to isolate the problem.
Article ID: 177446 - Last Review: November 1, 2006 - Revision: 2.2