Connection error reporting
When a compliance plan can’t connect to a device, it captures the error and surfaces it in the compliance plan detail page and compliance reports. This topic explains how connection errors are recorded, where they appear, and how to troubleshoot them.
How connection errors are captured
During compliance plan execution, if a connection fails, Configuration Manager captures the error message exactly as the device or adapter returns it—without modification or inference.
If the device returns a specific error, that message appears verbatim in the UI. Common examples include:
SSH timeoutAuthentication failedNetwork unreachable
If a connection fails but the device returns no error details, the system displays the following standardized message:
Connection failed - no error details received from device.
Configuration Manager doesn’t attempt to infer or fabricate an error reason beyond what the device or adapter provides.
Connection errors apply only to live device connections. Compliance checks run against platform backup configurations don’t generate connection errors.
Where connection errors appear
Connection error information appears in three places:
Compliance plan detail page: The Connection Errors panel shows a breakdown of successful versus failed connections. Click View More Errors to open the full list of devices that failed, with the specific error message for each device.
Compliance report: Each report includes a Connection Errors panel showing connection results for that specific run, including the error message returned by each failed device.
Exports: When you export compliance results to CSV or JSON, connection error details and timestamps are included for all failed devices.
Troubleshoot connection failures
Use the error message displayed in the UI to identify the likely cause and next steps.
