OperationsManager Database Connectivity Issues After Migration

I was tasked with migration an OperationsManager database off to another SQL server on an SQL Instance other than the default “SQLSERVER” instance. I following the TechNet article to perform the migration but was receiving various database connectivity errors in the Operations Manager log on my RMS. Examples of errors occurring for me are below:

Sponsors, article continues below...

Log Name: Operations Manager
Source: Health Service Modules
Date: 10/25/2010 5:08:33 PM
Event ID: 11852
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: RMS01.domain.pvt
Description:
OleDb Module encountered a failure 0x80004005 during execution and will post it as output data item. Unspecified error
: [DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid connection.

Workflow name: Microsoft.SystemCenter.SqlBrokerAvailabilityMonitor
Instance name: RMS01.domain.pvt
Instance ID: {A851F280-FDAE-C8B0-79EC-FF7F12070A65}
Management group: NA

Log Name: Operations Manager
Source: Health Service Script
Date: 10/25/2010 5:39:13 PM
Event ID: 100
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: RMS01.domain.pvt
Description:
PartitioningAndGroomingMonitor.vbs : Script executed with Error Number: -2147467259 Error Details: [DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid connection.

Log Name: Operations Manager
Source: Health Service Script
Date: 10/25/2010 5:39:13 PM
Event ID: 100
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: RMS01.domain.pvt
Description:
DetectDuplicateRelAgnToSrvMonitor.vbs : Script executed with Error Number: -2147467259 Error Details: [DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid connection.

It turns out I was required to specify the instance name along with the SQL server name in two locations after performing the DB migration. The TechNet documentation specifies it in one area but neglects to mention it for another.

1) Add SQLSERVER\SQLINSTANCE to registry string value DatabaseServerName under key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup\DatabaseServerName.

2) Add SQLSERVER\SQLINSTANCE to column name SQLServerName_6B1D1BE8_EBB4_B425_08DC_2385C5930B04 in table dbo.MT_ManagementGroup in database Operations Manager.

After that I bounced the System Center Data Access, Management and Management Configuration services. Then I started to receive successful events for the scripts that were failing before. You can see examples of successful script executions below:

Log Name: Operations Manager
Source: Health Service Script
Date: 10/25/2010 5:46:07 PM
Event ID: 100
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: RMS01.domain.pvt
Description:
PartitioningAndGroomingMonitor.vbs : Script executed with Process Succeed Count 3

Log Name: Operations Manager
Source: Health Service Script
Date: 10/25/2010 5:46:07 PM
Event ID: 100
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: RMS01.domain.pvt
Description:
DetectDuplicateRelAgnToSrvMonitor.vbs : Script executed with Duplicate Records Count 0

This entry was posted in Microsoft, SCOM.

One Response to OperationsManager Database Connectivity Issues After Migration

  1. Ronald says:

    Having a slight issue with nr. 2 .. how to do this?

Leave a Reply