Skip to content

Error Reference: Application Errors

This page lists error messages related to application startup, configuration, and general operation.

Startup Errors

"Framework not found" / ".NET not installed"

  • What it means: The .NET 8.0 Desktop Runtime is not installed on this machine.
  • Common causes: New machine or the runtime was removed.
  • Resolution: Download and install the .NET 8.0 Desktop Runtime from the Microsoft website.

"Could not load file or assembly"

  • What it means: A required DLL file is missing from the installation folder.
  • Common causes: 1. Incomplete extraction from conveyor.zip. 2. Files accidentally deleted.
  • Resolution: Re-extract all files from conveyor.zip to C:\gatekeeper\conveyor\. Do NOT overwrite appsettings.json when extracting.

"Access denied" / "UnauthorizedAccessException"

  • What it means: The application does not have sufficient permissions.
  • Common causes: 1. Not running as Administrator. 2. Folder permissions restrict access.
  • Resolution: Right-click the application and select "Run as Administrator."

Hardware Initialization Errors

"No hardware configurations found or all devices are disabled. Check appsettings.json HardwareSettings section."

  • What it means: The appsettings.json file has no enabled hardware devices configured.
  • Common causes: 1. HardwareSettings section is missing from appsettings.json. 2. All devices have IsEnabled: false. 3. appsettings.json was overwritten with a blank or development config.
  • Resolution: Check appsettings.json for the HardwareSettings array. Each device should have "IsEnabled": true. See Verify Configuration.

"All hardware devices failed to initialize. Check connection strings and network connectivity."

  • What it means: Hardware configurations exist but every device failed to connect.
  • Common causes: 1. Network is down. 2. All devices are powered off. 3. IP addresses are wrong.
  • Resolution: 1. Check network connectivity. 2. Verify all hardware is powered on. 3. Check connection strings in appsettings.json. See Hardware Disconnected.

"Failed to initialize hardware"

  • What it means: An unexpected error occurred during hardware initialization.
  • Common causes: Configuration error or missing SDK.
  • Resolution: Check the log for the full error details.
  • When to escalate: If the error is not a simple configuration or connectivity issue.

"Failed to connect camera {name} at {connectionString}. Check network connectivity and camera power."

  • What it means: A specific camera could not connect.
  • Resolution: Check the camera power, network cable, and IP address. See Connection Errors.

"Failed to connect RFID reader {name} at {connectionString}. Check network connectivity and reader power."

  • What it means: A specific RFID reader could not connect.
  • Resolution: Check the RFID reader power, network cable, and IP address.

"Failed to connect Arduino via {type} to {connectionString}."

  • What it means: The controller could not connect.
  • Resolution: For TCP: check Ethernet cable and IP. For Serial: check USB cable and COM port.

"Unknown hardware type: {type}"

  • What it means: The appsettings.json contains a device type that the application does not recognize.
  • Common causes: Typo in the DeviceType field.
  • Resolution: DeviceType must be one of: "Camera", "RfidReader", or "Arduino".
  • When to escalate: If the type is correct but not recognized.

Configuration Errors

"Failed to deserialize Arduino configuration" / "Error parsing Arduino configuration JSON"

  • What it means: The Configuration JSON string inside the HardwareSettings for the Arduino is not valid JSON.
  • Common causes: 1. Missing quotes or brackets in the Configuration field. 2. Unescaped characters.
  • Resolution: Validate the Configuration JSON string in appsettings.json. Remember that the Configuration value is a JSON string inside a JSON file, so backslashes and quotes must be properly escaped.

"Error applying camera configuration"

  • What it means: The camera Configuration JSON string could not be parsed.
  • Common causes: Invalid JSON in the Configuration field.
  • Resolution: Check the camera Configuration JSON in appsettings.json.

"[DS9908] Failed to parse configuration JSON, using defaults"

  • What it means: The DS9908 scanner Configuration JSON is malformed. The scanner will use default settings.
  • Common causes: Invalid JSON in the Configuration field.
  • Resolution: Fix the Configuration JSON or remove it to use defaults.

PIN and Security Errors

"Enter {PinLength} digits" / "Please enter exactly {PinLength} digits."

  • What it means: The PIN entered has too few digits. The PIN must be exactly 6 digits.
  • Resolution: Enter all 6 digits of the PIN.

"Incorrect PIN. Please try again."

  • What it means: The PIN entered does not match the stored PIN hash.
  • Common causes: 1. Wrong PIN entered. 2. Custom PIN was set and the user does not know it.
  • Resolution: 1. Try the default PIN: 867530. 2. If a custom PIN was set and is forgotten, edit appsettings.json and clear the SettingsPinHash value to "", then restart.

Runtime Errors

"Consecutive failure threshold reached: {count}/{threshold}"

  • What it means: The configured number of consecutive validation failures has been reached. The system may stop the conveyor automatically.
  • Common causes: A persistent validation issue is causing every case to fail.
  • Resolution: 1. Fix the underlying validation issue (see Validation Failing). 2. The counter resets on any passing validation or manual reset.

"Failed to save validation result for case {caseId}"

  • What it means: The validation result could not be saved to disk.
  • Common causes: 1. Disk full. 2. Folder permissions.
  • Resolution: Check available disk space and folder permissions for the data directory.

"{count} devices are offline"

  • What it means: One or more hardware devices have lost connection during operation.
  • Common causes: Network or USB disconnection.
  • Resolution: Check hardware connections. See Hardware Disconnected.