How to re-link SCOM 2007 to its SCOM Database

Someone had uninstalled the MSSQL 2005 hosting the SCOM database. The only database file I had is the SCOM LDF & MDF database file. I had re-installed the SQL Server but SCOM console still cannot reconnect back to it. Any help would be greatly appreciated.
LVL 1
anekyAsked:
Who is Participating?
 
Batuhan CetinCIOCommented:
System Center Management, System Center Data Access, and System Center Management Configuration services must exist in your root management server. If they don't exist, you have a bigger problem than pointing to the database.

May be a silly question but are you sure you looked at services.msc on your root management server for these services?

Did you verify the registry key I also stated in step 1 on all management servers ?
0
 
Batuhan CetinCIOCommented:
Here, apply these steps and you'll be fine:

http://technet.microsoft.com/en-us/library/cc540384.aspx

This article describes how to move a SCOM database. As your SCOM lost connection to its DB, I recommend you to apply this and repoint your SCOM to its database from scratch for maximum reliability.
0
 
anekyAuthor Commented:
The issue I have is I cannot access the SCOM console at all to do the following suggested in technet. It kept give me the following error

Failed to connect to server "servername.domain.com" Sdk Service has not yet initialized. please retry

Additional Information:

Microsoft.EnterpriseManagement.Common.SdkServiceNotInitializedException: Sdk Service has not yet initialized. Please retry
   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(String serverName)
   at Microsoft.EnterpriseManagement.ManagementGroup.Connect(String serverName)
   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Common.ManagementGroupSessionManager.Connect(String server)
   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleWindowBase.TryConnectToManagementGroupJob(Object sender, ConsoleJobEventArgs args)


The things I had check is the OpsMgr SDK service is running. I had stop and restart the service the issue still persist. Any help will be welcome
0
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

 
Batuhan CetinCIOCommented:
Can you tell me does the server have the same name, was it renamed during all of this? Was it formatted or only the SQL Server is removed from from the machine? If formatted and rebuilt, does it by chance have a new AD machine account?

When you look at the registry on the RMS does it have the correct value in the  key mentioned here in the KB

1. Under HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Setup, double-click the value DatabaseServerName, and then change the value to the hostname of the SQL Server-based computer now hosting the OperationsManager database.
 
2. After you have completed this step on all management servers in the management group, restart the System Center Management, System Center Data Access, and System Center Management Configuration services on the root management server, and then restart only the System Center Management service on the remaining management servers
0
 
anekyAuthor Commented:
The server hostname wasn't change at all. Only the SQL 2005 was uninstalled. I only find remnants of the SCOM database with file extension of ldf and mdf. I believe it done by a disgruntle ex-it employee and this mess was left for me to clear.

What I did was reinstall the SQL server and load the SCOM database the database with ldf and mdf. But the SCOM console still unable to connect to it.
0
 
Batuhan CetinCIOCommented:
Did you take the steps I described above?

1. Under HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft Operations Manager\3.0\Setup, double-click the value DatabaseServerName, and then change the value to the hostname of the SQL Server-based computer now hosting the OperationsManager database.
 
2. After you have completed this step on all management servers in the management group, restart the System Center Management, System Center Data Access, and System Center Management Configuration services on the root management server, and then restart only the System Center Management service on the remaining management servers
0
 
anekyAuthor Commented:
I only see the following service installed and running in the server Ops Manager Audit Forwarding Service & Ops Health Manager. The SCM, SCDA and SCMC are not there at all.
0
 
anekyAuthor Commented:
I decide to uninstall the SCOM and SQL and redo it all over again.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.