Home
  •  

Registrar Database: Total ODBC Timeout Failures

Microsoft.LS.2019.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_REGDBACCESS_TOTAL_ODBC_TIMEOUT_FAILURES (UnitMonitor)

Knowledge Base article:

Summary

The total number of ODBC timeout failures that have occurred since the server started.

Causes

Registrar database is overloaded.

Resolutions

This might be a temporary condition. If the problem persists, please ensure that hardware and software requirements for this server meets the user usage characteristics.

Element properties:

TargetMicrosoft.LS.2019.Component.Registrar
Parent MonitorSystem.Health.PerformanceState
CategoryPerformanceHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityHigh
Alert Auto ResolveTrue
Monitor TypeMicrosoft.LS.2019.Performance.Double.DeltaThresholdMonitor
RemotableTrue
AccessibilityPublic
Alert Message
[Skype] The total number of ODBC timeout failures that have occurred since the server started.
Perf Object Name:
Perf Counter Name: {0}
Perf Counter Value: {1}
Error Threshold: 500
Warning Threshold: 100
Delta Window Size: 1
Single instance perf counter
Please see the 'Product Knowledge' and the 'Alert Context' tab on Alert Properties view for more information.
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.LS.2019.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_REGDBACCESS_TOTAL_ODBC_TIMEOUT_FAILURES" Accessibility="Public" Enabled="true" Target="SFBDiscovery!Microsoft.LS.2019.Component.Registrar" ParentMonitorID="Health!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="Microsoft.LS.2019.Performance.Double.DeltaThresholdMonitor" ConfirmDelivery="false">

  <Category>PerformanceHealth</Category>

  <AlertSettings AlertMessage="Alert_The_total_number_of_ODBC_timeout_failures_that_have_occurred_since_the_server_started.">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>High</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/CounterName$</AlertParameter1>

      <AlertParameter2>$Data/Context/Value$</AlertParameter2>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="Microsoft.LS.2019.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_REGDBACCESS_TOTAL_ODBC_TIMEOUT_FAILURES_OverThreshold" MonitorTypeStateID="OverThreshold" HealthState="Error"/>

    <OperationalState ID="Microsoft.LS.2019.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_REGDBACCESS_TOTAL_ODBC_TIMEOUT_FAILURES_UnderThreshold" MonitorTypeStateID="UnderThreshold" HealthState="Success"/>

    <OperationalState ID="Microsoft.LS.2019.Monitoring.UnitMonitor.ThresholdPC.Registrar.PERF_REGDBACCESS_TOTAL_ODBC_TIMEOUT_FAILURES_UnderThresholdOverThreshold" MonitorTypeStateID="UnderThresholdOverThreshold" HealthState="Warning"/>

  </OperationalStates>

  <Configuration>

    <ComputerName>$Target/Host/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

    <CounterName>USrv - Total ODBC Timeout Failures</CounterName>

    <ObjectName>LS:USrv - REGDBStore</ObjectName>

    <AllInstances>false</AllInstances>

    <Frequency>900</Frequency>

    <IncludeInstances/>

    <ExcludeInstances/>

    <WarningThreshold>100</WarningThreshold>

    <ErrorThreshold>500</ErrorThreshold>

    <NumSamples>1</NumSamples>

  </Configuration>

</UnitMonitor>