Sign in
 
Home2012Previous VersionsLibraryForumsGallery
System Center TechCenter > System Center - Operations Manager Forums > Operations Manager - General > SLA Dashboard v2 MSI 'Wizard ended prematurely'

Answered SLA Dashboard v2 MSI 'Wizard ended prematurely'

    •  
      Wednesday, August 12, 2009 3:47 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      So, I'm trying to install SLA Dashboard v2 on a MOSS 2007 SP2 instance and it's giving me this error near the end. I've done this succesfully on another farm, so I thought I understood the process, but I'm not finding much in event viewer (status 1603 when MSI fails to install) and I can't find any log files from the MSI to point me in direction to a fix.

      I've made the Application Pool Identity a local admin on OpsMgr Data Warehouse temporarily (that was necessary in my first successful install).

      The validation checks all succeed and the MSI lets me get to the Install option and I can see the following progress strings:

      * Something about creating SLD Database
      * Executing SQL
      * Installing Site templates

      The progress strings update rapidly, so I may not have them all... but it FAILS right after 'Installing Site template' shows up with 'Service Level Dashboard 2.0 Setup Wizard ended prematurely'.

      In the event viewer, I have an entry for MsiInstaller, Event ID 1033. "Windows Installer installed the product. Product Name: Service Level Dashboard 2.0. Product Version: 6.1.7220.0. Product Language: 1033. Installation success or error status: 1603."

      Any ideas where to look for more information on a resolution?

      gaurhoth
       

    Answers

    All Replies

    • Wednesday, August 12, 2009 5:53 PM
      Moderator
       
       
      Sign In to Vote
      1
      Sign In to Vote
      Hi.

      Try to run it with these parameters: msiexec /i serviceleveldashboard_x86.msi /L*V install.log and check that log for errors. Also a log file can be found here:  c:\program files\service level dashboard v2.0\logs\dashboard.log file. 
      Best regards, Marnix Wolf

       

      (Thoughts on OpsMgr)
       
    • Tuesday, September 08, 2009 9:05 AM
       
       Proposed Answer Has Code
      Sign In to Vote
      0
      Sign In to Vote
      Hi there.

      I face the same problem in my infrastructure. Unfortunately there is no dashboard.log file left, when the rollback is complete. But verbose MSI-Logging brought up this:

      SCRUM - Language: 1033 - Site Template: _GLOBAL_#2 - Template Id: 11254
     Scrum for Team System

ServiceLevelDashboard - Language: 1033 - Site Template: _GLOBAL_#5 - Template Id: 1

VSTS_MSF_CMMI - Language: 1033 - Site Template: _GLOBAL_#1 - Template Id: 1

VSTS_MSFAgile - Language: 1033 - Site Template: _GLOBAL_#0 - Template Id: 1

