Displayed when:

All monitoring data is being collected successfully.

Click Show log and select All events to view all data collection events in the last five minutes.

SQL Monitor is currently unable to collect monitoring data because the credentials it is using have failed authentication. A Monitoring stopped ([host machine|SQL Server] credentials) alert is also raised.

Suggested action:

• For host machine authentication failures, check that the credentials supplied to log in are valid and have sufficient permissions to collect WMI data, read the registry, and access files.
• For SQL Server instance authentication failures, check that the user name and password are correct and the log in has the required permissions.

  For more information, see Account permissions required.

  After an authorization error, by default SQL Monitor will not attempt to reconnect until you either change the credentials specified in SQL Monitor, or change the account permissions (in this case, you will need to click Retry connection on the Monitored Servers page). This prevents SQL Monitor from sending a potentially large number of failed login messages to your security log, and triggering Intrusion Detection System in the process.

  If the potential impact on your security log will not cause significant problems to your systems, you can change this default setting so that SQL Monitor will automatically attempt reconnection. See Reconnecting automatically after monitoring stopped.

  Once the correct credentials are entered and authentication is successful, monitoring will resume and the Monitoring stopped ([host machine|SQL Server] credentials) alert will be marked as Ended.

Displayed when:

One of the following reasons applies:

• The host machine or cluster node is not responding to Ping requests; either the machine name is incorrect or there is a network problem. A Machine unreachable alert is also raised, and a SQL Server instance unreachable alert is raised for each instance on the machine.
• The SQL Server service has been stopped or there is a problem with SQL connectivity. A SQL Server instance unreachable alert is also raised.
• The Remote Registry service is not started or remote file access is not set up. If this problem occurs continuously for 2 minutes, a Monitoring error ([host machine|SQL Server] data collection) alert is also raised.

Suggested action:

• Check that you have entered the server name correctly, and that your machine is not behind a firewall.
• Click Show log and check the Exception and Exception messagecolumns displayed in the table of data collection events to determine the specific problem.

  For more information, see Testing data collection methods.

Displayed when:

An unknown application error has occurred.

If this problem occurs continuously for 2 minutes, a Monitoring error ([host machine|SQL Server] data collection) alert is also raised.

Suggested action:

Please contact Red Gate support with information about your error, including relevant log file details. See Viewing component information and log files.

Displayed when:

SQL Monitor cannot process some data collected from the host machine or cluster node. Possible reasons are:

• The performance counter library may be corrupt and needs rebuilding. For information about rebuilding your PerfMon library, see http://support.microsoft.com/kb/300956.
• A WMI provider may be corrupt and needs rebuilding. For information about troubleshooting WMI, see http://technet.microsoft.com/en-us/library/ff406382.aspx.
• You are running a 32-bit SQL Server instance on a 64-bit Windows machine, and some performance counter objects are not available. For more information, see this MSDN article on 64-bit Support.

Suggested action:

Click Show log and refer to the Exception and Exception message columns in the  table of data collection events to determine the specific problem.

Displayed when:

One of the following reasons applies:

• Remote file access is not set up (hidden administrative shares should be enabled).
• One of the required services (WMI, Remote Registry) is not started.
• There is a problem with SQL connectivity.

  If this problem occurs continuously for 2 minutes, a Monitoring error ([host machine|SQL Server] data collection) alert is also raised.

Suggested action:

SQL Monitor will automatically retry the connection every few minutes. Click Show log and refer to the Exception and Exception message columns in the table of data collection events for information about the type of problem.

For more information, see Testing data collection methods.

Displayed when:

Your evaluation period has expired and the machine, cluster node or SQL Server instance has not yet been licensed.

Suggested action:

Enter a serial number or allocate licenses on the Configuration > Licensing page. One license is required for each host machine or cluster node - this will license all SQL Server instances on the machine or node.

For more information, see Licensing.

Displayed when:

Monitoring on this machine, cluster node or SQL Server instance has been manually suspended. No data will be collected until you resume monitoring.

Suggested action:

Go to the Configuration > Monitored servers page, click the Actions button  at the end of the row and select Resume monitoring.

For more information, see Configuring monitored servers.

Displayed when:

The host machine or node is currently in a maintenance window. SQL Monitor is still monitoring servers, but alerting is temporarily suspended. Once the maintenance window duration has ended, alerting will resume.

Suggested action:

Go to the Configuration > Monitored servers page to check when the current maintenance window is due to end.

For more information, see Setting maintenance windows.