Support Tip: OpsMgr 2012 SP1 upgrade fails with error "Failed to set DW upgrade scenario"

Support Tip: OpsMgr 2012 SP1 upgrade fails with error "Failed to set DW upgrade scenario"

  • Comments 2
  • Likes

Satish Phatge | Senior Support Engineer

imageHere’s a quick tip that might help you out when upgrading to System Center 2012 Operations Manager (OpsMgr 2012) Service Pack 1 (SP1).

When performing an upgrade to OpsMgr 2012 SP1, the upgrade process fails with the following error:

Failed to set DW upgrade scenario: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: Cannot open database "OperationsManagerDW" requested by the login. The login failed.

This can occur if there is an invalid Data Warehouse server name or SRS database instance name in the registry on the Management Server.

To resolve this, verify that the correct Data Warehouse server name and SRS database instance name exist in the registry on the Management Server:

Data Warehouse server name:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup\DatawarehouseDBServerName

NOTE: This is a DWORD value and is the NetBIOS name or FQDN of the server.

SRS database instance name:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Reporting\SRSInstance

NOTE: The default SQL instance name is MSSQLSERVER but may be different in your environment if using a named instance.

Once this is done try the upgrade again. If this was our issue then the upgrade should complete as expected.

Satish Phatge | Senior Support Engineer | Microsoft GBS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/
System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/
System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/
System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/
System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Windows Intune: http://blogs.technet.com/b/windowsintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The AD RMS blog: http://blogs.technet.com/b/rmssupp/

App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Hi wrote a similiar post some time ago you might want to link it also

    blog.scomfaq.ch/.../scom-2012-sp1-unable-to-proceed-setup-install-error

    Cheers,

    Stefan

  • Most of time two regs for DW are missing:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup\DatawarehouseDBServerName

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup\DatawarehouseDBName

    In my case both were missing. Then it is good idea to follow Stefan's link like suggested :)