SQL Service

Summary

This monitor tracks the status of the SQL Server (COMPUTECLUSTER) service. When this service is stopped, none of the administration or job tasks can be performed.

Configuration

For a failover cluster, the SQL Server (COMPUTECLUSTER) service is not configured to start automatically on both of the head nodes and the “Alert only if service startup type is automatic” option is set to True by default in the management pack. To monitor the SQL Server (COMPUTECLUSTER) service on a failover cluster, you must manually change the “Alert only if service startup type is automatic” option to False on the current active head node.

Causes

This error can be caused by any of the following:

• The SQL Server (COMPUTECLUSTER) service encountered an error and had to stop running.

• The SQL Server (COMPUTECLUSTER) service is disabled.

• Group policy does not allow this service to start.

Resolutions

To troubleshoot and fix this problem:

• Restart the service on the target head node.

• If the service cannot be started, resolve the errors that are reported by the Service Control Manager. The Service Control Manager will produce an error event if the service is terminated unexpectedly. Start the Event Viewer on the target compute node and check for any system events from the Service Control Manager or application events from the SQL Server (COMPUTECLUSTER) service. Resolve any errors that are reported by these events.

• If the service still cannot be restarted, contact the domain administrator to make sure that this service is not disabled by the domain group policy.

• If the preceding steps do not resolve the problem, uninstall and reinstall the HPC Pack on the compute node.

Additional

Recovery task will be run automatically to restart the service, so you may find the service keeps restarting while you are trying to stop it. There are couple of options to avoid it happen:

• Disable the recovery task;

• Change the service to start manually.