locked
Forefront Installation Error - Mom Reporting Service RRS feed

  • Question

  • One server topology. Win 2k8 32 bit, SQL 2005.

    Installation Error at "Install MOM Reporting Service". After a pause of about 5-10 mins the installation fails with exit code 1603.

    I've read previous logs. My user account (and servcie account) is a local administrator. I've manually added SQl server service roles as per a previous article but no joy.

    The  MOM Reporting logfile contents (250,000 chars) are too large to paste here. Instead I've pasted any sections that contained the word "error" below.

    I'd really appreciate help as I'm running out of ideas what might be wrong:

    CPreReqVerifier::CheckCurrentUserIsDBAdmin: Reporting registry key not found. Error Code: 0x80070002.

    CPreReqVerifier::ExclusiveChecksfailed: hr: -2147024894

    CPreReqVerifier::ExclusiveChecksfailed: hr: -2147024894

    CPreReqVerifier::Checkfailed: hr: -2147024894

     

    then later

     

    AddSchedulerTask: Reporting Task User. JohnDoe

    AddSchedulerTask: Reporting Task User domain. PatchServer

    AddSchedulerTask: MOM Database Instance Name. PATCHSERVER

    AddSchedulerTask: MOM Database Name. OnePoint

    AddSchedulerTask: MOM Reporting Database Instance Name. PATCHSERVER

    AddSchedulerTask: Reporting Database Name. SystemCenterReporting

    AddSchedulerTask: MOM Reporting Install Path. d:\Program Files\Microsoft Forefront\Client Security\Server\Reporting\Reporting\

    AddSchedulerTask: Task User Account. PatchServer\JohnDoe

    AddSchedulerTask: Reporting Application Name. MOM.Datawarehousing.DTSPackageGenerator.exe

    AddSchedulerTask: Reporting Parameters. /silent /srcserver:PATCHSERVER /srcdb:OnePoint /dwserver:PATCHSERVER /dwdb:SystemCenterReporting /product:"Microsoft Operations Manager"

    AddSchedulerTask: Failed calling IPersist::Save: . Error Code: 0x80070520.

     

    then later

     

    MSI (s) (3C:20) [13:34:05:778]: Executing op: ActionStart(Name=CreateFolders,Description=Creating folders,Template=Folder: [1])

    MSI (s) (3C:20) [13:34:05:785]: Executing op: ActionStart(Name=RemoveODBC,Description=Removing ODBC components,)

    MSI (s) (3C:20) [13:34:05:788]: Executing op: ActionStart(Name=ProcessComponents,Description=Updating component registration,)

    MSI (s) (3C:20) [13:34:05:789]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs,,BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:789]: Executing op: RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDLLs,,BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:790]: Executing op: ComponentUnregister(ComponentId={8FFCFEBB-F60A-455D-B11D-C68345BCBF98},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:815]: Executing op: ComponentUnregister(ComponentId={BB32B947-CAF6-4242-A79D-E14DFE3AC72F},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:838]: Executing op: ComponentUnregister(ComponentId={48B94A29-9E56-4677-A6CE-79A431893907},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:842]: Executing op: ComponentUnregister(ComponentId={882B5EBD-BE35-4BA9-998E-9A366092A77C},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:852]: Executing op: ComponentUnregister(ComponentId={646CF3FD-CF0A-4722-BE34-FFCC2F15E7EF},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:853]: Executing op: ComponentUnregister(ComponentId={357D147C-88DC-4E87-BA3C-94188E7ADF36},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:854]: Executing op: ComponentUnregister(ComponentId={A6A75C31-2CA9-47F1-938E-8004CADF7A71},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:879]: Executing op: ComponentUnregister(ComponentId={8E156C21-D064-4E3C-90AC-A62152841E97},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:881]: Executing op: ComponentUnregister(ComponentId={AD310FE4-F514-42C6-8AFF-1F58F25B2DF9},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:883]: Executing op: ComponentUnregister(ComponentId={A729A465-EE25-4751-A32A-48AE87889F22},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:884]: Executing op: ComponentUnregister(ComponentId={6571651D-084D-405D-8F41-FFC99415C4BF},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:890]: Executing op: ComponentUnregister(ComponentId={417F01DA-7642-49E7-94AF-10F7D3A9465D},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:892]: Executing op: ComponentUnregister(ComponentId={8E4DA690-8CB7-4498-8CA4-4D6221FFB2DD},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:893]: Executing op: ComponentUnregister(ComponentId={4B5266AA-89A6-4386-B422-4EC004D7C589},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:894]: Executing op: ComponentUnregister(ComponentId={666E7DD5-ACDA-4850-A703-3CBC5C4AC132},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:895]: Executing op: ComponentRegister(ComponentId={1CA051B6-1B70-11D2-9ADD-006097C4E452},KeyPath=C:\Windows\system32\msvcp60.dll,State=3,ProductKey={00000000-0000-0000-0000-000000000000},,SharedDllRefCount=1,BinaryType=0)

    MSI (s) (3C:20) [13:34:05:898]: Executing op: ComponentUnregister(ComponentId={1CA051B6-1B70-11D2-9ADD-006097C4E452},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:898]: Executing op: ComponentUnregister(ComponentId={1CA051B0-1B70-11D2-9ADD-006097C4E452},ProductKey={00000000-0000-0000-0000-000000000000},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:899]: Executing op: ComponentUnregister(ComponentId={1CA051B0-1B70-11D2-9ADD-006097C4E452},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:900]: Executing op: ComponentUnregister(ComponentId={90ECD999-8D6D-4DFE-9FEA-EDB3ED63046E},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:902]: Executing op: ComponentUnregister(ComponentId={43654CB3-1972-40BD-AD89-41503AE0C3C0},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:903]: Executing op: ComponentUnregister(ComponentId={94F5B14D-C610-4F94-A765-0A4D37A53EFD},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:904]: Executing op: ComponentUnregister(ComponentId={3E8628FF-89A2-422E-B3B5-ABA055574E20},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:905]: Executing op: ComponentUnregister(ComponentId={58868B36-CBDC-44D4-9094-431CE129DC79},ProductKey={63C847C6-07A0-4A6F-8A78-8A066C9F9773},BinaryType=0,)

    MSI (s) (3C:20) [13:34:05:908]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=0)

    MSI (s) (3C:20) [13:34:05:908]: Error in rollback skipped.              Return: 5

    MSI (s) (3C:20) [13:34:06:024]: No System Restore sequence number for this installation.

    MSI (s) (3C:20) [13:34:06:024]: Unlocking Server

    MSI (s) (3C:20) [13:34:06:085]: PROPERTY CHANGE: Deleting UpdateStarted property. Its current value is '1'.

    Action ended 13:34:06: INSTALL. Return value 3.

     

    and finally

     

    MSI (s) (3C:20) [13:34:06:741]: Note: 1: 1708

    MSI (s) (3C:20) [13:34:06:741]: Product: Microsoft Operations Manager 2005 Reporting -- Installation failed.

     

    MSI (s) (3C:20) [13:34:06:746]: 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) (3C:20) [13:34:06:769]: Deferring clean up of packages/files, if any exist

    MSI (s) (3C:20) [13:34:06:812]: MainEngineThread is returning 1603

    MSI (s) (3C:AC) [13:34:06:827]: RESTART MANAGER: Session closed.

    MSI (s) (3C:AC) [13:34:06:827]: No System Restore sequence number for this installation.

    === Logging stopped: 10/01/2011  13:34:06 ===

    MSI (s) (3C:AC) [13:34:06:834]: User policy value 'DisableRollback' is 0

    MSI (s) (3C:AC) [13:34:06:834]: Machine policy value 'DisableRollback' is 0

    MSI (s) (3C:AC) [13:34:06:834]: Incrementing counter to disable shutdown. Counter after increment: 0

    MSI (s) (3C:AC) [13:34:06:838]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

    MSI (s) (3C:AC) [13:34:06:844]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2

    MSI (s) (3C:AC) [13:34:06:854]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

    MSI (s) (3C:AC) [13:34:06:858]: Restoring environment variables

    MSI (s) (3C:AC) [13:34:07:430]: Destroying RemoteAPI object.

    MSI (s) (3C:90) [13:34:07:436]: Custom Action Manager thread ending.

    MSI (c) (18:98) [13:34:07:531]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

    MSI (c) (18:98) [13:34:07:533]: MainEngineThread is returning 1603

    === Verbose logging stopped: 10/01/2011  13:34:07 ===

     

    Please help :-)

    Stu

    Monday, January 10, 2011 3:13 PM

