Below is a list of common Importer errors. Click on an error to expand it and view instructions on troubleshooting and resolving it.

Importer-Failed: The import failed.

• The remote server returned an error: (500) Internal Server Error.
  This is typically an error from the external system / API elluminate is calling, and it is intermittent. Generally, if the import is run again, it will be successful. Always try rerunning the import; if it is successful, it confirms this is an intermittent error, and the issue can be closed with a note that rerunning it was successful.

• The underlying connection was closed: An unexpected error occurred on a send.
  This is typically an intermittent error from the external system / API we call. Generally, if the import is run again, it will be successful. Always try rerunning the import; if it is successful, it confirms this is an intermittent error, and the issue can be closed with a note that rerunning it was successful.

• The following domains have discrepancies, and the import task is not set to Integrate Upon Discrepancies.
  Typically, the Technical Services team member responsible for this account would investigate and determine how to proceed. However, for discrepancy errors in any domain import, a user can check the input domain for expected or unexpected metadata discrepancies. The Support team can check for the latest Prod metadata version in the Data Source details of the import definition. If found, and the latest metadata version is not selected, the team member can select the latest version and set it to Integrate Upon Discrepancies.   

• Error running SAS Program: ERROR: ()... for more information see 'ObservedDatasetsLog_xxxxxxxxxxxxxxx.log' file in eDrive.
  The remedy for this typically requires an SAS programmer's engagement. The Technical Services team member responsible for this account will know how to proceed.

• An import is already in progress.
  elluminate will not allow an import from the same import definition to occur if one is already in progress. This frequently happens when someone starts an import but forgets to select the 'integrate' step. This will cause an error for all subsequent import tasks until resolved. A user is generally unaware that this will be a problem. Go to the study in elluminate, check the import that is in progress. The import can be canceled, or the person who started the import can be contacted if the import was intentional.

• The remote server returned an error: (401) Unauthorized.
  A 401 Unauthorized error indicates that the stored credentials for the external system, API, FTP, S3, or similar, are invalid. If a task that once succeeded now fails or a recurring task, the password has likely expired under the client's policy. The Technical Services team should confirm and update the credentials with the client if needed.  

• Importer-Failed: The import failed. (followed by other text not mentioned above)
  This is another type of error that cannot be easily categorized. Typically, the Technical Services team member responsible for this account would have to figure out how to proceed.

Other Import Errors

• Uploading a zip file that contains a folder results in no files being imported or an error message being received.
  To import a zip file that includes a folder, create an import definition of the File type, and specify the folder to read from in the 'Zip File Folder' parameter. Only a single folder can be specified due to the possibility of duplicate file names across folders.

• The user has configured a Biostats Gateway Import with all required parameters. When the import is run, elluminate responds that the import has completed, but no domains / files are shown.
  This situation usually arises because the Rave user account configured for the Biostats gateway call can reach the study but lacks permission to view its domains. When the account's 'view scope' is empty, Rave returns no files, so elluminate reports a completed import with zero domains. Confirm that the Rave user can access the study and all associated domains.

• The user needs to configure a tab-delimited file for import.
  In the Import Definition Details window, type \t in the Delimiter field to use the tab character instead of the default comma.

• An Import using an FTP, S3, or Box Data Source Type returns no files or fewer files than expected.
  The problem is typically caused by the value specified in the 'Remote Files' parameter. This value can be a specific file name or a regex-type pattern using characters such as * or ?. However, when a pattern is used (for example, lab??????.xlsx), each pattern will return only a single file, the most recent file that matches the pattern. A comma-separated list of patterns can be specified in this field, but each pattern will still return only one file. Do not specify *.* or *.xlsx expecting all files or all Excel files to be retrieved, as the process does not function in that way.

• Publish Failed: Error during reload of '<any number of Analytics apps or scripts>'
  The remedy for this typically requires engagement by a QlikSense developer to interpret the error message or determine the cause. The remedy frequently involves changing a mapping. Typically the technical services team member responsible for this account would have to figure out how to proceed.