Fix SCOM Data Access Service Not Running or Not Initialized

One of the most common issues encountered after installing SCOM is that the data access service fails to start. This error prevents the operations manager console from launching with the error, “The Data Access service is either not running or not yet initialized.” Check the event log for more information.

The data access service in Microsoft System Center Operations Manager (SCOM) updates information in the operational database. The System Center Data Access service requires a dedicated account to run that is typically specified during the SCOM setup.

What happens when Data Access Service fails to start?

The data access service is set to launch automatically at SCOM server startup. However, when this service fails to start, you see the “Failed to connect to SCOM server: Data access service not running or not initialized” error.

Most administrators encounter this error with SCOM installations running on virtual machines, but it can also occur on physical servers. Closing and opening the operations console doesn’t help here because the problem is with the service itself.

Closing the SCOM console and launching it back brings up the same error again. In the same error window, the Additional Information section shows more information about why this issue could be occurring. You can also review the SCOM logs to find out more about the data access service startup issue.

Microsoft.EnterpriseManagement.Common.ServiceNotRunningException: The Data Access service is either not running or not yet initialized. Check the event log for more information. ---> System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://corpscom.prajwal.local:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:03.0062091. TCP error code 10061: No connection could be made because the target machine actively refused it [2001:0:9d38:6abd:24c4:aa2:3f57:9b79]:5724. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it [2001:0:9d38:6abd:24c4:aa2:3f57:9b79]:5724
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
--- End of inner exception stack trace ---

Check Event Viewer for SCOM Event ID 7031

If the data access service is repeatedly stopping on your server, you must check the event viewer to find out more on why exactly it’s happening. The Event ID 7031 gets logged when a service crashes or when a service stops unexpectedly.

In our case, we see the Event 7031 on the SCOM server shows that the data access service terminated unexpectedly. Although it says corrective action “restart the service” will be taken in 60000 ms, the service doesn’t start, and you still cannot launch the SCOM console.

Fix SCOM Data Access Service Not Running

There are two reasons why the data access service fails to initialize on an SCOM server:

1. The System Center Data Access Service is in a stopped state, or the credentials used for running this service are expired or specified incorrectly.
2. The firewall is disabled on the server, or TCP ports 5723 and 5724 are blocked.

Solution 1: Manually restart the Data Access Service

If you are experiencing the data access service startup issue for the first time, the simplest way to resolve it is to manually restart the service. Sign in to the SCOM server and launch the services console. Right-click System Center Data Access Service and select Start.

Note: The startup type of the data access service is set to Automatic by default, and this shouldn’t be changed.

After following the above steps, launch the Event Viewer and now look for Event 7036. We see that event ID 7036 confirms that the System Center Data Access service entered the running state. Now launch the SCOM console, and you will not see the start-up error.

Solution 2: Configure a Firewall for Operations Manager

If the data access service is repeatedly crashing on the SCOM server, it could be your firewall that is causing this. The data access service will not start if the firewall is turned off or TCP ports 5723 and 5724 are blocked.

If it’s a firewall that is causing this issue, you will see the TCP error code 10061: No connection could be made because the target machine actively refused it in the error description.

Microsoft.EnterpriseManagement.Common.ServiceNotRunningException: The Data Access service is either not running or not yet initialized. Check the event log for more information. > System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://scom.prajwal.local:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:01.0011001. TCP error code 10061: No connection could be made because the target machine actively refused it SCOM IP:5724.  > System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it.

If the firewall is turned off, you should turn it on. In addition, you should configure your firewall to allow communication between the different Operations Manager features on your network. Your network administrator should ensure that TCP ports 5723 and 5724 are open on the management server.

For more information, refer to the guide on configuring the firewall for operations manager.