| Previous | Next |
| RPC_NT_SS_CHAR_TRANS_OPEN_FAIL | RPC_NT_SS_IN_NULL_CONTEXT |
RPC_NT_SS_CHAR_TRANS_SHORT_FILE
RPC character-translation table is incomplete
RPC_NT_SS_CHAR_TRANS_SHORT_FILE is returned before normal call semantics matter: the generated RPC stub support code opened the translation table but found that the file is not large enough to contain the expected character-map data.
This is usually a packaging, deployment, or environment problem. Recreating the binding or changing the endpoint does not fix a table file that is truncated, substituted, or read through the wrong path.
What to check
- Check file size and content of the path named by
DCERPCCHARTRANS; a zero-byte or truncated file is enough to reproduce the failure. - Verify that the service account and the interactive account do not resolve the environment variable to different files.
- Replace the table from a known-good deployment rather than editing endpoint or authentication settings.
References
- Microsoft Open Specifications: MS-RPCE overview
- The Open Group: DCE 1.1 RPC protocol definitions
- Microsoft RPC: RPC return values
Looking for a different code? Search another status or error code.