UnicodeDecodeError: 'utf-8' codec can't decode byte... #1464
-
|
Symptom: Validation interrupted due to UnicodeDecodeError |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
The If this sounds familiar and you have a TI.XPT, IE.XPT, or TS.XPT file, try excluding those files from your folder and rerun CORE. These characters might also appear in other XPT files, but TI.XPT, IE.XPT, and TS.XPT are usually the first ones we recommend isolating. After you isolated the offending files, it would be best to review this issue with your internal programming or IT resources. They will have the context needed to identify where the formatting is being altered during conversion and can implement the appropriate fixes. Reference: [2] Record Layout for a SAS Version 5 or 6 Data Set in SAS Transport Format: Encoding Guidelines for Reading a V5 Transport File. May 2025. SAS Documentation. Retrieved December 3, 2025, from https://documentation.sas.com/doc/en/pgmbasecdc/9.4/movefile/n0167z9rttw8dyn15z1qqe8eiwzf.htm |
Beta Was this translation helpful? Give feedback.
The
UnicodeDecodeErrorin the log points to a common issue we see with SAS V5 XPT files, especially when the XPT files are created by importing data from Microsoft Word or Excel. The problem often comes from smart quotes instead of straight quotes, em-dash instead of hyphen, or ellipsis instead of three consecutive dots.[1] The software cannot interpret those characters correctly.[2]If this sounds familiar and you have a TI.XPT, IE.XPT, or TS.XPT file, try excluding those files from your folder and rerun CORE. These characters might also appear in other XPT files, but TI.XPT, IE.XPT, and TS.XPT are usually the first ones we recommend isolating.
After you isolated the offending files, it …