Page History
...
This issue typically occurs when SQLCM SQL CM is unable to establish or maintain the necessary connection, hindering its functionality. Whether due to network restrictions, server instance unavailability, or configuration errors, understanding the underlying causes and solutions to this problem is essential for troubleshooting and restoring efficient communication.
The potential causes behind the disruption could be:
- SQLCM SQL CM cannot connect to a SQL Server instance (repository or audited instance).
- To address this issue, verify the following:
- The repository SQL server is online
- The CM SQL Compliance Manager components (Collection Server and the Agents) are online
- The audited instances are online
- The user login credentials are correct
...
- To resolve this issue, it is necessary to verify the following:
- Confirm that the CM SQL Compliance Manager components (Collection Server and the Agents) are online
- Inspect if the audited instances are online
- Check that the repository of the SQL server is online
...
The potential causes behind the disruption could be:
- The CM SQL Compliance Manager Components (Collection Server and Agents) are offline
- The repository of the SQL server or the audited instance is offline
- Missing configuration files. Please verify your configuration files and save your settings
...