none
SCOM 2012 issue: Error when starting SCOM Management Console. Can you help PLEASE? RRS feed

  • General discussion

  • So last night I had SCOM working wonderfully but when I got home to work on the server I couldn't log in to the management console (from the management server). I keep getting an error

    Failed to connect to server 'servername.domain.local'

    The Data Access Service is either not running or not yet initialized, check even log for more information.

    The event log really isn't any help it just says "The System Center Data Access Service service terminated unexpectedly. It has done this xx time(s).

    I have tried:

    1. Repairing the Console Installation from control panel

    2. Restarting the service

    3. Changing the account used for the service

    4. Reinstalling the management console

    5. Adding a registry key (per a Microsoft KB)

    Here is the message from SCOM

    Date: 6/27/2012 8:48:49 AM
    Application: Operations Manager
    Application Version: 7.0.8443.0
    Severity: Error
    Message: Failed to connect to server server.domain.local'

    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://server.domain.local:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:02.0039292. TCP error code 10061: No connection could be made because the target machine actively refused it 10.10.1.185:5724.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.10.1.185: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 ---

    Server stack trace:
       at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
       at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
       at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.EnterpriseManagement.Common.Internal.IDispatcherService.Connect(SdkClientConnectionOptions connectionOptions)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Initialize(EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
       --- End of inner exception stack trace ---
       at Microsoft.EnterpriseManagement.Common.Internal.ExceptionHandlers.HandleChannelExceptions(Exception ex)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.ConstructEnterpriseManagementGroupInternal[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore clientCallback)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.RetrieveEnterpriseManagementGroupInternal[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Connect[T,P](EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
       at Microsoft.EnterpriseManagement.ManagementGroup.InternalInitialize(EnterpriseManagementConnectionSettings connectionSettings, ManagementGroupInternal internals)
       at Microsoft.EnterpriseManagement.Mom.Internal.UI.Common.ManagementGroupSessionManager.Connect(String server)
       at Microsoft.EnterpriseManagement.Monitoring.Console.Internal.ConsoleWindowBase.TryConnectToManagementGroupJob(Object sender, ConsoleJobEventArgs args)
    System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://server.domain.local:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:02.0039292. TCP error code 10061: No connection could be made because the target machine actively refused it 10.10.1.185:5724.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.10.1.185: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 ---

    Server stack trace:
       at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
       at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
       at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
       at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.EnterpriseManagement.Common.Internal.IDispatcherService.Connect(SdkClientConnectionOptions connectionOptions)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Initialize(EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
       at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint[T](EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
    System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 10.10.1.185: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)

    If someone could help me figure this error out I would really really appreicate it.

    Thank you


    • Edited by mattfreshwater Wednesday, June 27, 2012 2:39 PM added error
    Wednesday, June 27, 2012 2:00 PM

All replies

  • Hi

    This isn't a console issue so there is no need to reinstall consoles.

    Check the SQL Server service is running. If that stops, the Data Access service will stop. Also that he OPerationsManager database isn't full.

    Also check the SQL Server error log.

    Do you have group polices that restrict membership of the local administrators group?

    Cheers

    Graham


    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

    Wednesday, June 27, 2012 2:18 PM
    Moderator
  • Hi Graham,

    Thank you for your quick reply. I checked the SQL service and that seems to be running fine. I will look at the SQL database. I do have a group policy that restricts membership to the local admins group. Do you think this could possibly be a permission issue?

    Wednesday, June 27, 2012 2:51 PM
  • How did you get on with this issue?

    After applying one of the following updates - KB2677070, KB2709630, KB2699779, KB2709981 - I also cannot get the Data Access Service started.

    Log Name:      Setup
    Source:        Microsoft-Windows-Servicing
    Date:          27/06/2012 9:48:17 a.m.
    Event ID:      2
    Task Category: None
    Level:         Information
    Keywords:      
    User:          SYSTEM
    Computer:      TARSCOM01.EIT.CAMPUS
    Description:
    Package KB2709981 was successfully changed to the Installed state.

    Log Name:      System
    Source:        Service Control Manager
    Date:          27/06/2012 9:48:49 a.m.
    Event ID:      7009
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SCOM01.DOMAIN
    Description:
    A timeout was reached (30000 milliseconds) while waiting for the System Center Data Access Service service to connect.

    I have checked the following

    • verified the permissions on the database.
    • verified the database instance is running on the same port (telnet db01 14035)



    • Edited by Andy.Scott Thursday, June 28, 2012 10:59 AM
    Thursday, June 28, 2012 10:58 AM
  • To the original poster - "I do have a group policy that restricts membership to the local admins group. Do you think this could possibly be a permission issue?"

    Make sure tha the Data Access Account is allowed to be a member of the local administrators. If it is removed then you will get an error when you try and start it.

    Also this TCP error code 10061: No connection could be made because the target machine actively refused it 10.10.1.185:5724. - could well be a firewall issue or a kerberos authentication issue. Check for any recent changes to those settings.

    Andy - your issue sounds like this - updates - KB2677070:

    http://www.systemcentercentral.com/Forums/tabid/60/categoryid/4/indexid/94083/Default.aspx


    Regards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

    Thursday, June 28, 2012 11:17 AM
    Moderator
  • Thank you Graham - creating the ServicesPipeTimeout registry entry has resolved my issue, as noted in KB922918

    Best of luck to the original poster - I would suggest also checking the SPN entrys for the Management Server and Data Access Service account.

    Kind Regards,

    Andy

    Thursday, June 28, 2012 11:35 AM
  • We had the same issue and our DBAs found that SCOM creates the OPS DB & DW DBs with FIXED sizes. Our DW DB got to its fixed size limit and failed to allow anymore data to be stored in the DB. By checking the Event logs on the DB server I found issue.
    Friday, July 20, 2012 6:07 AM