A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
The “Data Access Service Group” health state reflects the health of the System Center Data Access Service across the management servers in the management group. When this management group function shows as failed or critical on multiple servers, the issue is typically with:
- Connectivity from those management servers to the Operations Manager operational database (and possibly the data warehouse database)
- The Data Access Service itself not running or failing to start
- Incorrect configuration of the database server name on the management servers
Use the following steps on one of the affected management servers and then repeat as needed on others:
- Verify the Data Access Service
- On each listed server (for example, ODSDMMDWSVR7, ODSDMMDWSVR8, ODSDMMDBSVR6, etc.), open Services.msc.
- Locate System Center Data Access Service.
- Ensure the service is set to Automatic and is Running.
- If it is stopped or repeatedly failing, restart it and immediately check the Operations Manager event log for related errors.
- Confirm database connectivity configuration
- On an affected management server, open Registry Editor.
- Navigate to:
HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Setup - Check the value of DatabaseServerName.
- Confirm that this value matches the actual SQL Server name (and instance name, if not default) that hosts the Operations Manager operational database.
- If the value is incorrect, update it to the correct
ServerNameorServerName\InstanceName. - After correcting, restart the System Center Data Access Service and recheck the health state.
- Check SQL Server availability
- From each affected management server, verify that the SQL Server hosting the Operations Manager database is reachable (for example, via ping and SQL tools if available).
- Ensure the SQL Server service and the SQL instance that hosts the Operations Manager database are running.
- Review Management Group Health dashboard
- In the Operations console, go to Operations Manager → Management Group Health.
- Confirm the health state of:
- System Center Data Access service group (function level)
- Management servers (infrastructure level)
- Use Health Explorer from this view to drill into the specific monitors and alerts that are critical for the Data Access Service Group and affected management servers.
- Validate data warehouse and other functions
- If the Data Warehouse DB or other management group functions also show critical, review their alerts and event logs on the management servers and SQL servers, as data warehouse connectivity or processing issues can also impact overall management group health.
Once the registry configuration and connectivity are corrected and the Data Access Service is running successfully on all affected management servers, the Data Access Service Group and Management Group Infrastructure states should return to healthy after the next monitoring cycle.
References: