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
RPC Error Messages
When you use RPC, you may receive any of the following error messages,
which may or may not be caused by slow network connectivity:
- The RPC protocol sequence is not supported.
- The RPC protocol sequence is invalid.
- The RPC server is already listening.
- The RPC server is not listening.
- The RPC server is unavailable.
- The RPC server is too busy to complete this operation.
- A remote procedure call (RPC) protocol error occurred.
- The transfer syntax is not supported by the RPC server.
- The RPC protocol sequence was not found.
- An internal error occurred in a remote procedure call (RPC).
- The RPC server attempted an integer division by zero.
- An addressing error occurred in the RPC server.
- A floating-point operation at the RPC server caused a division by zero.
- A floating-point underflow occurred at the RPC server.
- A floating-point overflow occurred at the RPC server.
- The list of RPC servers available for the binding of auto handles has been exhausted.
- The error specified is not a valid Windows RPC error code.
- Incompatible version of the RPC stub.
- The RPC pipe object is invalid or corrupted.
- An invalid operation was attempted on an RPC pipe object.
- Unsupported RPC pipe version.
- Invalid asynchronous RPC call handle for this operation.
- The RPC pipe object has already been closed.
- The RPC call completed before all pipes were processed.
- No more data is available from the RPC pipe.
Troubleshooting RPC Performance and Error Messages
There 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.