After our upgrade-in-place to SCSM 2012 Data Warehouse (seperate dedicated server but a shared database server environment) all of our report jobs would show as “Running” and would never complete. They weren’t enabled either. After researching this, it’s a normal state, but my reports were failing with a “no date selected” error. Below are the high level steps we followed to eventually overcome the problem:
- Either rename or delete the SCSM 2010 databases – DWStagingAndConfig, DWRepository, DWDataMart. You can also create new databases during the installation process and achieve the same results.
- Delete these registry keys before every SCSM 2012 DW installation attempt – (HKLM\Software\Microsoft\Microsoft Operations Manager and HKLM\Software\Microsoft\System Center)
- Install the previous installation encryption key.
- Run the SCSM 2012 Data Warehouse installation process as normal BUT skip installing the OM and CM databases.
- Register the SPN (see below).
After upgrading our SCSM 2012 management server, we could not install the data warehouse. My first troubleshooting stop was this Technet (eerily similar to Skynet when you say it out loud) article, which called for using new SCSM 2012 cmdlets.
To use these cmdlets, you must add them to your powershell script. This article details the difference between the SCSM 2010 and SCSM 2012 cmdlets. You’ll need to run these from your warehouse server.
I know my reporting server is working, since I can get to the url – http://Server FQDN/Reports/Pages/Folder.aspx but I coudn’t fix the running jobs. Reports failed and cubes were not working.
After a few days of troubleshooting, the team decided to rebuild our data warehouse server and start from scratch. We didn’t, however, delete our old databases (DWStagingAndConfig, DWRepository, DWDataMart) from the separate SQL 2008 R2 server.
Our fist error during the installation on the rebuilt server was the “createMomregkey” error. Deleting some reg keys (HKLM\Software\Microsoft\Microsoft Operations Manager and HKLM\Software\Microsoft\System Center) with an installation of the saved encyption key fixed that.
Then we hit the “SMScript” error and could not get around it.
So, two PSA tickets later (one for cubes and one for the warehouse), we solved the problem by…
- Created new DW databases (you can try it with your existing DW databases, but I’m seeing a number of posts about missing criteria on the reports).
- Skipped the installation of the Ops Manager and Config Manager databases (you can do that later).
- Created an SPN. Make sure you have correct SPN’s for the servers and databases using the service account for your SCSM data warehouse install. The SCSM data warehouse process should do this, but it appears to fail during some installs. This link walks you through the process. Kerberos errors kill any install until the SPN is registered correctly.
If successful, you can then register your warehouse via the SCSM console. The first data house job you’ll see is the “MPSYNCJOB.” This will start running and other jobs will install as management packs are loaded and synchronized. Process will have a state of “Running” or “Not Started,” so don’t panic if you don’t see a “Completed” status.
Hope this helps. If not, throw me a comment.