| Previous | Next |
| RPC_S_PROXY_ACCESS_DENIED | RPC_S_UNSUPPORTED_TYPE |
RPC_S_UNSUPPORTED_TRANS_SYN
Transfer syntax is the wire representation of RPC parameters
RPC_S_UNSUPPORTED_TRANS_SYN means the server cannot accept the transfer syntax negotiated for the RPC presentation context. Interface UUID and endpoint discovery may be correct, yet the bind still fails because client and server do not agree on how parameters are encoded.
In DCE/RPC, a presentation context associates an abstract interface syntax with a transfer syntax. Windows RPC commonly uses NDR, and MS-RPCE also documents transfer-syntax negotiation behavior. This status should therefore be investigated at bind negotiation, not as a generic application error.
What to inspect
- Capture the RPC bind and bind-ack or bind-nak exchange and compare the proposed transfer syntax UUID and version.
- Verify that client and server stubs were generated for compatible RPC/NDR capabilities and deployment architecture.
- When a custom or third-party DCE/RPC implementation is involved, confirm which transfer syntaxes it advertises and accepts.
Changing authentication or firewall rules will not add transfer-syntax support. The client must propose a syntax the server runtime and interface stubs can process.
References
Looking for a different code? Search another status or error code.