Sign in
 
HomeProductsLibraryLearnDownloadsSupportForums
Microsoft Forefront TechCenter >
> 
> 
FCS Installation failing

Answered FCS Installation failing

  • Thursday, December 27, 2012 9:02 PM
     
      Has Code
    Sign In to Vote
    0

    I am trying to install FCS and I am getting an error:

    Tasks started: [12/27/2012 12:50:01 PM]
Root Directory: C:\Users\svcFFCS\Desktop\FCS\SERVER
Current Directory: C:\Users\svcFFCS\Desktop\FCS\SERVER
[12/27/2012 12:50:01 PM] Task(Install the Collection Database)
Installing from this MSI: 'c:\users\svcffcs\desktop\fcs\Server\MOMServer.msi'
Log file: 'C:\Program Files\Microsoft Forefront\Client Security\Server\Logs\MOMDB.log'.
[12/27/2012 12:50:01 PM] Task(Install the Collection Database)
Starting Install the Collection Database.
[12/27/2012 12:50:01 PM] Task(Install the Collection Database)
Starting C:\Windows\system32\msiexec.exe.
[12/27/2012 12:50:01 PM] Task(Install the Collection Database)
Process command 'C:\Windows\system32\msiexec.exe'
[12/27/2012 12:50:01 PM] Task(Install the Collection Database)
Process arguments '/i "c:\users\svcffcs\desktop\fcs\Server\MOMServer.msi" /norestart /qn /l*v "C:\Program Files\Microsoft Forefront\Client Security\Server\Logs\MOMDB.log" INSTALLDIR="C:\Program Files\Microsoft Forefront\Client Security\Server\Microsoft Operations Manager 2005" ADDLOCAL="MOMXDB" MOM_SERVER="VOFOREFRONTCS1" SQLSVR_INSTANCE="VOFOREFRONTCS1" DAS_ACCOUNT="SvcFFCS" DAS_PASSWORD="*****" DAS_DOMAIN="AD" DB_SIZE="15360" CONFIG_GROUP="ForefrontClientSecurity" '
[12/27/2012 12:50:02 PM] Task(Install the Collection Database)

[12/27/2012 12:50:02 PM] Task(Install the Collection Database)
The following process failed.
Process: C:\Windows\system32\msiexec.exe
Exit code: 1603Number of tasks completed: [12/27/2012 12:50:03 PM]

    When I am trying to run manually the MOMServer.msi I have also an error:

    "The minimum prerequisites for installation have not been met. When I open the log the page is empty:

     Selected Components:    

Failures 
 Minimum Requirement  Recommended
(if different from minimum)  Required For  Detected Value  Resolution  

Warnings 
 Minimum Requirement  Recommended
(if different from minimum)  Required For  Detected Value  Resolution  

SQL Instances 
 SQL Instances  Required For  Instance Name  Status of SQL Instance  Resolution  

Passed 
 Minimum Requirement  Recommended
(if different from minimum)  Required For  Detected Value  Resolution

    What is the next step to correct this? no information about the failure ???

    Thanks,
    Dom

    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

     

All Replies

  • Friday, December 28, 2012 1:24 AM
     
     
    Sign In to Vote
    0

    Hello,

    Already Look for the following folder/file C:\Users\administrator.FCS\AppData\Local\Temp\MOMPreReqReporting.html and the file is empty!!

    Any clue?

    Thanks,
    Dom

    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

     
  • Friday, December 28, 2012 7:06 AM
    Moderator
     
     
    Sign In to Vote
    1

    Hi,

    Thank you for the post.

    Before going any further, you may check the system requirement : http://technet.microsoft.com/en-us/library/bb404245.aspx, and it is no support install FCS server component on 64 bit servers. As the code 1603 is a generic failure that requires you to open the MOMDB log. Do a search for "error" and let us know if you find anything. Please also check if you have enough disk space when installing FCS and if you have already have a OnePoint or SystemCenterReportingDB existing on your SQL server. Here is thread related 1603 error: http://social.technet.microsoft.com/Forums/en-GB/Forefrontclientsetup/thread/850f05f2-1971-442e-8ea5-0408f2d37665

    Regards,

    Nick Gu - MSFT

     
  • Friday, December 28, 2012 5:00 PM
     
      Has Code
    Sign In to Vote
    0

    Hello,

    The server is Windows Server 2008 Enterprise 32-Bits Service Pack 2.

    C: Free Space 136 GB

    RAM: 65 GB

    CPU: 24 Core 2.80 Ghz Intel Xeon(R) X5660

    SQL Server 2005 SP3 (version 9.0.4060)

    GPMC 6.0.01

    MMC 3.0 (build 6002: Service Pack 2)

    C:\Program Files\Microsoft Forefront\Client Security\Server\Logs\MOMDB.log

    Action start 21:00:25: _VerifyPreRequisites.
