Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Status TypePossible Causes
Alert/Error
  • The Repository is installed on a SQL Server 2000 2005 instance but a SQLcompliance Agent is deployed to a SQL Server 2005 2012 or later instance. For example, to audit activity on instances running SQL Server 2005, install a second Repository on a SQL Server 2005 instance.
  • A version 1.1 SQLcompliance Agent is deployed to a SQL Server 2005 or later instance. Version 1.1 does not support auditing SQL Server 2005 instances. To continuing auditing SQL Server 2005 instances, upgrade the agents to the latest version.
  • The SQLcompliance Agent missed every heartbeat over the last 24 hours. This issue occurs when the SQLcompliance Agent service is stopped, the Collection Server is offline, the computer hosting the agent is offline, or network availability is lost.
  • The SQLcompliance Agent service is no longer running. The SQLcompliance Agent service is stopped by a SQL Server login or a third-party application.
  • A system alert is triggered. System alerts notify you when the health of your SQL Compliance Manager deployment may be compromised. For more information, see the Activity Log tab.
OKSQL Compliance Manager is performing as expected.
Warning
  • No SQL Server instances are registered with SQL Compliance Manager. SQL Compliance Manager cannot begin auditing your environment until instances are registered, SQLcompliance Agents are deployed, and audit settings are configured.
  • The SQLcompliance Agent is not yet deployed to an instance that is registered with SQL Compliance Manager. SQL Compliance Manager cannot audit this instance until an agent is deployed and audit settings are configured.
  • A deployed SQLcompliance Agent has not yet contacted SQL Compliance Manager. This issue occurs when the SQLcompliance Agent service is stopped, the computer hosting the agent is offline, or network availability is lost.
  • A deployed SQLcompliance Agent missed two sequential heart beats. This issue occurs when the SQLcompliance Agent service is stopped, the computer hosting the agent is offline, or network availability is lost.

...