attachments/jcowan/media/windowslivewriter/opsmgr2012sp1workaroundfreshinstallresul_11291/clip_image002_thumb.jpg

OpsMgr 2012 SP1: Workaround – Fresh Install results in blank OperationsManagerDW Data and Log File Names (mdf and ldf)

I’m noticing this in every OpsMgr 2012 SP1 environment where there is a fresh new build and thought I’d give you all a heads up with a quick workaround.

This may be related to why you cannot deploy the DW to a non-default SQL Data and Log file location noted here:

http://blogs.catapultsystems.com/jcowan/archive/2013/03/07/opsmgr-2012-sp1-cannot-install-opsmgr-due-to-operationsmanagerdw-database-files-in-a-non-default-location-for-user-databases-error-code-0x80131500.aspx?utm_source=OpsMgr2012Pipe&utm_medium=Twitter

In SQL Management Studio the File Name under DB\Properties\Files only shows mdf and ldf, no File Name. 

I also used Windows Explorer and found the same thing.  A blank file name…

Workaround:

  1. Backup all DB’s
  2. Stop OpsMgr Services to the DB instance
  3. Note the path of the OperationsManagerDW
  4. From SQL Server Management Studio, Detach the OperationsManagerDW
  5. Browse to the mdf and ldf via Windows Explorer
  6. Rename the files with the correct file names (OperationsManagerDW.mdf, OperationsManagerDW.ldf)
  7. From SQL Server Management Studio, Re-Attach the OperationsManagerDW
  8. Restart OpsMgr Services to the DB instance

clip_image002

3 Comments

  1. Jawm May 21, 2013
  2. Giovani July 26, 2013
  3. Vivekanand July 29, 2013

Leave a Reply