GetMsiFeatureState: Failed to get feature state. Error Code: 0x80070646. MOMReporting
    CPreReqVerifier::CheckCurrentUserIsDBAdmin: Database instance registry value not found. Error Code: 0x80070002. 
    VerifyPreRequisites: Result of Pre-Req check: PreReq_Requirements_Not_Met . See PreReq report for details: \MOMPreReqReport.html. Error Code: 0x80004005. 
VerifyPreRequisites: Function returned value. Error Code: 0x80004005. 
Action ended 21:00:25: _VerifyPreRequisites. Return value 3.

    I found these errors ..

    SQL is installed on C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL

    SQL Reporting is installed C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services

    From the thread I checked:

    C:\Users\Administrator\AppData\Local\Temp

    The direcrory is empty

    svcFFCS is the user account used to login in... and then right click on "SERVERSETUP.EXE run as administrator...

    http://technet.microsoft.com/en-us/library/bb404265.aspx

    the account is a domain user, local administrator on the one-server all roles.

    DataEngine: Server Roles: dbcreator, public, sysadmin

    This user is able to open SSMS and access the ReportServerDB & ReportServerTempDB.

    The user is able to open SSMS and access Reporting Service: Home, Security, Shared Schedules but getting an error on them when expanding... then redo SSMS Run As Administrator and everything is accessible.

    C:\Users\svcFFCS\AppData\Local\Temp

    The directory is empty

    Space on C: drive 116 GB

    IIS:

    IIS 6.0 installed

    Authentication: Anonymous Authentication Disabled, Windows Autentication Enabled.

    http://localhost/ReportServer is browsable by svcFFCS

    http://localhost/Reports/Pages/Folder.aspx is browsable by svcFFCS

    Remains WSUS I have tried to remove WSUS but it gives me an access denied trying to delete the file EventCategories.dll within C:\Program Files\Update Services\Common so another road block.

    I tried lodctr /R, I tried reboot mutiple times, all registries using this dll are gone...

    Any idea?

    Thanks,

    Dom

    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

    • Edited by Felyjos Friday, December 28, 2012 11:22 PM
    •  
     
  • Saturday, December 29, 2012 5:01 AM
     
      Has Code
    Sign In to Vote
    0

    Hello,

    Finally after several remove of WSUS, databases, software, registries, folders, etc...  now it passed the Collection Server Installlation...  Reporting failing later on..

    Starting Install Client Security Agent.
    [12/28/2012 4:06:04 PM] Task(Install Client Security Agent)
    Starting c:\users\svcffcs\desktop\fcs\Client\clientsetup.exe.
    [12/28/2012 4:06:04 PM] Task(Install Client Security Agent)
    Process command 'c:\users\svcffcs\desktop\fcs\Client\clientsetup.exe'
    [12/28/2012 4:06:04 PM] Task(Install Client Security Agent)
    Process arguments '/NOMOM /I "C:\Program Files"'
    [12/28/2012 4:06:04 PM] Task(Install Client Security Agent)
    Microsoft Forefront Client Security -- Installation failed.
    See log 'C:\Program Files\Microsoft Forefront\Client Security\Client\Logs\Clientsetup.log' for more information.
    [12/28/2012 4:06:04 PM] Task(Install Client Security Agent)

    The following process failed.
    Process: c:\users\svcffcs\desktop\fcs\Client\clientsetup.exe
    Exit code: 1603Number of tasks completed: [12/28/2012 4:06:04 PM]

    Checking the ClientSetup.log for clues...

    2012-12-28 16:06:04  Microsoft Forefront Client Security (1.0.1703.0) -- Installation started
