Sign in
 
Home2012Previous VersionsLibraryForumsGallery
System Center TechCenter >
> 
> 
"The Data Access service is either not running or not yet initialized" error after restoring the encryption key in SCSM 2010

Answered "The Data Access service is either not running or not yet initialized" error after restoring the encryption key in SCSM 2010

  • Tuesday, July 10, 2012 8:15 PM
     
     
    Sign In to Vote
    0

    Hi all,

    I created a new environment and installed SCSM 2010 Managment server and etc... then I restored the Encyprion key that I just backed up from my production environment. After doing so, I encountered the above error. I even uninstalled the SCSM and installed it again but still the same error.

    Can you please help?

    attached is th event log.

    Thanks!

    Date: 7/10/2012 3:55:06 PM
    Application: System Center Service Manager Console
    Application Version: 7.0.6555.128
    Severity: Error
    Message: Failed to connect to server 'SVR-DEV-SMSC'

    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://svr-dev-smsc:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:02.0157411. TCP error code 10061: No connection could be made because the target machine actively refused it ::1:5724.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it ::1: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.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.ConnectInternal(EnterpriseManagementConnectionSettings connectionSettings)
       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.ServiceManagementGroup.InternalInitialize(EnterpriseManagementConnectionSettings connectionSettings, EnterpriseManagementGroupInternal internals)
       at Microsoft.EnterpriseManagement.ServiceManagementGroup..ctor(ServiceManagementConnectionSettings connectionSettings)
       at Microsoft.EnterpriseManagement.UI.SdkDataAccess.ManagementGroupSessionManager.Connect(String server)
       at Microsoft.EnterpriseManagement.ServiceManager.UI.Console.Credentials.ManagementGroupConnection.TryConnectToManagementGroupJob(Object sender, ConsoleJobEventArgs args)
    System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://svr-dev-smsc:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:02.0157411. TCP error code 10061: No connection could be made because the target machine actively refused it ::1:5724.  ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it ::1: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.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.ConnectInternal(EnterpriseManagementConnectionSettings connectionSettings)
       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: No connection could be made because the target machine actively refused it ::1: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)

     

All Replies

  • Wednesday, July 11, 2012 5:47 AM
     
     
    Sign In to Vote
    0

    I am open to correction here,

    But I am sure you are meant to restore the encryption key first and then install SCSM and choose the option to use an existing database.

    From the DR Guide

    1.     Start with a new computer that has the same computer name as the computer that failed.
    2.     Restore the encryption key that you saved from the original Service Manager management server. For more information, see How to Restore the Service Manager Encryption Key in this guide.
    3.     Install a Service Manager management server. For more information, see "Service Manager 2010 SP1 Deployment Scenarios" in the System Center Service Manager 2010 SP1 Deployment Guide (http://go.microsoft.com/fwlink/?LinkId=198071).

    http://blogs.technet.com/b/servicemanager/archive/2010/04/25/where-s-the-docs.aspx

    F.

    As long as you learn something new every day, the day is not wasted.

     
  • Wednesday, July 11, 2012 1:43 PM
     
     
    Sign In to Vote
    0
     

    Fletcher, the computer that I am talking about is the service manager management server.

    I first installed service manager management server and etc... Registered with the DW ... Everything was working well. Then I restore the backed up encryption key and the error showed up.

    I think you mean I should have restored the key while installing the management server, is that right?

     
  • Wednesday, July 11, 2012 1:50 PM
     
     
    Sign In to Vote
    1

    Hi,

    you should restore the Encryption key first

    Then

    Install Service Manager

    As long as you learn something new every day, the day is not wasted.

     
  • Wednesday, July 11, 2012 2:04 PM
     
     
    Sign In to Vote
    0

    Thanks Fletcher!

    I think I should wipe the server and start from the beginning.

    I also restored the key in DW management server, so I think I should wipe that too.

     
  • Wednesday, July 11, 2012 2:31 PM
     
     
    Sign In to Vote
    0

    your data should be fine, unless you want to wipe the data.

    1. Restore encryption key.

    2. Restore DB if needed.

    3. Install using existing DB

    F.

    As long as you learn something new every day, the day is not wasted.

     
  • Wednesday, July 11, 2012 2:37 PM
     
     Answered
    Sign In to Vote
    0

    I had no data on the management server and DW management server. The reason I am wiping is that unistalling the SCSM didn't work...

    DB and DWDBs are already restored on 2 other servers. Still I can use the exsiting DB, right?

     
  • Wednesday, July 11, 2012 2:39 PM
     
     
    Sign In to Vote
    0

    Name needs to remain the same or you can try this.

    This one I have tried and works

    http://blogs.technet.com/b/servicemanager/archive/2012/04/22/moving-the-service-manager-and-dw-databases.aspx

    I have not tried this as yet

    http://blogs.technet.com/b/servicemanager/archive/2012/06/28/moving-the-scsm-data-warehouse-dw-databases.aspx

    F.

    As long as you learn something new every day, the day is not wasted.

     
  • Wednesday, July 11, 2012 3:08 PM
     
     
    Sign In to Vote
    0

    As there is nothing installed on the servers now, do I still need to stop the services?

    what I am doing now is creating a 2010 Lab environment mirror production to test the 2012 upgrade. At this poit I am just trying to install the 2010 with my production encryption keys.

    The DB and DWDB backups are restored on two seperate servers.

     
  • Thursday, July 19, 2012 8:05 PM
     
     
    Sign In to Vote
    0

    Hi Fletcher,

    Is restoring the encryption key required? it is not mentioned in the steps on http://technet.microsoft.com/en-us/library/hh914226 or http://technet.microsoft.com/en-us/library/hh914226 

    I guess you created the lab environment (mirror your production) and tested the upgrade there, right?

    So, did you restore the encryption key after restoring the DB and before installing 2010 on your lab environment?

    Thanks,

    Parisa

     
  • Friday, July 20, 2012 5:44 AM
     
     Answered
    Sign In to Vote
    0

    Hi,

    yes, the restoration of the encryption is needed if you want to use existing data.

    and yes I tested this originally in a lab environment but have since done it in our production environment.

    F.

    As long as you learn something new every day, the day is not wasted.