| Previous | Next |
| RPC_E_CONNECTION_TERMINATED | RPC_E_CLIENT_DIED |
RPC_E_SERVER_DIED
When a remote call is performed, a connection is established between the client and the server (usually using TCP/IP). The client sends information to the server identifying the method to call and its parameters. Then the client waits information about the results of the method execution from the server. If during the waiting period the connection to the server is lost (for example, for some reason the TCP/IP connection was broken), there is no information about the reason for the connection loss, nor about the stage of the method execution. The method could be either successfully executed or completed with an error. As result the RPC management code returns This result.
Diagnostic interpretation of RPC_E_SERVER_DIED
RPC_E_SERVER_DIED has the HRESULT value 0x80010007. AllStat records the condition as “The callee (server [not server application]) is not available and disappeared; all connections are invalid. The call may have executed.”.
Evidence to capture
- Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions this result or the server / died operation.
- Reproduce this result with the smallest valid input and note whether the result changes with identity, architecture, service state, or target object.
Retry and recovery
Retry this result only when the owning API documents a transient state or after the condition described as “The callee (server [not server application]) is not available and disappeared; all connections are invalid. ” has changed.
Official references
Diagnostic interpretation
This result has the HRESULT value 0x80010007. The call may have executed.”.
Looking for a different code? Search another status or error code.