| Previous | Next |
| RPC_X_NO_MORE_ENTRIES | RPC_X_SS_CHAR_TRANS_SHORT_FILE |
RPC_X_SS_CHAR_TRANS_OPEN_FAIL
Legacy character conversion data is unavailable to the stub
RPC_X_SS_CHAR_TRANS_OPEN_FAIL comes from stub-support character translation, not from opening the application’s payload file. A generated or legacy DCE-compatible path attempted to load a translation-table file used when converting character data and could not open it.
Identify the table path and the account under which the client or server process runs. Check deployment packaging, working-directory assumptions, file ACLs, architecture-specific installation locations, and endpoint version. Do not replace the table with arbitrary bytes: the related short-file status shows that RPC also validates the table’s minimum structure.
What to inspect
- Trace the resolved translation-table path in the failing process.
- Verify the file is deployed with the component that generated or expects it.
- Check service-account read access and avoid current-directory-dependent paths.
References
- Microsoft: character-translation RPC statuses
- Microsoft: RPC character base types
- MS-RPCE: NDR and IDL terminology
Looking for a different code? Search another status or error code.