locked
The Data Access service is either not running or not yet initialized RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi there,

    We shut down our SCOM server two months ago. Yesterday, we were informed to bring SCOM server up, and run a performance report for some servers. However, when we tried to open SCOM console from either server or workstation, we got "The Data Access service is either not running or not yet initialized" error. Also, it seems like that System Center Data Access service started for while and then stop by self. Does anyone have any idea about how to resolve this issue? Please see error log below. Thanks!

    Date: 1/4/2018 2:52:45 PM
    Application: Operations Manager
    Application Version: 7.1.10226.1360
    Severity: Error
    Message: Failed to connect to server 'aba-scom'

    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://aba-scom: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 10.10.10.10:5724.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.10.10.10: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.LayeredChannel`1.OnOpen(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.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, 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://aba-scom: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 10.10.10.10:5724.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.10.10.10: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.LayeredChannel`1.OnOpen(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.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, 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.10.10: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)

    Thursday, January 4, 2018 9:07 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    >>Could not allocate space for object 'sys.sysbinobjs'.'clst' in database 'OperationsManager' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup<<

    Yes, that can very well be the reason behind this. Suggest you to increase the size of your OpsDB and check if the issue persists.

    Please follow these link below:
    ould not allocate space for object.

    Also, suggest you to decrease the data retention period in the OpsDB from 7 days by default to lets say 4 or 5 days.

    Administration >  Settings > Database Grooming

    Don't forget to set the DAS startup type back to Automatic :)

    Hope this helps.

    Cheers

    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!)


    Saturday, January 6, 2018 7:23 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    >>Center Data Access service started for while and then stop by self. Does anyone have any idea about how to resolve this issue? Please see error log below. Thanks!
    >>Microsoft.EnterpriseManagement.Common.ServiceNotRunningException: The Data Access service is either not running or not yet initialized.

    Please check whether "system Center Data Access service", running on Managment server" is runniong or not. If it is not running, start it manually. Besides, also check any firewall block port 5724 communication and also check management server event log for any error.

    Roger

    Friday, January 5, 2018 1:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    Suggest you to restart your SCOM Database services. Also please check the port if its listening as suggested by Roger.

    Cheers

    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!)

    Friday, January 5, 2018 5:08 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Also please check the Log on account of Data access service is active.

    Sree

    Friday, January 5, 2018 6:07 AM
  • Question
    Sign in to vote
    0
    Sign in to vote


    Please check whether "system Center Data Access service", running on Managment server" is runniong or not. If it is not running, start it manually. Besides, also check any firewall block port 5724 communication and also check management server event log for any error.

    Roger

    HI Roger,

    System Center Data Access Server is configured to start up automatically on SCOM server. We tried to change it to manually, and restarted the service, but it started up for while and then stopped by itself. Firewall is disabled by our group policy, so it shouldn't block any ports.

    Friday, January 5, 2018 3:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We found out in Operations Manager event log that every time after we restarted system center data access service, it came up with OpsMgr SDK Service error Event ID 26380. It says "Could not allocate space for object 'sys.sysbinobjs'.'clst' in database 'OperationsManager' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup."

    Is this the reason system center data service keeps to stop by self? We don't have DBA, and not sure how to clean this up and free some space. Please help!

    Friday, January 5, 2018 8:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi There,

    As Sam and Roger said, First do check either MOMchanel port is open or not and as i could see the below error message the server "ABA-SCOM", please check on this mgmt server the services are running or not. And also restart the services once. Hope this will fix the error!

    Date: 1/4/2018 2:52:45 PM
    Application: Operations Manager
    Application Version: 7.1.10226.1360
    Severity: Error
    Message: Failed to connect to server 'aba-scom'

    Cheers, Gourav (Please do take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!) or find my Facebook and LinkedIn link in profile.

    Saturday, January 6, 2018 6:53 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    >>Could not allocate space for object 'sys.sysbinobjs'.'clst' in database 'OperationsManager' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup<<

    Yes, that can very well be the reason behind this. Suggest you to increase the size of your OpsDB and check if the issue persists.

    Please follow these link below:
    ould not allocate space for object.

    Also, suggest you to decrease the data retention period in the OpsDB from 7 days by default to lets say 4 or 5 days.

    Administration >  Settings > Database Grooming

    Don't forget to set the DAS startup type back to Automatic :)

    Hope this helps.

    Cheers

    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!)


    Saturday, January 6, 2018 7:23 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Sameer,

    We tried by following the link you provided, but it ended with anther SQL error.

    The transaction log for database 'OperationsManager' is full due to 'NOTHING'.  (Microsoft SQL Server, Error: 9002)

    What will happen if we shirk the transaction log? Will we lose any SCOM data? Thank you.

    Monday, January 8, 2018 3:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    It is not suggested to shrink operationsmanager database. 

    Here is a similar thread for your reference:

    https://social.technet.microsoft.com/Forums/systemcenter/en-US/115b6708-5e74-4b42-a237-919a255d551d/large-opsmgr-database-logfile?forum=operationsmanagergeneral

    In addition, the article below should be helpful:

    https://blogs.technet.microsoft.com/kevinholman/2010/10/05/uh-oh-operations-database-is-full/

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Proposed as answer by GouravIN Wednesday, September 4, 2019 6:35 AM
    Friday, January 12, 2018 2:32 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    this worked for me, I also set the service to automatic 
    Wednesday, September 4, 2019 1:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    >>"Could not allocate space for object 'sys.sysbinobjs'.'clst' in database 'OperationsManager' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrow on for existing files in the filegroup."

    In the short term, make sure that database and file group can autogrow. Moreover, make sure that the HD containing DB file has free space.

    Roger
    Wednesday, September 4, 2019 4:39 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    We found out in Operations Manager event log that every time after we restarted system center data access service, it came up with OpsMgr SDK Service error Event ID 26380. It says "Could not allocate space for object 'sys.sysbinobjs'.'clst' in database 'OperationsManager' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup."

    Is this the reason system center data service keeps to stop by self? We don't have DBA, and not sure how to clean this up and free some space. Please help!

    Hi,

    did you resolve this? We would appreciate your feedback. 

    Thanks in advance!

    Regards,

    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" where applicable. This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks!) Blog: https://blog.pohn.ch/ Twitter: @StoyanChalakov

    Friday, September 13, 2019 8:40 AM