During a recent deployment of System Center Operations Manager 2012 SP1, I ran into an installation failure that occurred during the data warehouse creation process. This particular implementation resides on Windows Server 2012 and utilizes a SQL 2012 instance, and only occurs on SCOM 2012 with SP1.
The error text, as retrieved from the Application error log:
"CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file 'E:DATA.mdf'."
After doing a little digging, I found this to be a bug in the SCOM 2012 SP1 installer. It seems the Data Warehouse installer function is attempting to install the database as the same name as the top level folder specified in the installer. For example, if you chose "E:Data" for the Data Warehouse installation folder, it will attempt to install the Data Warehouse database as "E:Data.mdf" instead of "E:DataOperationsManagerDW.mdf".
Fortunately, there is a relatively simple workaround; by modifying "E:Data" and "E:Logs" in the database installation paths, the problem can be overcome. Add "OperationsManagerDW" (or the name of your database) to the end of "Data File Folder" and "Log File Folder" as seen below:
After adjusting the folders accordingly, the installation will complete successfully. The folder structure will look like the following:
The OperationsManagerDW folder can be deleted after the installation completes, as the OperationsManagerDW.mdf database file will appear next to the other databases shown above.