Install failing... msiexec code 1603

Friday, December 01, 2006 12:58 AM

Hi Mark

Thanks for posting! The failure code 1603 is a generic failure that requires you to open the specific FCS log. If you could do the following:

Open this folder: %Program Files%\Microsoft Forefront\Client Security\Server\Logs
Open the MOMReporting.log file
Do a search for "error" and let us know if you find anything

Without having seen your log file, a potential item might be drive space available. By default, we attempt to allocate 15 GB for the MOM Operational DB (OnePoint) and 1 GB for the MOM Reporting DB (SystemCenterReporting). It may be that you've run out of drive space on your VM

Let me know what you find and we will help you get it installed!

Thanks

Chris

Forefront Client Security PM

Proposed As Answer by Jackyproof Tuesday, February 23, 2010 4:45 PM

Thursday, December 07, 2006 8:33 PM

0

It was a space issue - the VM only had a 10 gig drive defined... Thanks for your help!

Thursday, December 07, 2006 9:19 PM

0

No problem! Glad the install is now working and I could help you out!

Thanks

Chris

Forefront Client Security PM

Monday, March 03, 2008 6:33 PM

0

I'm running into the same issue with Forefront.

I am using the single server topology and have installed and tested all the pre-requisites and I keep getting the same exit code 1603.

The forefront server has 2 processors (this is a test box) and 238GB for the OS and 238GB for the data drives., and 4GB of RAM.

I have verified that reporting services is working.

I would appreciate any help. To speed things up, I am including the output of the serversetup error log; I can e-mail the output of the mom log (since it is too long to post here).

Once I get past this, we are planning to build the actual production environment to deploy forefront and exchange 2007.

Thanks in advance for any help anyone can give..

Doc (doc@scmadv.com)

serversetup (forefront client security) log:

Number of verifications started: [3/3/2008 8:54:56 AM]

[3/3/2008 8:54:56 AM] Verification(Verifying operating system requirements)

[3/3/2008 8:54:56 AM] Verification(Verifying hardware requirements)
Warning: Having two or more processors is recommended for the specified component(s). Recommended processor speed (in MHz): 2850

[3/3/2008 8:54:57 AM] Verification(Verifying software prerequisites)
Warning: SQL Reporting Services 2005 SP1 is not installed.

[3/3/2008 8:54:57 AM] Verification(Verifying collection database)

[3/3/2008 8:54:57 AM] Verification(Verifying access to collection server)

[3/3/2008 8:54:57 AM] Verification(Verifying DAS account)

[3/3/2008 8:54:58 AM] Verification(Verifying access to reporting server)

[3/3/2008 8:54:58 AM] Verification(Verifying reporting database configuration)

[3/3/2008 8:54:58 AM] Verification(Verifying URLs for reports)

[3/3/2008 8:54:59 AM] Verification(Verifying action account)

[3/3/2008 8:54:59 AM] Verification(Verifying DAS account)

[3/3/2008 8:54:59 AM] Verification(Verifying DTS account)

[3/3/2008 8:54:59 AM] Verification(Verifying reporting database service startup)

Number of verifications completed: [3/3/2008 8:55:00 AM]
Tasks started: [3/3/2008 8:55:01 AM]
Root Directory: D:\server
Current Directory: D:\
[3/3/2008 8:55:01 AM] Task(Install the Collection Database)
Installing from this MSI: 'd:\Server\MOMServer.msi'
Log file: 'C:\Program Files\Microsoft Forefront\Client Security\Server\Logs\MOMDB.log'.
[3/3/2008 8:55:01 AM] Task(Install the Collection Database)
Starting Install the Collection Database.
[3/3/2008 8:55:01 AM] Task(Install the Collection Database)
Starting C:\WINDOWS\system32\msiexec.exe.
[3/3/2008 8:55:01 AM] Task(Install the Collection Database)
Process command 'C:\WINDOWS\system32\msiexec.exe'
[3/3/2008 8:55:01 AM] Task(Install the Collection Database)
Process arguments '/i "d:\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="EL-FCS02" SQLSVR_INSTANCE="EL-FCS02" DAS_ACCOUNT="FCS-DAS" DAS_PASSWORD="*****" DAS_DOMAIN="EXCHLAB" DB_SIZE="25600" CONFIG_GROUP="ForefrontClientSecurity" DATA_DIR="E:\MSSQL\DATA" LOG_DIR="E:\MSSQL\DATA"'
[3/3/2008 8:55:21 AM] Task(Install the Collection Database)

