| Previous | Next |
| DBG_APP_NOT_IDLE | RPC_NT_WRONG_KIND_OF_BINDING |
RPC_NT_INVALID_STRING_BINDING
RPC_NT_INVALID_STRING_BINDING is an NTSTATUS value used by the Windows RPC runtime. An RPC string binding is a textual representation of binding information: it can contain an object UUID, protocol sequence, network address, endpoint and options. This status is raised when that representation cannot be accepted as a binding description. RpcBindingFromStringBinding creates a handle locally and does not contact the server, so this result does not by itself show that the server is down.
It differs from RPC_NT_INVALID_BINDING, which concerns an already-created binding handle, and from RPC_NT_NO_ENDPOINT_FOUND, where a binding can be valid but endpoint resolution does not identify a usable endpoint.
The binding text is invalid before the RPC runtime can create a handle
- Record the exact string binding after removing any deployment-specific secrets. Check the protocol sequence, network address, endpoint delimiters and escape characters as separate fields.
- Use the documented compose/parse APIs instead of concatenating fields by hand, then compare the parsed fields with the client configuration.
- Do not treat this as proof of a network outage: correct the binding representation first and retry only after it converts to a binding handle.
References
- Microsoft: Binding handles
- Microsoft: RpcBindingFromStringBinding
- The Open Group: DCE 1.1 RPC specification
Looking for a different code? Search another status or error code.