2012-12-28 16:06:04  Hardware requirement check passed.
2012-12-28 16:06:04  Warning: This version of Vista is not supported.
2012-12-28 16:06:04  OS requirement check passed.
2012-12-28 16:06:04  Software requirement check passed.
2012-12-28 16:06:04  SSA Installation Failed.  See FCSSSA.log for details.
2012-12-28 16:06:04  Microsoft Forefront Client Security -- Installation failed.

    Windows Server 2008 Enterprise 32-bits Service Pack 2.

    ... let me check again the requirements on this server as I suppose it is where it tries first to install the client...

    Client Computer:

    Windows Server 2008 Standard with SP1 or later, or Windows Server 2008
    Enterprise with SP1 or later 

    MSI (s) (34:A8) [21:24:33:206]: Product: Microsoft Forefront Client Security State Assessment Service -- A newer version of the product is already installed on this system.

Action ended 21:24:33: LaunchConditions. Return value 3.
Action ended 21:24:33: INSTALL. Return value 3.
MSI (s) (34:A8) [21:24:33:208]: Note: 1: 1708 
MSI (s) (34:A8) [21:24:33:209]: Product: Microsoft Forefront Client Security State Assessment Service -- Installation operation failed.
    where did it detect this?

    I need to do or skip this step to run the "Installation Management Server Component" why did it fail?

    Add/Remove Programs : Uninstall the Antimalware service and State Assessement service

    Click Back and next and the Client Security Agent installeed successfully

    now the failure is on the Management Server component 

    MSI (s) (94:84) [21:44:07:499]: Executing op: ActionStart(Name=StartServices,Description=Starting services,Template=Service: [1])
MSI (s) (94:84) [21:44:07:500]: Executing op: ProgressTotal(Total=1,Type=1,ByteEquivalent=1300000)
MSI (s) (94:84) [21:44:07:500]: Executing op: ServiceControl(,Name=FcsMs,Action=1,,)
MSI (s) (94:84) [21:44:37:512]: Product: Microsoft Forefront Client Security Management Server -- Error 1920.Service Microsoft Forefront Client Security Management Service (FcsMs) failed to start.  Verify that you have sufficient privileges to start system services.