[3/3/2008 8:55:21 AM] Task(Install the Collection Database)
The following process failed.
Process: C:\WINDOWS\system32\msiexec.exe
Exit code: 1603Number of tasks completed: [3/3/2008 8:55:21 AM]

Monday, March 03, 2008 8:43 PM

0

Hi,

I have run into this error when i have tried to install forefront client security after an previously failed install. Try to completely uninstall FCS using this guide.

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

...and then try a fresh install.

Good luck!

/Johan

Monday, March 03, 2008 10:18 PM

0

Thank you Johan,

Unfortunately this option did not work for me.

Anyone else have any other ideas?

Thanks.

Doc

Wednesday, March 05, 2008 1:51 PM

0

Hey,

1. check the you have enough disk space when trying to install FCS. you should have at least 20GB (by default) on the drive you are trying to install the CollectionDB on.

2. check if you already have a OnePoint or SystemCenterReportingDB existing on your SQL server

this is usually what makes this problems.

to find out more information I'll need you to post you MOMDB.log and/or files under %Program Files%\Microsoft Forefront\Client Security\Server\Logs

Monday, April 21, 2008 9:42 PM

0

I am having the same issue on a brand new installation. I am installing this on a Windows Server 2003 R2 x64 Standard machine with SQL 2005 x64 standard. I have a 500GB HD so space is not an issue and there is no SystemCenterReportingDB existing on the SQLServer.

I have the DAS setup with an account that has Domain Admins rights and is added as a SQL Sys admin so it shouldn't be a permission issue. Any other ideas would be appreciated. Here is the error message that i am seeing.

Number of verifications completed: [4/21/2008 3:38:56 PM]
Tasks started: [4/21/2008 3:38:57 PM]
Root Directory: D:\server
Current Directory: D:\
[4/21/2008 3:38:57 PM] Task(Install the Collection Database)
Installing from this MSI: 'd:\Server\MOMServer.msi'
Log file: 'C:\Program Files\Microsoft Forefront\Client Security\Server\Logs\MOMDB.log'.
[4/21/2008 3:38:57 PM] Task(Install the Collection Database)
Starting Install the Collection Database.
[4/21/2008 3:38:57 PM] Task(Install the Collection Database)
Starting C:\WINDOWS\system32\msiexec.exe.
[4/21/2008 3:38:57 PM] Task(Install the Collection Database)
Process command 'C:\WINDOWS\system32\msiexec.exe'
[4/21/2008 3:38:57 PM] Task(Install the Collection Database)
Process arguments '/i "d:\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="NEWAPP001" SQLSVR_INSTANCE="NEWAPP001" DAS_ACCOUNT="******" DAS_PASSWORD="*****" DAS_DOMAIN="*****" DB_SIZE="30720" CONFIG_GROUP="ForefrontClientSecurity" '
[4/21/2008 3:39:00 PM] Task(Install the Collection Database)

[4/21/2008 3:39:00 PM] Task(Install the Collection Database)
The following process failed.
Process: C:\WINDOWS\system32\msiexec.exe
Exit code: 1603Number of tasks completed: [4/21/2008 3:39:00 PM]

Thanks

Tracy

Also found this error message in the event log followed by an MSIError stating MOM failed to install.

Event Type: Error
Event Source: .NET Runtime Optimization Service
Event Category: None
Event ID: 1101
Date:  4/21/2008
Time:  3:24:52 PM
User:  N/A
Computer: NEWAPP001
Description:
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Monday, April 21, 2008 9:58 PM

0

Hi Tracy,

x64 windows & SQL is not supported for the FCS server roles. You can install an FCS agent onto an x64 host fine, but the server back-end needs to all be 32bit unfortunately...

Take a look here http://technet.microsoft.com/en-us/library/bb418802.aspx for the system requirements, I would expect your errors are down to that

