Error Reference: Import Errors¶
This page lists error messages from the data import services (TeasdaleImporter, NetworkFileImporter, ZflImporter).
Teasdale Importer Errors¶
"[TEASDALE-IMPORTER] Import directory does not exist: {path}"¶
- What it means: The folder configured for incoming job files does not exist.
- Common causes: 1. The path in appsettings.json is wrong. 2. The network share is not mounted. 3. The folder was deleted.
- Resolution: 1. Check
TeasdaleImportPathin appsettings.json. 2. Verify the path exists in File Explorer. 3. If it is a network share, check network connectivity and credentials.
"[TEASDALE-IMPORTER] File is empty: {filePath}"¶
- What it means: The JSON file was found but contains no data.
- Common causes: The DCOM system exported an empty file.
- Resolution: Contact the DCOM system administrator. The file must contain valid JSON with production data.
"[TEASDALE-IMPORTER] No valid production data found in file: {filePath}"¶
- What it means: The JSON file was read and parsed, but no usable production data was found inside.
- Common causes: 1. JSON structure does not match expected format. 2. Required fields (GTIN, LotNumber, etc.) are missing.
- Resolution: Contact the DCOM system administrator to check the export format.
"[TEASDALE-IMPORTER] Missing required field: GTIN"¶
- What it means: The imported JSON data does not contain a GTIN value.
- Common causes: The DCOM export is missing the GTIN field.
- Resolution: Contact the DCOM system administrator. GTIN is required for validation.
"[TEASDALE-IMPORTER] Missing required field: LotNumber"¶
- What it means: The imported JSON data does not contain a lot number.
- Common causes: The DCOM export is missing the lot number field.
- Resolution: Contact the DCOM system administrator. Lot number is required for validation.
"[TEASDALE-IMPORTER] Missing or invalid PackagingDate"¶
- What it means: The packaging date in the import file is missing or could not be parsed.
- Common causes: 1. Date field is empty. 2. Date is in an unexpected format.
- Resolution: Check the date value in the import file. Contact the DCOM system administrator if the format is wrong.
"[TEASDALE-IMPORTER] Invalid JSON format"¶
- What it means: The file could not be parsed as valid JSON.
- Common causes: 1. File is corrupted. 2. File is not JSON (wrong file type). 3. File was only partially written.
- Resolution: 1. Check the file content -- is it valid JSON? 2. Wait and check again (file may still be writing). 3. Contact the DCOM system administrator.
"[TEASDALE-IMPORTER] File locked or in use, will retry: {filePath}"¶
- What it means: The file could not be opened because another process is using it.
- Common causes: The DCOM system is still writing the file.
- Resolution: No action needed. The importer will automatically retry on the next poll interval (default 10 seconds).
"[TEASDALE-IMPORTER] Failed to connect to network share - file polling will likely fail"¶
- What it means: The application could not authenticate to the network share.
- Common causes: 1. Network credentials are wrong. 2. Password has expired. 3. Network share is down.
- Resolution: 1. Check
TeasdaleNetworkUsernameandTeasdaleNetworkPasswordin appsettings.json. 2. If using encrypted password (starts withENC:), the password may need to be re-encrypted. 3. Test the network share manually in File Explorer.
"[TEASDALE-IMPORTER] Ignoring duplicate JobId {jobId} (same as current job)"¶
- What it means: The same job file was imported again. The importer is skipping it because it is already loaded.
- Common causes: Normal behavior -- the file is still in the import folder and was detected again.
- Resolution: No action needed. This is expected.
"[TEASDALE-IMPORTER] Missing 'ilmd' section in JSON object"¶
- What it means: The JSON structure does not contain the required 'ilmd' section that holds production data.
- Common causes: The DCOM export format has changed or is incorrect.
- Resolution: Contact the DCOM system administrator.
- When to escalate: If the DCOM format is correct but GateKeeper cannot parse it.
"[TEASDALE-IMPORTER] Failed to create directories"¶
- What it means: The import or processed directories could not be created.
- Common causes: 1. Insufficient permissions. 2. Disk full. 3. Invalid path.
- Resolution: Check folder permissions and disk space.
"[TEASDALE-IMPORTER] ApplyPendingJob called but no pending job exists"¶
- What it means: An internal operation tried to advance to the next job, but the queue is empty.
- Common causes: This is usually a timing issue and can be ignored.
- Resolution: No action needed unless accompanied by other errors.
NetworkFileImporter Errors (CargillSalt)¶
"[NETWORK-FILE-IMPORTER] Directory does not exist: {path}"¶
- What it means: The configured import directory does not exist.
- Common causes: 1. Wrong path in appsettings.json. 2. Network drive not mapped.
- Resolution: Check
NetworkFileImportPathin appsettings.json.
"[NETWORK-FILE-IMPORTER] File has less than 2 lines, skipping: {filePath}"¶
- What it means: The import file needs at least a header row and one data row.
- Common causes: File is empty or contains only a header.
- Resolution: Check the file content and contact the data provider.
"[NETWORK-FILE-IMPORTER] GTIN column '{columnName}' not found in header. Available columns: {columns}"¶
- What it means: The column name configured for GTIN does not match any column in the file header.
- Common causes: 1. The file uses different column names than configured. 2. The configuration has a typo.
- Resolution: Compare the column names shown in the error (the "Available columns" list) to the configured column name. Update the configuration to match.
"[NETWORK-FILE-IMPORTER] Expiration column '{columnName}' not found in header. Available columns: {columns}"¶
- What it means: Same as above, but for the expiration date column.
- Resolution: Same as above.
"[NETWORK-FILE-IMPORTER] GTIN value is empty in column '{columnName}'"¶
- What it means: The GTIN column exists but the value is blank.
- Common causes: The data row has an empty GTIN field.
- Resolution: Check the file content. Contact the data provider.
"[NETWORK-FILE-IMPORTER] Invalid expiration date format (expected YYYYMMDD or MM/DD/YYYY): {date}"¶
- What it means: The date value in the file could not be parsed.
- Common causes: The date is in an unexpected format.
- Resolution: The importer accepts YYYYMMDD or MM/DD/YYYY. Check the date value in the file and ensure it matches one of these formats.
"[NETWORK-FILE-IMPORTER] File locked or in use, will retry on next interval: {filePath}"¶
- What it means: The file is currently being written by another process.
- Common causes: Normal -- the data source is still writing the file.
- Resolution: No action needed. Will retry automatically.