locked
Failing at "Installing MOM Reporting Services" on Reporting Database Server RRS feed

  • Question

  • 3 - server topology - all servers are implemented.  Just waiting to complete the install on the Reporting Database Server. 

    I keep getting failing at the first step - something like - "MOM installing Reporting".

     

     

    Here is my log, does anyone have any input?  (I REMOVED A LOT OF THE EXTRA STUFF IN THE MOMREPORTLOG.  AS I THOUGHT IT WAS NOT-NEEDED.  PLEASE LET ME KNOW IF IT IS).

     

     

     

    === Verbose logging started: 10/26/2010  11:55:23  Build type: SHIP UNICODE 4.00.6001.00  Calling process: C:\Windows\system32\msiexec.exe ===
    MSI (c) (E4:2C) [11:55:23:759]: Resetting cached policy values
    MSI (c) (E4:2C) [11:55:23:759]: Machine policy value 'Debug' is 0
    MSI (c) (E4:2C) [11:55:23:759]: ******* RunEngine:
               ******* Product: d:\forefront source\Server\MOMReporting.msi
               ******* Action:
               ******* CommandLine: **********
    MSI (c) (E4:2C) [11:55:23:760]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (E4:2C) [11:55:23:760]: Grabbed execution mutex.
    MSI (c) (E4:2C) [11:55:23:774]: Cloaking enabled.
    MSI (c) (E4:2C) [11:55:23:774]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (E4:2C) [11:55:23:780]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (58:20) [11:55:23:783]: Grabbed execution mutex.
    MSI (s) (58:3C) [11:55:23:784]: Resetting cached policy values
    MSI (s) (58:3C) [11:55:23:784]: Machine policy value 'Debug' is 0
    MSI (s) (58:3C) [11:55:23:784]: ******* RunEngine:
               ******* Product: d:\forefront source\Server\MOMReporting.msi
               ******* Action:
               ******* CommandLine: **********
    MSI (s) (58:3C) [11:55:23:784]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (58:3C) [11:55:23:792]: SRSetRestorePoint skipped for this transaction.
    MSI (s) (58:3C) [11:55:23:792]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
    MSI (s) (58:3C) [11:55:23:793]: File will have security applied from OpCode.
    MSI (s) (58:3C) [11:55:23:803]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'd:\forefront source\Server\MOMReporting.msi' against software restriction policy
    MSI (s) (58:3C) [11:55:23:803]: SOFTWARE RESTRICTION POLICY: d:\forefront source\Server\MOMReporting.msi has a digital signature
    MSI (s) (58:3C) [11:55:23:831]: SOFTWARE RESTRICTION POLICY: d:\forefront source\Server\MOMReporting.msi is permitted to run at the 'unrestricted' authorization level.
    MSI (s) (58:3C) [11:55:23:831]: End dialog not enabled
    MSI (s) (58:3C) [11:55:23:831]: Original package ==> d:\forefront source\Server\MOMReporting.msi
    MSI (s) (58:3C) [11:55:23:831]: Package we're running from ==> C:\Windows\Installer\303f23f.msi
    MSI (s) (58:3C) [11:55:23:835]: APPCOMPAT: looking for appcompat database entry with ProductCode '{63C847C6-07A0-4A6F-8A78-8A066C9F9773}'.
    MSI (s) (58:3C) [11:55:23:835]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (58:3C) [11:55:23:838]: MSCOREE not loaded loading copy from system32
    MSI (s) (58:3C) [11:55:23:840]: Machine policy value 'TransformsSecure' is 1
    MSI (s) (58:3C) [11:55:23:840]: Machine policy value 'DisablePatch' is 0
    MSI (s) (58:3C) [11:55:23:840]: Machine policy value 'AllowLockdownPatch' is 0
    MSI (s) (58:3C) [11:55:23:840]: Machine policy value 'DisableLUAPatching' is 0
    MSI (s) (58:3C) [11:55:23:841]: Machine policy value 'DisableFlyWeightPatching' is 0
    MSI (s) (58:3C) [11:55:23:841]: APPCOMPAT: looking for appcompat database entry with ProductCode '{63C847C6-07A0-4A6F-8A78-8A066C9F9773}'.
    MSI (s) (58:3C) [11:55:23:841]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (58:3C) [11:55:23:841]: Transforms are not secure.
    MSI (s) (58:3C) [11:55:23:842]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\Program Files\Microsoft Forefront\Client Security\Server\Logs\MOMReporting.log'.
    MSI (s) (58:3C) [11:55:23:842]: Command Line: ROSETTA_SERVER=DC1FFMGMT01 SQLSVR_INSTANCE=DC1FFRPT01 TASK_USER_ACCOUNT=apmffadmin TASK_USER_PASSWORD=********** TASK_USER_DOMAIN=apm REPORTING_USER=apmffadmin REPORTING_PASSWORD=********** REPORTING_DOMAIN=apm MOM_DB_SERVER=DC1FFMGMT01 INSTALLDIR=C:\Program Files\Microsoft Forefront\Client Security\Server\Reporting REPORT_SERVER_VDIR=ReportServer REPORT_MANAGER_VDIR=Reports HttpConnectionType=http:// DB_SIZE=184320 AUTOMATICALLY_DETECT_ROSETTA_VDIRS=0 CURRENTDIRECTORY=D:\Forefront Source\AUTORUN CLIENTUILEVEL=3 CLIENTPROCESSID=3812
    MSI (s) (58:3C) [11:55:23:842]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{F51B3310-5805-4174-86B8-AF0013E818DD}'.
    MSI (s) (58:3C) [11:55:23:842]: Product Code passed to Engine.Initialize:           ''
    MSI (s) (58:3C) [11:55:23:842]: Product Code from property table before transforms: '{63C847C6-07A0-4A6F-8A78-8A066C9F9773}'
    MSI (s) (58:3C) [11:55:23:842]: Product Code from property table after transforms:  '{63C847C6-07A0-4A6F-8A78-8A066C9F9773}'
    MSI (s) (58:3C) [11:55:23:842]: Product not registered: beginning first-time install
    MSI (s) (58:3C) [11:55:23:842]: Product {63C847C6-07A0-4A6F-8A78-8A066C9F9773} is not managed.
    MSI (s) (58:3C) [11:55:23:842]: MSI_LUA: Credential prompt not required, user is an admin
    MSI (s) (58:3C) [11:55:23:842]: PROPERTY CHANGE: Adding ProductState property. Its value is '-1'.
    MSI (s) (58:3C) [11:55:23:842]: Entering CMsiConfigurationManager::SetLastUsedSource.
    MSI (s) (58:3C) [11:55:23:842]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (58:3C) [11:55:23:842]: Adding new sources is allowed.
    MSI (s) (58:3C) [11:55:23:842]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.
    MSI (s) (58:3C) [11:55:23:843]: Package name extracted from package path: 'MOMReporting.msi'
    MSI (s) (58:3C) [11:55:23:843]: Package to be registered: 'MOMREPORTING.MSI'
    MSI (s) (58:3C) [11:55:23:843]: Note: 1: 2262 2: AdminProperties 3: -2147287038
    MSI (s) (58:3C) [11:55:23:844]: Machine policy value 'DisableMsi' is 1
    MSI (s) (58:3C) [11:55:23:844]: Machine policy value 'AlwaysInstallElevated' is 0
    MSI (s) (58:3C) [11:55:23:844]: User policy value 'AlwaysInstallElevated' is 0
    MSI (s) (58:3C) [11:55:23:844]: Product installation will be elevated because user is admin and product is being installed per-machine.

     

    SetSqlProperties: Selected SQL server instance. DC1FFRPT01
    SetSqlProperties: MSSQL CurrentVersion. 9.00.4035.00
    SetSqlProperties: MSSQL version. 9
    SetSqlProperties: SQL Server SQLDataRoot. D:\Microsoft SQL Server\MSSQL.1\MSSQL
    MSI (s) (58!44) [11:55:27:167]: PROPERTY CHANGE: Modifying DB_DATA_DIR property. Its current value is 'F:\MSSQL\data\'. Its new value: 'd:\Microsoft SQL Server\MSSQL.1\MSSQL\Data\'.
    MSI (s) (58!44) [11:55:27:168]: Note: 1: 2727 2: 
    MSI (s) (58!44) [11:55:27:168]: PROPERTY CHANGE: Modifying DB_LOG_DIR property. Its current value is 'F:\MSSQL\data\'. Its new value: 'd:\Microsoft SQL Server\MSSQL.1\MSSQL\Data\'.
    MSI (s) (58!44) [11:55:27:168]: Note: 1: 2727 2: 
    MSI (s) (58!44) [11:55:27:169]: PROPERTY CHANGE: Modifying MSSQL_VERSION property. Its current value is '0'. Its new value: '9'.
    MSI (s) (58!44) [11:55:27:169]: PROPERTY CHANGE: Deleting MSSQL_CSDVERSION property. Its current value is '0'.
    MSI (s) (58:3C) [11:55:27:170]: Doing action: _ValidateDBOptions.B8A67CEF_63FF_40C5_B79F_68FE309F3E50
    Action ended 11:55:27: _SetSqlProperties.B8A67CEF_63FF_40C5_B79F_68FE309F3E50. Return value 1.
    MSI (s) (58:C8) [11:55:27:173]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI7D08.tmp, Entrypoint: ValidateDBOptions
    Action start 11:55:27: _ValidateDBOptions.B8A67CEF_63FF_40C5_B79F_68FE309F3E50.
    ValidateDBOptions: Database size property value. 184320
    ValidateDBOptions: Database data file file location. d:\Microsoft SQL Server\MSSQL.1\MSSQL\Data\
    MSI (s) (58!80) [11:55:27:179]: PROPERTY CHANGE: Modifying DbFilesSpaceGood property. Its current value is '1'. Its new value: '0'.
    ValidateDBOptions: Database log file file location. d:\Microsoft SQL Server\MSSQL.1\MSSQL\Data\
    ValidateDBOptions: The specified database data or log file drive does not contain sufficient disk space. Error Code: 0x80076591.
    MSI (s) (58:3C) [11:55:27:181]: Machine policy value 'DisableRollback' is 0
    MSI (s) (58:3C) [11:55:27:181]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    Action ended 11:55:27: _ValidateDBOptions.B8A67CEF_63FF_40C5_B79F_68FE309F3E50. Return value 3.
    MSI (s) (58:3C) [11:55:27:181]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (58:3C) [11:55:27:181]: No System Restore sequence number for this installation.
    MSI (s) (58:3C) [11:55:27:181]: Unlocking Server
    Action ended 11:55:27: INSTALL. Return value 3.

    MSI (s) (58:3C) [11:55:27:262]: Note: 1: 1708
    MSI (s) (58:3C) [11:55:27:262]: Product: Microsoft Operations Manager 2005 Reporting -- Installation failed.

    MSI (s) (58:3C) [11:55:27:263]: Windows Installer installed the product. Product Name: Microsoft Operations Manager 2005 Reporting. Product Version: 5.0.2911.0. Product Language: 1033. Installation success or error status: 1603.

    MSI (s) (58:3C) [11:55:27:264]: Cleaning up uninstalled install packages, if any exist
    MSI (s) (58:3C) [11:55:27:265]: MainEngineThread is returning 1603
    MSI (s) (58:20) [11:55:27:265]: Destroying RemoteAPI object.
    MSI (s) (58:A4) [11:55:27:265]: Custom Action Manager thread ending.
    MSI (s) (58:20) [11:55:27:266]: RESTART MANAGER: Session closed.
    MSI (s) (58:20) [11:55:27:266]: No System Restore sequence number for this installation.
    === Logging stopped: 10/26/2010  11:55:27 ===
    MSI (c) (E4:2C) [11:55:27:271]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
    MSI (c) (E4:2C) [11:55:27:271]: MainEngineThread is returning 1603
    === Verbose logging stopped: 10/26/2010  11:55:27 ===

     


    Kenneth Rodulfo MCP, , MCSA, MCSE, MCTS - Forefront, MCTS - Windows 7 Cisco Certified Network Professional
    • Moved by Miles Zhang Wednesday, October 27, 2010 7:39 AM FCS (From:Forefront Client Security Setup and Configuration)
    Tuesday, October 26, 2010 5:29 PM

