Monday, September 19, 2011

The sdk service is either not running or not yet initialized

I would like to bring out some points which can be used to troubleshoot issue related to System Center Operation Manager 2007 R2 SDK Service. You may get the below mentioned error while opening SCOM console, or on other services or applications (like SharePoint) where this data is being utilized. The problem lies with the SCOM server's sdk (System Center Data Access) service.

To analyze the issue further, we will need to reproduce the issue and check “Operations Manager” logs from event viewer on SCOM server.

Following are few possibilities/cause of the issue -
  1. If any of the following service is stopped.
    • System Center Management (Health)
    • System Center Data Access (SDK)
    • System Center Configuration (Config service)
  2. If any of the above service is stopped, please start the service. 
  3. Re-enter the password for the identity of above services and restart the service. 
  4. In case we are getting an error while starting the service, the reason might one of the reasons mentioned below
  • Incorrect SPN set for the account that is running the System Center Data Access (OpsMgr SDK) service. Need to find out what SPNs are set for the account and rule out any possibility of incorrect SPNs.
  • If SCOM is running on Windows 2003 SP1 and uses SQL 2005, we can also check the “SynAttackProtect” TCP registry as mentioned in the blog article below:
  • Before making the above registry change, we need to ensure that we are getting System.Data.SQLClient.SQLException from Operations Manager event viewer logs. Event ID: 26380
  • If System Center Operations Manger 2007 R2 Authoring console is installed on System Center Operations Manager 2007 SP1 RMS or if there are errors related to assembly in event viewer, please check this article:
  • Verify if the port numbers are same across the following registry key and SQL Server configuration manager settings for the SQL instance.
  • Registry Key Location: HKLM\Software\Microsoft\Microsoft Operations Manager\3.0\Setup\
    Check the “DatabaseServerName” key information.
    Match it with the port number specified in SQL Configuration manager for SQL instance. Both should be same.
  • Ensure that we are able to open SCOM Console on SCOM server.
  • Check for any handler or access denied errors in event viewer. If yes, then the SDK account might not have permissions on “Services Configuration” or SCOM installation directory.If starting a sdk service gives time out error, we can consider increasing the timeout for the sdk service –

No comments:

Post a Comment

You might find these articles useful