Overview
To view Import Errors in SIS Integration Administration, click here.
Import Error "Could not parse file" means that there is an issue in the SIS source data and/or CSV file that is causing the data extract to be invalid or skipped/missing from the SIS Import Job process, preventing any "fresh" data from importing into SS&E.
NOTE: This error message usually indicates data-related issues, for example a bad character or invalid format preventing the entire data extract file from being processed. New data will NOT import into SS&E on this data feed until the underlying issue is resolved.
- Upon finding this error message, the SIS Import Job is most likely running and completing successfully, and most likely the associated data stream is not displaying as out of date.
- In most cases, this error message indicates that the data extract is invalid and the system has not been able to import any new data on this data feed since it last imported successfully. This can most likely be figured out by checking when the import error started appearing.
Resolution
In most cases, viewing the error message details and downloading the most recent data extract on file from Admin > SIS Integration > Datafeeds will show exactly what's causing this error message.
The message displayed on the import error record found in Admin > SIS Integration > Import Errors will most likely explain why the data extract (Json file) is invalid.
For example:
- The data extract may have formatting errors or invalid characters that need to be resolved.
- Even if only one record cannot be parsed/is formatted incorrectly, this can make the entire data extract (json file) invalid.
- Data may be importing as null on a required field. To check this, open the data extract in Notepad++ and scroll through required fields looking for null. To view which fields are required on each data feed, click here.
To fix this error message, the SIS source data/Informer reports/csv files/data extract definitions must be reviewed so that the underlying issue is fixed at the source, where it first occurs.
- To make sure the issue is resolved and SIS data is importing successfully, we recommend monitoring the next few import cycles by verifying that the Import Error(s) stop displaying on the Import Errors menu.
- If there are still problems with the data not updating correctly, check the Connect Job (from the client server or Admin > Advanced> External Logging) and the SIS Import Job (from Admin > Advanced > Batch Processing) to make sure they are running and completing.
NOTE: It is important to fix the source data where the root cause of the issue first occurs so that the issue is permanently fixed. Fixing the problem(s) in the data extract on file will NOT fix the root cause and a new "invalid" data extract will be generated every time the SIS Import Job is scheduled to run and the import errors will reappear. Only when the issue is identified and resolved at the source will fresh data import into SS&E.