Answers

  • Bellard - I thought the same, but you can read it in 2 different ways.  I read it as "being a DB Option" and not an actual error.  Or maybe an error that was uncontrollable.  I ran the MOMReporting.msi and entered the EXACT same variables (database sizes and etc) and it was succesful.

     

    I was able to rectify this situation by manually running MOMReporting.msi and entering in the appropriator fields.  In my opinion what happens is that somehow the data that was "input" into the forefront "momreporting" prompt did not make it into the fields in the actual MOMReporting.msi during the running of it.  Call a "corruption" if you may.

    One major thing I did notice was that when you run the MOMReporting.msi, you have a lot more details that you can work with rather than the "enter data, click and go" method on the forefront software installation screen for Reporting Server and Reporting Database. 

    Note that you should in-defiantly un-click "automatically recognize URLS" when in comes up in the install, referencing the Management Server.  The reason for this being is that forefront was not configured to auto recognize the difference in the SQL 2k and SQL 2k5 difference in software development (as researched on Microsoft's site).

    Summary - if you run into this problem - run MOMReporting.MSI, it is the file that runs anyway during the "Reporting Server and Reporting Database" setup screen in the background.  It will return more responses than just "error 1603 - failure".

     

     


    Kenneth Rodulfo MCP, , MCSA, MCSE, MCTS - Forefront, MCTS - Windows 7 Cisco Certified Network Professional
    • Marked as answer by HanldeX84 Wednesday, October 27, 2010 2:03 PM
    Wednesday, October 27, 2010 2:02 PM

All replies

  • Hi

    I think your disk is toe small

    >>>> ValidateDBOptions: The specified database data or log file drive does not contain sufficient disk space. Error Code: 0x80076591.

    Check your disk size

    More abou sizing: http://technet.microsoft.com/en-us/library/cc180200.aspx

     


    Martijn B.
    • Proposed as answer by Miles Zhang Wednesday, October 27, 2010 9:14 AM
    Wednesday, October 27, 2010 7:14 AM
  • Bellard - I thought the same, but you can read it in 2 different ways.  I read it as "being a DB Option" and not an actual error.  Or maybe an error that was uncontrollable.  I ran the MOMReporting.msi and entered the EXACT same variables (database sizes and etc) and it was succesful.

     

    I was able to rectify this situation by manually running MOMReporting.msi and entering in the appropriator fields.  In my opinion what happens is that somehow the data that was "input" into the forefront "momreporting" prompt did not make it into the fields in the actual MOMReporting.msi during the running of it.  Call a "corruption" if you may.

    One major thing I did notice was that when you run the MOMReporting.msi, you have a lot more details that you can work with rather than the "enter data, click and go" method on the forefront software installation screen for Reporting Server and Reporting Database. 

    Note that you should in-defiantly un-click "automatically recognize URLS" when in comes up in the install, referencing the Management Server.  The reason for this being is that forefront was not configured to auto recognize the difference in the SQL 2k and SQL 2k5 difference in software development (as researched on Microsoft's site).

    Summary - if you run into this problem - run MOMReporting.MSI, it is the file that runs anyway during the "Reporting Server and Reporting Database" setup screen in the background.  It will return more responses than just "error 1603 - failure".

     

     


    Kenneth Rodulfo MCP, , MCSA, MCSE, MCTS - Forefront, MCTS - Windows 7 Cisco Certified Network Professional
    • Marked as answer by HanldeX84 Wednesday, October 27, 2010 2:03 PM
    Wednesday, October 27, 2010 2:02 PM