Thanks

Chris

Wednesday, May 07, 2008 5:56 PM

0

I am getting the same error in the MOMdb.log file that is created when I run the installer.

GetMsiFeatureState: Failed to get feature state. Error Code: 0x80070646. MOMReporting

I have plenty of Processor and Memory and 100Gigs of disk space.

I am installing on a Win2003 32bit server at SP2 with SQL2005 32bit installed and no other instance of SystemCenterReportingDB.

When the Verify Settings and Requirements run I get GREEN checks but the install immediately fails on the first attempt to install anything.

I have searched and searched and searched for an answer and have found nothing...

Help???

TCrowell

Monday, July 28, 2008 1:57 PM

0

I had the same problem on a previously failed installation. After removing all previous installs and files of FCS, I still had the problem. It turns out that the installation proces needs to create the OnePoint database. It couldn't do that, because the MDF and LDF files already existed, which it could not overwrite. So I just deleted the eeadata.mdf and eealog.ldf files in C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data. After deleting the files, the error disappeared.

Hope this helps......

Friday, August 08, 2008 11:12 AM

0

Can you perhaps run just the MOMreporting or MOMserver installations alone on the machine from the forefront client media. Once it runs it usually will fail and allow you to open the log file. Once you open it you can usually get a pretty good idea of what is failing for that specific component.

Thursday, November 20, 2008 1:56 PM

0

has anybody got this to work yet?

I have a new build of server 2003 x86, installed and running sql2005 x86, I have wsus 3 sp1 installed and running. All fully updated.

Forefront had NOT been already installed.
There is plenty of disk space and there is plenty of memory.

So why do I get:

MSI (s) (34!D8) [13:34:46:166]: Note: 1: 2711 2: MOMReporting
Action start 13:34:46: _VerifyPreRequisites.
GetMsiFeatureState: Failed to get feature state. Error Code: 0x80070646. MOMReporting

When I try to install forefront client security.

Is it that MS are using old software MOM2005 as part of forefront and that other updates have broken the install MOM2005?

Friday, November 21, 2008 8:16 PM

Moderator

0

Look for the following folder/file

C:\Users\administrator.FCS\AppData\Local\Temp\MOMPreReqReporting.html

This should give you more clues as to what failed for the MOM reporting failure.

CSS Security Support Engineer (FCS/MBSA/WUA/Incident Response) Check out my blog http://blogs.technet.com/kfalde

Proposed As Answer by Mat Mirabito Friday, December 12, 2008 1:56 AM

Friday, December 12, 2008 1:54 AM

0

I had this issue also, and it was related to the server having the Forefront client (and consequently the MOM 2005 agent) pushed out by an existing Forefront server on the network.

This server was meant to be replacing the old server, but as it had a MOM agent deployed to it, the install of MOM 2005 failed.

You need to install the MOM 2005 agent before proceeding if you run in to this situation.

Mat Mirabito [MCITP, MCSE]

Friday, January 09, 2009 10:14 AM

0

I dont Know exactly if this could help you, but in my case i've noticed on the installation Log the following:

RepLog.ldf still exists. So i deleted it from "Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\".
The file asociated to msiexec.exe was C:\WINDOWS\Installer\8f53bd3.msi. So I terminate the process msiexec.exe on the task maganer AND delete all the files located on c:\WINDOWS\Installer\

And thas was all, when i ran the setup again the intallation process was sucessfull

Note: Obviously i validate the freespace on disk and the Property: OutOfDiskSpace was = to 0

Try it.

H1R@M

Tuesday, May 26, 2009 2:18 PM

0

Hi there,

Try to run the MOMSERVER.MSI manually and check the prerequisities. For me, running Windows 2008 x64 with SQL 2005 SP3 gives me:

Failures
Minimum Requirement: Microsoft SQL Server 2000 SP3 or later - Required For: MOM Database - Detected Value: Could not get SQL Server instance names
Minimum Requirement: .NET Framework v1.1 - Required For: MOM User Interfaces, MOM Management Server - Detected Value

For me that means that MOM cannot get the instance names from SQL 2005 SP3.

Anyone?

