Access Services: Excessive SQL Connection Retries

Microsoft.SharePoint.2016.AccessDataServicesExcessiveSQLConnectionRetries (AggregateMonitor)

We're retrying too many times when connecting to the application SQL database.

Knowledge Base article:

Summary

This monitor rolls up the health information for all monitors under it. If this monitor reflects an unhealthy state, it means that one or more monitors that roll up to this monitor reflect an unhealthy state. If the state is unknown, either monitoring has not begun for this object or there are no monitors defined that roll up to this monitor.

Causes

An unhealthy state for this monitor indicates some problem with another monitor running against this object. View all current alerts from this object using this link:

View Alerts

Resolutions

Use the health explorer to drill down and find the cause of the unhealthy state. Use the knowledge on the specific monitor causing the issue to troubleshoot and fix the problem.

Element properties:

Target

Microsoft.SharePoint.2016.SPServiceInstance.Access2

Parent Monitor

System.Health.AvailabilityState

Algorithm

BestOf

Category

AvailabilityHealth

Enabled

True

Alert Generate

True

Alert Severity

MatchMonitorHealth

Alert Priority

Normal

Alert Auto Resolve

True

Remotable

True

Accessibility

Public

Alert Message

Access Services: Excessive SQL Connection Retries

A warning incident has occurred where the back end Access Data Services application server is not able to open a connection to the SQL server on the initial attempt.

Source Code:

<AggregateMonitor ID="Microsoft.SharePoint.2016.AccessDataServicesExcessiveSQLConnectionRetries" Accessibility="Public" Enabled="true" Target="MOSS16Core!Microsoft.SharePoint.2016.SPServiceInstance.Access2" ParentMonitorID="Health!System.Health.AvailabilityState" Priority="Normal">

  <Category>AvailabilityHealth</Category>

  <AlertSettings AlertMessage="Microsoft.SharePoint.2016.AccessDataServicesExcessiveSQLConnectionRetries_AlertMessageResourceID">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

  </AlertSettings>

  <Algorithm>BestOf</Algorithm>

</AggregateMonitor>