| Previous | Next |
| RPC_E_VERSION_MISMATCH | RPC_E_INVALID_EXTENSION |
RPC_E_INVALID_HEADER
RPC_E_INVALID_HEADER (0x80010111) is a very low-level RPC error. RPC is used by COM to make cross-thread and out-of-process calls. Nothing that code could do to cause this kind of error, other than thoroughly corrupting the process state. A misbehaving driver would be the likelier reason.
The proposed fixes: update Windows, uninstall Malwarebyte antivirus, disconnect all external hardware, e.g. printer, scanner, external hard drives.
Overview of an RFC Application
A traditional application is a single program running on a single computer system, where a procedure and its caller execute in the same address space. In contrast, the client-server model for distributed applications embodies a client program and a server program, usually running on different systems of a network. The client makes a request to the server, which is usually a continuously running daemon process, and the server sends a response back to the client.
The remote procedure call (RFC) mechanism is the simplest way to implement client-server applications, because it keeps the details of network communications out of your application code. The idea is that each side behaves, as much as possi ble, the way it would within a traditional application: the programmer on the client side issues a call, and the programmer on the server side writes a procedure to carry out the desired function. To convey the illusion that you are working in a single address space, some hidden code has to handle all the networking. Many related issues are also involved, such as converting data between formats for dif ferent systems, and detecting communication errors.
The server s RFC runtime library receives the remote procedure call and hands the client information to the server stub. The server stub invokes the remote proce dure in the server application.