File: Troubleshooting#
I see a filename error message when fetching data from File#
The following error messages indicate an issue with the filename configuration:
Filename has no extension: This occurs when the file being processed does not have a file extension.Incorrect Filename date match: This occurs when the date pattern specified in the datastream settings does not match any date found in the filename.
To resolve these issues, ensure that your files have a valid extension and that the Filename date match setting accurately reflects the date format within your filenames.
I see a decoding error message when fetching data from File#
An error message beginning with 'utf-8' codec can't decode or 'ascii' codec can't decode can appear for a number of reasons:
The encoding for your File datastream is defined incorrectly.
The datastream is set to parse an incorrect file type.
The source file contains characters with multiple encoding types.
The source file contains invalid or corrupted characters.
To resolve this issue, depending on the cause, you need to correct your datastream settings, ensure that the source file only contains characters with one encoding type, and remove any invalid or corrupted characters in the source file.
If this error persists after following these steps, please contact the Adverity Support team.
I see a character decoding error message when fetching data from File#
The Adverity cannot determine the character encoding error message appears when Adverity is not sure whether the automatically detected encoding is correct.
To resolve this issue, we recommend checking the automatically detected encoding, and changing the setting if it is incorrect. If it is correct, you do not need to take any further action.