| Previous | Next |
| RPC_X_SS_CHAR_TRANS_OPEN_FAIL | RPC_X_SS_IN_NULL_CONTEXT |
RPC_X_SS_CHAR_TRANS_SHORT_FILE
The translation file opened but lacks the required table data
RPC_X_SS_CHAR_TRANS_SHORT_FILE is more specific than an open failure: the stub found the configured character-translation file, but its length is below the format’s required minimum. Microsoft’s RPC status definition identifies a file shorter than 512 bytes.
Compare the deployed file with the version shipped for the same generated interface and platform. A zero-length placeholder, truncated package extraction, text-mode transfer, or security product quarantine can preserve the filename while destroying its contents. Restoring the correct file is preferable to padding it, because the table values themselves define conversion behavior.
What to inspect
- Record file size, hash, package version, and resolved path.
- Compare against a known-good installation of the same RPC component.
- Replace the file atomically and investigate why deployment truncated it.
References
- Microsoft: RPC_X_SS_CHAR_TRANS_SHORT_FILE definition
- Microsoft: RPC character types
- Microsoft: handling RPC failures
Looking for a different code? Search another status or error code.