SCOM 2007 R2 Service Level Dashboard

My company uses SCOM 2007 and recently upgraded to R2, which provides a whole host of new features like linux support and Service Level Dashboards. Walter Eikenboom has some great SCOM related posts and one on this feature.

If you read the release notes, SharePoint MUST be a local install, can't do remote yet.

I was brought in to install the dashboard on our staging environment where it was installed in the past, but somehow it was removed. The install package can't handle this, so I thought I would write up how I solved. This post is about the RC1 version of the dashboard from May 2009 http://www.microsoft.com/downloads/details.aspx?FamilyId=1d9d709f-9628-46a8-952b-a78f5dd2bdd9&displaylang=en. I exported the SQL install script from the .mp file; use at your own risk, I haven't tested.

On install you just get an error "Service Level Dashboard 2.0 Setup Wizard ended prematurely because of an error." and no log files or helpful messages anywhere. Luckily this is a MSI installer and MSIExec has great logging capabilities that you have to manually run from a command prompt window. Below are the steps and how I solved:

I turned on msiexec logging:

C:\SCOM Installer\Service Level Dashboard 2.0>msiexec /i ServiceLevelDashboard_x
86.msi /l* Install.log

Digging through the log file near the end I found this:

Action 12:13:17: ADDOPSMGRUSERTOWPG2003. Adding account to worker process group...
CAQuietExec:  System error 1378 has occurred.
CAQuietExec: 
CAQuietExec:  The specified account name is already a member of the local group.
CAQuietExec: 
CAQuietExec:  Error 0x80070002: Command line returned an error.
CAQuietExec:  Error 0x80070002: CAQuietExec Failed
Action 12:13:17: ADDSITETEMPLATE. Adding Site Template...
CAQuietExec: 
CAQuietExec:  Web template with file SLD_SiteTemplate.stp already exists.
CAQuietExec: 
CAQuietExec:  Error 0xffffffff: Command line returned an error.
CAQuietExec:  Error 0xffffffff: CAQuietExec Failed

Looks like they didn’t account for account already being there and site template already exists.

I removed accounts from iis_wpg and wss_wpg in Local Users and Groups in Computer Management. Next I re-ran the uninstall steps (they are in log file, but don’t seem to be executed by installer).

Property(S): ROLLBACKSITETEMPLATE = "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\BIN\STSADM.EXE" -o deletetemplate -title ServiceLevelDashboard
Property(S): ROLLBACKEXTENDVS = "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\BIN\STSADM.EXE" -o unextendvs -url http://BLV21WMOSS02:5555 -deletecontent -deleteiissites
Property(S): ROLLBACKIISRESETEXTENDVS = "iisreset"
Property(S): ROLLBACKSOLUTION = "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\BIN\STSADM.EXE" -o deletesolution -name SLD_Solution.wsp -override
Property(S): EXECADMSVCROLLBACKSOLUTION = "C:\Program Files\\Common Files\microsoft shared\Web Server Extensions\12\BIN\stsadm.exe" -o execadmsvcjobs
Property(S): ROLLBACKDEPLOYSOLUTION = "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\BIN\STSADM.EXE"  -o retractsolution -name SLD_Solution.wsp -url http://BLV21WMOSS02:5555 -immediate
Property(S): EXECADMSVCROLLBACKDEPLOYSOLUTION = "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\BIN\STSADM.EXE" -o execadmsvcjobs

Some of the steps fail, but most work. Once I removed all the offending existing components, installation went just fine. It should take a few minutes to install and see another temporary cmd window pop up for deploying the site. Follow the setup instructions in the download from there to configure. It will come up with a blank site with only the setup account having rights to it.

Update: Sometimes it seems the procs are not created properly. Follow help on this post for recreating the procs: http://social.technet.microsoft.com/Forums/en/operationsmanagermgmtpacks/thread/4b67aa58-8edf-4c67-94fa-8e085ee696c5

If you are uninstalling, there is a sql job that is created to delete stale entries from the SLDSessions. Make sure to manually delete this job.