Error Code Lookup
AppProfileSafe uses structured error codes in the format APS-NNNN. Error codes appear in the application log, in GUI error dialogs, in CLI console output, and in event pipeline events (via the errorCode field). The format in log entries and exceptions is [APS-NNNN] Message – Detail.
License (APS-1000 – APS-1099)
| Code | Message | Resolution |
|---|---|---|
APS-1000 |
License file not found | Place License.json and AppProfileSafe.pem in the application folder or configure custom paths in settings.xml. See Installing a License. |
APS-1001 |
License has expired | Renew your license at the license portal. If within the 30-day grace period, all features remain available. |
APS-1002 |
License signature invalid | The license file may be corrupted or tampered with. Redownload from the license portal. Ensure both License.json and AppProfileSafe.pem are from the same distribution. |
APS-1003 |
Feature not covered by license | The requested operation requires a feature not included in your license tier. Contact sales to upgrade. |
Configuration (APS-1100 – APS-1199)
| Code | Message | Resolution |
|---|---|---|
APS-1100 |
Configuration file not found | Ensure settings.xml exists in the application folder. Reinstall if missing. |
APS-1101 |
Configuration does not match schema | Validate the XML file against the corresponding XSD schema. Common causes: typos in element names, invalid values, or missing required elements. |
Export (APS-2000 – APS-2099)
| Code | Message | Resolution |
|---|---|---|
APS-2000 |
Export target path not writable | Check NTFS and share permissions on the export folder. The service account needs write access. |
APS-2001 |
No app definitions selected for export | Specify at least one application with --apps (CLI) or select applications in the GUI. |
APS-2002 |
Registry export failed | The application could not read a registry key. Check that the key exists and the account has read permission. The detail message includes the specific key path. |
APS-2003 |
File copy failed during export | A file could not be read or copied. Check that the source file exists, is not locked by another process, and the account has read access. |
Import (APS-2100 – APS-2199)
| Code | Message | Resolution |
|---|---|---|
APS-2100 |
Import source not found | The manifest data folder or a referenced file does not exist at the expected location. Verify the manifest path and ensure the export data is complete. |
APS-2101 |
Manifest validation failed | The manifest XML does not conform to the Manifest XSD. Re-export or manually fix the manifest. |
APS-2102 |
Path mapping could not be applied | A mapping rule references a path that does not exist in the manifest or produces an invalid target path. |
APS-2103 |
Registry import failed | A registry key could not be written. Check that the account has write access to the target key and that the registry value type is supported. |
APS-2104 |
File copy failed during import | A file could not be written to the target path. Check permissions, disk space, and whether the file is locked. |
APS-2105 |
Import conflict detected | A target file or registry value already exists with a different value. Review the DryRun report to understand the conflict. |
Simulation & Preflight (APS-2200 – APS-2399)
| Code | Message | Resolution |
|---|---|---|
APS-2200 |
Dry run simulation failed | The read-only analysis could not complete. Check the application log for the underlying error (e.g. missing manifest, invalid registry XML). |
APS-2300 |
Insufficient disk space | The target drive has less than 0.5 GB free. Free up space or use a different drive. |
APS-2301 |
Insufficient permissions | The current account does not have administrator privileges. Run as administrator. |
Event Pipeline & Sinks (APS-3000 – APS-3299)
| Code | Message | Resolution |
|---|---|---|
APS-3000 |
Sink delivery timeout | The target endpoint did not respond in time. Check network connectivity and endpoint availability. See Event Pipeline Troubleshooting. |
APS-3001 |
Sink returned HTTP error | The endpoint returned a non-success HTTP status. The detail includes the status code. Check the endpoint configuration and authentication. |
APS-3002 |
Sink connection failed | TCP connection to the sink endpoint could not be established. Verify host, port, firewall, and DNS. |
APS-3003 |
Event moved to dead letter | An event exhausted all retry attempts and was moved to the dead-letter queue. Investigate the dead-letter entries in the diagnostics bundle. |
APS-3004 |
Queue file corrupt or unreadable | The NDJSON event queue file is damaged. Delete the corrupt queue file and restart. Queued events in the corrupt file will be lost. |
APS-3100 |
Webhook shared secret not configured | A webhook endpoint requires HMAC signing but no shared secret is set. Configure the secret in webhook.xml. |
APS-3200 |
SIEM connection failed | Cannot reach the SIEM endpoint. Verify host, port, protocol, and TLS settings in siem.xml. |
Network (APS-4000 – APS-4099)
| Code | Message | Resolution |
|---|---|---|
APS-4000 |
UNC authentication failed | Credentials were rejected by the file server. Verify username and password. See Network & UNC Troubleshooting. |
APS-4001 |
UNC path not reachable | The server or share cannot be accessed. Check DNS, network connectivity, and the SMB port (TCP 445). |