MSI (s) (CC!90) [09:53:44:756]: Closing MSIHANDLE (86) of type 790531 for thread 8592
MSI (s) (CC!90) [09:55:18:701]: Creating MSIHANDLE (87) of type 790531 for thread 8592
Die IIS-Website wurde mit Windows SharePoint Services erweitert, aber w„hrend der Erstellung der Standardwebsite "http://po01:51918/" ist der folgende Fehler aufgetreten. Korrigieren Sie die Eingabe, und versuchen Sie erneut, die Standardwebsite zu erstellen. Fehler: Ungltige Datei oder Argumente fr Webvorlage '_GLOBAL_#5'.

      The question is, do I get this error because I have the german Office Server installed?
      There are some other errors in the log, but these may be "ok", as the msi just stops (and rollbacks) at the above mentioned point.

      Another question: the mentioned "Application Pool Identity", what account is that exactly? We have seperate accounts for the MySite, Portal, Central Administration and so on. Which one is the one I need to make admin on the SQL Machine?

      Thanks in advance,
      Christoph
      Christoph Schmidt || IT Consultant || Germany || MCITP Enterprise Administrator
       
    • Tuesday, September 15, 2009 10:18 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hi,

      <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-alt:"Calisto MT"; mso-font-charset:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-alt:"Times New Roman"; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} @font-face {font-family:"Trebuchet MS"; panose-1:2 11 6 3 2 2 2 2 2 4; mso-font-alt:Arial; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:647 0 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} span.EmailStyle15 {mso-style-type:personal; mso-style-noshow:yes; mso-style-unhide:no; mso-ansi-font-size:10.0pt; mso-bidi-font-size:11.0pt; font-family:"Trebuchet MS","sans-serif"; mso-ascii-font-family:"Trebuchet MS"; mso-hansi-font-family:"Trebuchet MS"; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi; color:blue;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} -->

      Did you troubleshooted this issue, if so please share the workaround.

       

      Thanks,


       
    • Tuesday, October 13, 2009 7:32 AM
       
       Proposed Answer
      Sign In to Vote
      0
      Sign In to Vote
      No luck yet. Tested again in a clean testlab (german Sharepoint) ... no luck. I really think the setup wasn't tested on localized Sharepoints... I'd be really happy if someone would find a way through this. I already spent hours tweaking the msi without any luck...
      Christoph Schmidt || IT Consultant || MCITP EA || LinkedIn: http://www.linkedin.com/in/schmidtchristoph || XING: http://www.xing.com/profile/Christoph_Schmidt59
      • Proposed As Answer by Lourh Friday, October 30, 2009 4:01 PM
      •  
       
    • Friday, October 30, 2009 4:05 PM
       
       Proposed Answer
      Sign In to Vote
      1
      Sign In to Vote
      Hi,

      I have the same issue. As a workground, I  installed  SLA dashboard using an account that have  db-owner on both sharepoint Databases (config and admin)
      Lourh
       
    • Saturday, October 31, 2009 9:05 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hi Lourh,

      I'll test that and report back next week. Thanks for your insights.

      Christoph
      Christoph Schmidt || IT Consultant || MCITP EA || LinkedIn: http://www.linkedin.com/in/schmidtchristoph || XING: http://www.xing.com/profile/Christoph_Schmidt59
       
    • Monday, November 02, 2009 8:37 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      This is what I did,

      Go to command prompt and execute
      msiexec /i serviceleveldashboard_x86.msi /L*V install.log

      If the installation fails, it will generate install.log file

      I noticed that when the installer tries to execute "Adding Site Template" I got hit with an error. Took a quick look ath the log file and it gives me the Access Denied.

      Action 16:16:59: ADDSITETEMPLATE. Adding Site Template...
      MSI (s) (3C:F0) [16:16:59:113]: Executing op: CustomActionSchedule(Action=ADDSITETEMPLATE,ActionType=1025,Source=BinaryData,Target=CAQuietExec,CustomActionData="C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\BIN\STSADM.EXE" -o addtemplate -filename "C:\Program Files\Service Level Dashboard 2.0\SLD_SiteTemplate.stp" -title ServiceLevelDashboard)
      MSI (s) (3C:D0) [16:16:59:118]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI69E8.tmp, Entrypoint: CAQuietExec
      CAQuietExec: 
      CAQuietExec:  Access denied.

      Tried my luck and use the Run as Administrator option. It works. My SLA Dashboard is successfully installed

       
    • Tuesday, December 08, 2009 2:52 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      I really cannot find any evidence that this is a permission problem. I tried this on a german x86 and a x68 Sharepoint with no luck. Here is my log, maybe I overlook something and you can proove me wrong.

      It was too big to put it in here, so I made it available on my SkyDrive <HERE>.

      Again, thanks to everyone who takes his/her time to look into this! Let me donate you a coffee if you can help ;)

      With kind regards
      Christoph
      Christoph Schmidt || IT Consultant @ TOP TECHNOLOGIES CONSULTING || MCITP EA || My Blog || LinkedIn || XING
       
    • Wednesday, January 06, 2010 1:55 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote

      I finally gave up waiting for a solution here.

      For everyone still with this problem: grab a suitable server, install the Windows Sharepoint Services (english version of course) on it and install the Service Level Dashboard. I should have done that a lot earlier as it would have saved me so much time.

      Christoph Schmidt || IT Consultant @ TOP TECHNOLOGIES CONSULTING || MCITP EA || My Blog || LinkedIn || XING
       
    • Monday, February 08, 2010 7:35 PM
      Moderator
       
       
      Sign In to Vote
      0
      Sign In to Vote
      No activity for 30 days. I will close the thread now. Feel free to re-open it.
      Anders Bengtsson | Microsoft MVP - Operations Manager | http://www.contoso.se
       
    • Saturday, February 26, 2011 12:45 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      I too had this error.  I ran verbose logging and it gave error that I had given the wrong password.  I knew I had put in the correct password, so I dug a little deeper and then realized that it was probably the special characters in the passwords it didn't like (assume the " character).  They apparently didn't do any error handling, but what can you expect from a free application? :)  I reset password and magic!

       

      I was simply using my domain admin account (same account in installed WSS with) to install and a normal service account for the application pool (no special rights). 

       

      Hope that helps someone.

       

       
    • Thursday, June 16, 2011 3:17 PM
       
       Proposed Answer
      Sign In to Vote
      1
      Sign In to Vote
      Had the same issue as the OP. I ran the installer (using msiexec /i serviceleveldashboard_x86.msi /L*V install.log) under a command prompt w/ admin rights, and the install completed doing that.
      • Proposed As Answer by Seth Steward Thursday, August 11, 2011 9:54 PM
      •  
       
    • Wednesday, September 07, 2011 12:49 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Had the same issue as the OP. I ran the installer (using msiexec /i serviceleveldashboard_x86.msi /L*V install.log) with an admin account  and also enable webdav , and the install completed doing that.Also