Error 1920.Service Microsoft Forefront Client Security Management Service (FcsMs) failed to start.  Verify that you have sufficient privileges to start system services.

    Thanks,

    Dom

    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager




    • Edited by Felyjos Saturday, December 29, 2012 6:33 AM
    •  
     
  • Saturday, December 29, 2012 7:36 AM
    Moderator
     
     Answered
    Sign In to Vote
    1

    Hi,

    Thank you for the post.

    “GetMsiFeatureState:Failedto getfeature state.ErrorCode:0x80070646.MOMReporting” - By default, whenever a previous version of MOM2005 or SQL is uninstalled, we don't remove the db files automatically. They must be manually removed. From c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\,  remove "EeaData.mdf" and log files.

    Regards,

    Nick Gu - MSFT

    • Marked As Answer by Felyjos Thursday, January 03, 2013 2:49 PM
    •  
     
  • Sunday, December 30, 2012 3:09 AM
     
     
    Sign In to Vote
    0

    Hello,

    I removed the Client through add/remove programs then now I am fighting the next step on the Management Server with

    Error 1920.Service Microsoft Forefront Client Security Management Service (FcsMs) failed to start.  Verify that you have sufficient privileges to start system services.

    The LPO have the administrators group listed as allowed to start a servive.

    When I start it manually it works.

    I have access to SQL ...

    Finally it passed after stopping the Antimalware service... reboot... setup passed.

    But now

    1) the Antimalware service refused to start 0x80509003..

    2) I need to move the Databases to bigger drives, is it just Stop SQL > Detach DB > Move mdf and ldf to their proper drive > Attache DB? (anything to stop on FCS side?)

    Any idea?

    Thanks,

    Dom

    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager





    • Edited by Felyjos Sunday, December 30, 2012 7:47 PM
    •  
     
  • Wednesday, January 02, 2013 4:18 AM
    Moderator
     
     Answered
    Sign In to Vote
    1

    Hi,

    Thank you for the update.

    You probably need to check the actual reg key at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and look for FCSAM and what that actual Product ID is on your system. Then run command as follow:

    rem uninstall Microsoft Forefront Client Security Antimalware Service

    MsiExec.exe /X { Product ID} /norestart /qn /l*v

    rem uninstall Microsoft Forefront Client Security State Assessment Service

    MsiExec.exe /X { Product ID} /norestart /qn /l*v

    rem uninstall Microsoft Operations Manager 2005 Agent

    MsiExec.exe /X { Product ID} /norestart /qn /l*v

    Regards,

    Nick Gu - MSFT

    • Marked As Answer by Felyjos Thursday, January 03, 2013 2:48 PM
    •  
     
  • Wednesday, January 02, 2013 5:00 PM
     
     
    Sign In to Vote
    0

    Hello,

    I tried

    AntiMalware

    MsiExec.exe /X {436028CD-6476-4224-9274-8F0320F30FD1} /norestart /qn /l*v

    also

    State Assessement

    MsiExec.exe /X {E8B56B38-A826-11DB-8C83-0011430C73A4} /norestart /qn /l*v

    but it gives me

    so I did

    MsiExec.exe /X {E8B56B38-A826-11DB-8C83-0011430C73A4}

    MsiExec.exe /x {436028CD-6476-4224-9274-8F0320F30FD1}

    it works ... but I could not find the GUID for MOM!!!!

    I found

    Microsoft Operations Manager 2005 Reporting
    MsiExec.exe /I{63C847C6-07A0-4A6F-8A78-8A066C9F9773}

    Microsoft Operations Manager 2005
    MsiExec.exe /I{C724B0A5-AFD4-47BB-BC41-F4AF51E8535F}

    And the FCS Agent is still failing !!!

    Any idea?

    Thanks,

    DOm

    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager






    • Edited by Felyjos Wednesday, January 02, 2013 6:31 PM
    •  
     
  • Wednesday, January 02, 2013 7:25 PM
     
     
    Sign In to Vote
    0

    Hello,

    I disabled all services, rebooted and renabled the service and now it works (the Client)

    The databases have been moved to their final drives as well.

    Checking now whyc only 288 machines are reporting from the 1058 machines managed in the MOM Console.

    From the MOM Console:

    All computers:                                      1,058 computers

    Unmanaged Computers:                              1

    Agentless Managed Computers:                    0

    Agent Managed Computers:                   1,004 (All Agent-Managed or Windows Server Cluster Computer - Managed)

    Windows Server Cluster Computers:           52

    Pending Actions:                                         0

    Computer Discover Rules:                         999

    On the FCS Console only                           288 managed computers???

    Why this discrepancy? 

    Thanks,

    Dom

    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager



    • Edited by Felyjos Wednesday, January 02, 2013 7:55 PM
    •  
     
  • Thursday, January 03, 2013 2:57 AM
    Moderator
     
     Answered
    Sign In to Vote
    1

    Hi,

    Thank you for the update.

    Please refer to this kb: http://support.microsoft.com/kb/942581/en-us

    Regards,

    Nick Gu - MSFT

    • Marked As Answer by Felyjos Thursday, January 03, 2013 2:48 PM
    •  
     
  • Thursday, January 03, 2013 2:48 PM
     
     
    Sign In to Vote
    0

    Happy new Year

    The numbers are growing slowly 290 yesterday by 6 PM to 340 this morning 6 am 50 machines in 12 hours it is very slow...

    I am opening a new thread to folllow in this http://social.technet.microsoft.com/Forums/en-US/Forefrontclientgeneral/thread/6550abc4-858d-49e5-8693-99e6c5dd2f40

     Thanks a lot Nick

    Dom

    System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager