To develop a locally available OpsMgr environment on my laptop, I recently installed OpsMgr 2012 SP1 on an all-in-one configuration running on Windows Server 2012 and using SQL Server 2012 (hey, if you are going to build an all-in-one for something might as well try the latest and greatest of everything!). I was attempting the installation with default values with the exception of where the OperationsManager and OperationsManagerDW database and log files were being stored. I received the following error on multiple attempts at installation:


Digging through the installation file indicated that there was a problem attempting to create a file called data.mdf on the F:\ path (the directory where my data files were going to be added for these databases.

The error in the log is below:

EXEC(@sql);: Threw Exception.Type: System.Data.SqlClient.SqlException, Exception Error Code: 0x80131904, Exception.Message: CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file ‘F:\DATA.mdf’.

Interestingly it worked for the Operations Manager database (as you can see since it went past the Operational database configuration), but not for the Data Warehouse configuration. There are some interesting results from installing the Operations Manager data warehouse with a fresh installation from the SP1 media that it creates the database and log file for the DW with a blank name. Both Marnix and Bob have blogged on this at: and

To work around this issue I installed the OperationsManager and OperationsManagerDW databases to the default location and used the process to rename and relocate the OperationsManagerDW files discussed in Bob’s article above.

Summary: Failing on the Data warehouse configuration on a fresh installation of Operations Manager 2012 SP1? Try installing to the default paths and moving the database and log files after the installation has completed.