Jaa


Server role installation issues (Sdk Service has not yet initialized),Or Please call ManagementGroup.Reconnect() to reestablish the connection, issues

I've come across a number of cases in the past where Opsmgr/SCE server role installation may fail, or even post installation processes such as report deployment can fail with no indication as to why. Some symptoms you may see which may indicate the need to install the hotfix detailed below are:

 

Installing an Opsmgr/SCE server roll results in an MSI installation failure and subsequent rollback with the error "The setup wizard was interrupted before System Center Operations Manager 2007 could be installed."
Then clicking the Finish button pops up an error dialogue the says "The setup failed. Do you want to open the setup log file (search for "value 3" in the file for locating failure)". Although this message can be displayed for a very wide variety of reasons, if you search the failed MSI log for " Sdk Service has not yet initialized. Please retry" and get a hit with a stack trace similar to below, it's quite likely this is your problem.

 

AssociateSecureRefsForADWriterAndAlertSubscriptionModules: Error: Sdk Service has not yet initialized. Please retry,
Stack:    at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.HandleIndigoExceptions(Exception ex)
   at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.CreateChannel(TieredManagementGroupConnectionSettings managementGroupTier)
   at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer..ctor(DuplexChannelFactory`1 channelFactory, TieredManagementGroupConnectionSettings managementGroupTier, IClientDataAccess callback, CacheMode cacheMode)
   at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.CreateEndpoint(ManagementGroupConnectionSettings connectionSettings, IClientDataAccess clientCallback)
   at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.Connect(ManagementGroupConnectionSettings connectionSettings)
   at Microsoft.EnterpriseManagement.ManagementGroup..ctor(ManagementGroupConnectionSettings connectionSettings)
   at Microsoft.EnterpriseManagement.ManagementGroup.Connect(ManagementGroupConnectionSettings connectionSettings)
   at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.AssociateSecureRefsForADWriterAndAlertSubscriptionModules(Session session)

 

Another possible post server roll installation problem which you may see is instances of "Please call ManagementGroup.Reconnect() to reestablish the connection" in events (opsmgr event log) or alerts, such as the following:

Report deployment process failed to request management pack list from SQL RS Server. The operation will be retried. Exception 'ServerDisconnectedException': The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection. One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DataWarehouse.Deployment.Report

 

If you do see symptoms such as those described above, installation of the following Windows Server 2003 SP1 & SP2 hotfix may well solve the issue : https://support.microsoft.com/default.aspx/kb/931319/ (Error code when you run a network program that uses a Winsock connection on a computer that is running Windows Server 2003: "WSAECONNABORTED (10053)"). Details of how to obtain the hotfix are discussed in the article.

A KB article for OpsMGr/SCE will be available shortly. If I discover any more symptoms I'll be sure to include them.

Comments

  • Anonymous
    January 01, 2003
    The comment has been removed
  • Anonymous
    January 01, 2003
    I searched for an error I was getting in SCE : AssociateSecureRefsForADWriterAndAlertSubscriptionModules: Error: Sdk Service has not yet initialized. Please retry, Stack:    at Microsoft.EnterpriseManagement.DataAbstractionLayer.SdkDataAbstractionLayer.HandleIndigoExceptions(Exception ex) There was only one link that came back, that was your blog. Thank you, I have submitted a request for that hotfix.