Answers

  • Hi,

    Thanks for the post.

    Have you tried the solutins provided in the following post?

    http://social.technet.microsoft.com/Forums/en/Forefrontclientsetup/thread/83c27b1c-dd40-4198-bd44-e38fbe3552ca

    In addition, are you attempting to install FCS on a server that already has a SystemCenterReporting DB?  Doing so is not supported - FCS requires it's one OnePoint and SystemCenterReporting databases

    Thanks,

    Miles


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Miles Zhang Monday, February 7, 2011 1:40 AM
    Tuesday, January 11, 2011 7:37 AM

All replies

  • Hi,

    Thanks for the post.

    Have you tried the solutins provided in the following post?

    http://social.technet.microsoft.com/Forums/en/Forefrontclientsetup/thread/83c27b1c-dd40-4198-bd44-e38fbe3552ca

    In addition, are you attempting to install FCS on a server that already has a SystemCenterReporting DB?  Doing so is not supported - FCS requires it's one OnePoint and SystemCenterReporting databases

    Thanks,

    Miles


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Miles Zhang Monday, February 7, 2011 1:40 AM
    Tuesday, January 11, 2011 7:37 AM
  • Hi Miles!

    Many thanks for your swift reply. I’ve looked at that link you sent.

    It suggests lots of things, which I’ll reply to here:

     

    ·          check that you have local administrator rights on the server. YES

    ·          check the the installation folder is locally on the computer (and you are not trying to install from a share on the network). YES

    ·          install from an interactive console session, not from Terminal. YES

     

    ·          Sufficient Disk Space: I’m configuring my collection DB at 1GB and reporting at 15GB. I have approx 50GB free disk space (so plenty?).

     

    ·          There is no pre-existing SystemCenterReporting Database.

    The only “Reporting” database already in existing in the SQL ReportServer database (created by installing SQl Reporting Service, which is a prerequisite for Forefront installation).

     

    When the installation fails, I can see that the OnePoint DB has been created but not the SystemcenterReporting DB.

     

     

    ·          SQL server isn’t case sensitive.

    ·          The default website is listening on port 80.

     

    ·          I have added the reporting services “Execution Account”.

     

    Still not working! L

    I’ve tried uninstall/reinstall Forefront about 5 times already.

     

    I’d really appreciate any further suggestions. I’m beginning to lose the will to live J

    Many thanks in anticipation!

    Stu

    Tuesday, January 11, 2011 2:10 PM
  • Hi!

    Have you installed .Net Framework 1.1?

    It is a prereq, however the FCS prereq verifier does not look for it so the FCS prereq verifier can show "all green" and then it fails anyway.

    /Johan

     


    MCSE, forefront spec | www.msforefront.com
    Tuesday, January 11, 2011 3:02 PM
  • Yes - Actually my installation failed to install due to that at an earlier stage (during collection server) and i used this forum to diagnose that it was due to .Net Framework 1.1 missing (I incorrectly assumed that .Net Framework 3 being installed meant that 1.1 and SP1 was not needed). That is now installed and the installation progreses further until it fails while attempting to install the MOM reporting service.

    So - I'm still stuck and looking for suggestions/answers please!! :-)

    Stu

    Wednesday, January 12, 2011 2:10 PM