Upgrade to SCOM 2012 R2: Unable to proceed

 

The upgrade time has truly come!

 

During an upgrade at a costumer site I got the following error when trying to upgrade the secondary management server:

 

Unable to Proceed

Setup could not detect the current Data Warehouse Scenario. Please ensure that the SQL Server service for the Data Warehouse is running, and the current user has permission to access the Data Warehouse.

 

clip_image002

 

I checked the services and I had already upgraded the RMS emulator server so i was sure it wasn’t a permission issue.

 

Time to dig a little deeper…

 

I start by firing up the SMS Trace to view the OpsMgrSetupWizard.log (located in %LocalAppData%\SCOM\Logs). Even a good old fashioned pirate with one eye would see the red lines:

 

clip_image004

 

The obvious error here is: “Error: DW DB name is null or empty”. The first place that came to my mind here was the registry, so I checked HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup where this stuff is listed.

 

And sure enough! The DataWarehouseDBName and DataWarehouseDBServerName were both empty:

 

clip_image006

 

Pretty fixable – I simply put in the database and server name:

 

clip_image008

 

I crank up the installer again and this time SCOM isn’t complaining:

 

clip_image010

 

Happy upgrading to SCOM 2012 R2 – see you on the bright side


Comments (5):

  1. adelaide hills b…

    Coretech Blog » Blog Archive » Upgrade to SCOM 2012 R2: Unable to proceed

  2. dog day care adelaide

    Coretech Blog » Blog Archive » Upgrade to SCOM 2012 R2: Unable to proceed

  3. Kiki says:

    Great
    10x

  4. LvilleSystemsJockey says:

    Perfect, saved me lots of time!

  5. TorATB says:

    Thank you very much!

Leave a Reply