Today when I powered on my VM and launched SCOM console, it gave an error. This VM was powered off for some days and I when I powered it on, SCOM console failed to launch. The error was Failed to connect to server “server FQDN”. The Data Access service is either not running or not yet initialized. Check the event log…
The error message is important because it also tells the reason for failing the console to start. Checking the event viewer shows lot of other errors that are logged. Closing the SCOM console and launching it back brings up the same error again.Along with the error message, we also find a lengthy code under additional information. I never understood anything further beyond first line.
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 ---
SCOM Data Access Service Not Running
If you look at other forum threads, it is suggested to check whether SCOM Center Data Access service is running or not. If it is not running, start it manually. In addition to that, check if required ports are open on firewall. Here is an article on SCOM firewall ports. The last step is to check event viewer logs for any errors.
In my case the System Center Data Access service is configured to start up automatically on SCOM server. Changing it to manually and restarting the service didn’t help. As I am running SCOM in my lab, I have turned off the firewall on VM, so it shouldn’t block any ports.
Event 7031 tells us the SCOM data access service terminated unexpectedly. Thought it says corrective action “restart the service” will be taken in 60000 ms, i don’t think the service is restarted.
The solution here is to go to services console on SCOM server and start System Center Data Access Service.
Go to event viewer and now look for Event 7036. The System Center Data Access service entered the running state. Now launch the SCOM console and you will not find the start up error. So far I have been restarting this service whenever I encounter the error.