This topic provides guidance for diagnosing and resolving common issues encountered when running Asset Backup Scheduler. For each problem area, the most likely causes are listed alongside recommended resolution steps.
Tip: Enable Debug Logging in Settings to capture detailed diagnostic log entries when troubleshooting. Log files are written to:
Application fails to launch or crashes immediately
.NET Framework 4.7.2 or later is not installed on the host
Install .NET Framework 4.7.2 or later from Microsoft and restart the host.
UAC prompt is declined and application does not open
Application requires elevated privileges to manage Windows services and access network shares
Accept the UAC elevation prompt. If UAC is disabled, ensure the application is run under a local administrator account.
Application opens but Settings are blank
First-run initialization — no settings have been saved yet
Complete the initial configuration in Settings as described in Getting Started.
SQL Server Connection Failures
Symptom
Likely Cause
Resolution
Test Connection returns: Server not found
Incorrect server name in the connection string, or the SQL Server host is offline or unreachable
Verify the server name or IP address. Confirm the SQL Server host is running and reachable from the Asset Backup Scheduler host (ping test). Check for firewall rules blocking port 1433.
Test Connection returns: Login failed
Incorrect username or password in the connection string, or the SQL Server account is locked
Re-enter the SQL Server credentials using the SQL Connection Builder. Confirm the account is not locked in SQL Server Management Studio.
Test Connection returns: Database not found
The database name in the connection string does not match an existing database on the SQL Server instance
Verify the database name. For CDA: ps_erdb; For SCADA: QBDB. Use SQL Server Management Studio to confirm the database exists.
Test Connection returns: Connection timed out
SQL Server is under heavy load, or the network route to the server has high latency
Check SQL Server performance. Consider increasing the connection timeout value in the connection string (Connect Timeout=60).
Backup Job Failures
Symptom
Likely Cause
Resolution
CDA Export job fails with executable not found
Honeywell PKS Engineering Tools are not installed, or are installed in a non-standard path
Confirm the Engineering Tools are installed at: %AppData%\Automation Software Technology, Inc\Engineering Tools\system\bin. Reinstall Engineering Tools if necessary.
CDA Export job fails with access denied
Insufficient privileges to execute the Engineering Tools process with elevation
Ensure Asset Backup Scheduler is running under a local administrator account. The batch process is launched with the runas verb and requires administrative rights.
SCADA Export job fails with cannot connect to SCADA database
SCADA SQL connection string is invalid or the QBDB database is unreachable
File copy jobs fail with access denied or path not found
Network share credentials are incorrect, the share path is wrong, or the share server is offline
Verify the Network Share Folder path and Domain/Username/Password credentials in Settings. Confirm the share is accessible using Windows Explorer from the host workstation.
Job marked as Canceled — timeout exceeded
The backup job took longer than the scheduled End Time window allows
Increase the End Time duration on the scheduled appointment in the Scheduler tab to provide a longer execution window. Large SCADA databases or slow network connections may require extended time windows.
All jobs show Not Started after scheduled time
Asset Backup Scheduler was not running at the scheduled time, or the schedule was not saved correctly
Verify that Asset Backup Scheduler is running continuously on the host. Open the Scheduler tab and confirm the appointment is visible and correctly configured. Consider setting the application to launch on system startup.
WatchDog Test Failures
Symptom
Likely Cause
Resolution
Step 1 fails — test file cannot be written
No write access to the network share
Verify network share credentials in Settings. Confirm write permissions on the share for the configured user account.
Step 2 fails — no Watchdog event received
Control Architect Backup File Monitor Service is not running, or the Control Architect Host API address is wrong
Check the Control Architect Backup Monitor Windows service status in Services (services.msc). Verify the Control Architect Host API Address in Settings. Confirm no firewall is blocking communication.
Step 3 fails — event validation mismatch
A stale or mismatched event was received, possibly from a previous run or another application instance
Restart the Control Architect Backup File Monitor Service and re-run the Watchdog Test. Ensure only one instance of Asset Backup Scheduler is running.
LCN Data Collection Issues
Symptom
Likely Cause
Resolution
LCN Data Collection tab is not visible
Enable LCN Backup is not checked in Settings
Enable the LCN Backup option in Settings to make the LCN Data Collection tab visible.
Data transfer fails — cannot connect to HM directory
PCN network path is incorrect, or the History Module is not accessible from the host
Verify the LCN Data Files Directory Path in the LCN Wizard. Confirm PCN network connectivity from the host workstation.
TPS File Transfer Service status shows Warning or Not Started
The Honeywell TPS File Transfer Service is not running
Enable Auto Start HW File Transfer Service in Settings, or manually start the service via Windows Services (services.msc). Verify the File Transfer Service Name in Settings matches the actual Windows service name.
EC file generation fails
LCN Wizard parameters (LCN Site ID, LCN ID, AM Unit ID) are incomplete or incorrect, or EC template files are missing from application resources
Review and complete all LCN Wizard parameters. Reinstall Asset Backup Scheduler if application resource files are corrupted or missing.
Control Architect Snapshot Not Generated
Symptom
Likely Cause
Resolution
Backup run completes but no snapshot is generated
Enable Snapshot Auto Generation is not enabled in Settings
Enable the Snapshot Auto Generation option in Settings and re-run the backup.
Snapshot generation notification sent but Control Architect does not respond
The Control Architect Host API Address is incorrect, Control Architect is not running, or a firewall is blocking the API call
Verify the Control Architect Host API Address in Settings. Confirm Control Architect is running on the target host. Check firewall rules for the API communication port.
Snapshot Generated Time is not visible in Job History
The snapshot was not triggered, or the run did not complete successfully
Check the overall backup run status in Job History. A Failed or Canceled run will not trigger snapshot generation. Resolve any backup failures and re-run.
Collecting Diagnostic Information for Support
If a problem cannot be resolved using the guidance above, collect the following information before contacting support:
1. Enable Debug Logging in Settings and reproduce the issue.
2. Collect the log files from: %AppData%\Automation Software Technology, Inc\AssetBackupScheduler\
3. Capture the Activity Messages from the failed backup run in the Job History tab (right-click to copy messages to clipboard).
4. Note the exact error messages displayed, including any SQL Server error codes or Windows service error messages.
5. Record the Asset Backup Scheduler version number (visible in the application title bar or About dialog).
