Install of SCOM F5 Man Pack 1.6.2.311 fails

John,

 

 

It looks like your data warehouse may have been moved at some point -- is that the case?

 

 

I have a couple diagnostics you can run and hopefully a fix as well. You will need to run some SQL queries against the Operations Manager database:

 

 

1. Open SQL Server Management Studio

 

2. Connect to the Operations Manager operational database server

 

3. Expand the databases to the OperationsManager database and select that database

 

4. Click the "New Query" button in the top left

 

5. Paste the following queries into the window and then click "Execute":

 

 

 

-- Get the global setting

 

select SettingValue

 

from globalsettings G

 

join managedtypeproperty MTP on G.managedtypepropertyid = MTP.managedtypepropertyid

 

join managedtype MT on MTP.managedtypeid = MT.managedtypeid

 

where typename = 'Microsoft.SystemCenter.DataWarehouse'

 

and ManagedTypePropertyName = 'MainDatabaseServerName'

 

 

-- Get the instance setting

 

select MainDatabaseServerName_16781F33_F72D_033C_1DF4_65A2AFF32CA3 from MT_DataWarehouse

 

 

 

I'm guessing that the second query will return the correct data warehouse server and that the first query will be empty or wrong. To correct the first value (if it is wrong), stop the SCOM services (System Center Data Access, System Center Management, System Center Management Configuration) and then run this query in the same way as the previous queries:

 

 

 

update GlobalSettings

 

set SettingValue = 'CORRECT DATA WAREHOUSE SERVER NAME HERE'

 

from globalsettings G

 

join managedtypeproperty MTP on G.managedtypepropertyid = MTP.managedtypepropertyid

 

join managedtype MT on MTP.managedtypeid = MT.managedtypeid

 

where typename = 'Microsoft.SystemCenter.DataWarehouse'

 

and ManagedTypePropertyName = 'MainDatabaseServerName'

 

 

 

Please send the results of the first two queries as this will help improve our product.