Sincerely,
Lukasz

Wednesday, June 03, 2009 12:31 PM

0

hi,

please check your temp directorys (c:\temp, c:\documents and settings\administrator.domain\local settings\temp, c:\windows\temp) if the are empty and c:\windows\installers are also empty. this works for me.
Good luck!

Kind regards Joerg

Thursday, June 11, 2009 10:20 PM

0

I have been running into this for 2 days on both a Windows 2003 and a Windows 2008 two server install. The way I was able to get past it was to install all just the database portions not the distribution and the management console. That allowed me to get past this error and then I was able to install the management console after that.

Friday, June 19, 2009 2:03 PM

0

Had the same issue on Windows 2008, sql 2005 sp3. All 32 bit. Opened the registry and searched for c:\program files\microsoft forefront. Deleted all these entries and run "serversetup.exe" from the Administrator:CMD. Installed perfectly.

yours sincerly, Robin E. Turpijn Microsoft Manageabilty Specialist @ Wortell, Lijnden NL.

Thursday, December 31, 2009 3:54 PM

2

Same issue here. Installing .Net Framework 1.1 sp1 on my Windows 2008 x32 with SQL 2005 sp3 solved this problem.

Proposed As Answer by Vitalie Ciobanu Friday, January 29, 2010 11:44 AM

Wednesday, January 06, 2010 9:39 AM

0

had a similar issue as Mat had

my server already had Client security installed with MOM agent. After uninstalling the MOM agent the installation was successful

Hope this helps as it seems there are a multitude of resons why the installation fails, pity the error does not give clarity.

rgds

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------

Sizla

Thursday, February 25, 2010 12:08 PM

0

Unbeleivable.. just had the same prob and the fix was to put the das account username in CAPS..! even though I chose not case sensitive for SQL... I hope that helps someone..!

Tuesday, April 06, 2010 8:55 AM

1

Installing .Net Framework 1.1 did the trick for me as well.

I have a Windows 2008 x32 with SQL 2005 sp3. Don't be fooled by the v1.1 folder in \Microsoft.Net\Framework - it will only hold a small number of files. So that doesn't mean it's installed.

Proposed As Answer by rlawson-iccohio Wednesday, September 01, 2010 6:47 AM

Monday, September 06, 2010 12:48 PM

0

In my case, Installing .Net Framework 1.1 with SP1 on Windows 2008 x86 with SQL 2005 SP3 solved this problem.

Kind Regards,

Majid Ali Nagori...

Thursday, September 09, 2010 8:08 PM

0

Is this to mean that .net framework 3.5 (sp1) will NOT work, or are you guys saying to have at least 1.1?

Thursday, September 09, 2010 8:19 PM

0

I've read all these forums and still haven't found a suitable answer for my scenario. I meet all the pre-requisites, except it's recommending 2 or more processors. However, my VM does have 2 processors and it says 2 processors when I right click on my computer and hit properties, so I just ignore this warning. I have more than enough disk space. I have .net 3.5 sp1 installed. I saw some recommendations of .net 1.1. I'm assuming 3.0 supercedes that, or are they saying that 3.0 doesn't work? When I run the momserver.msi by itself, it fails the pre-requisite (even though I pass the client security pre-requisite check). However, when I go to look at the .html log file, there is no data in it, so I don't know why the momserver component is failing. I'm running SQL 2005 sp3 and Server 2008 Enterprise x86. 2 processors, 4 gigs, 100 gigs free. I'm installing it on a fresh VM with no failed attempts (I blow away the VM each time it fails and start again with a new one). Any help would be appreciated. I hope the product works better than the install!

Thursday, September 09, 2010 9:18 PM

1

.net 1.1 needs to be installed as well

Friday, September 10, 2010 1:12 PM

0

i just installed .net1.1 and it messed up all my pre requisites so i had to roll back to a previous snapshot will all reuisites checked.. Help please how can i stop getting Error1603 on Install the Collection database i have 108GB free

Install failing... msiexec code 1603

All Replies

Products

Resources

Solutions

Updates

Trials

Related Sites

Training

Certifications

Other resources

Support by product

Other support links

Not an IT pro?