How to locate the cause of error code 1603 in a verbose MSI log file

How to workaround errors installing .NET Framework 2.0 that are caused by registry permission problems

Aaron Stebner's WebLog — Wed, 10 Aug 2005 04:27:23 GMT

I have had a few customers report problems installing the .NET Framework 2.0 with the following symptoms:...

How to workaround errors installing .NET Framework 2.0 that are caused by registry permission problems

Aaron Stebner's WebLog — Wed, 10 Aug 2005 04:27:42 GMT

I have had a few customers report problems installing the .NET Framework 2.0 with the following symptoms:...

WiLogUtl.exe does not work with Windows Installer 3.1 log files

Aaron Stebner's WebLog — Fri, 19 Aug 2005 06:02:17 GMT

A little while back I described a method of searching for errors in a verbose MSI log file.&nbsp; At...

WiLogUtl.exe does not work with Windows Installer 3.1 log files

Aaron Stebner's WebLog — Tue, 23 Aug 2005 19:07:41 GMT

A little while back I described a method of searching for errors in a verbose MSI log file.&nbsp; At...

re: How to locate the cause of error code 1603 in a verbose MSI log file

Ubhatnagar — Wed, 23 Aug 2006 14:29:54 GMT

I get an error
[08/23/06,14:41:31] Windows Communication Foundation: ***ERRORLOG EVENT*** : Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
[08/23/06,14:41:56] WapUI: ***ERRORLOG EVENT*** : DepCheck indicates Microsoft .NET Framework 3.0 - was not attempted to be installed.

i followed the steps as above to find the error in msi*.log file. I did not find any "return value 3", instead all where "return value 1". What should I do now?

Any help would be appreciated. I am running WinXP Sp2.

Thanks
Urvashi

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Sat, 26 Aug 2006 07:09:14 GMT

Hi Ubhatnagar - Can you check and see if you have any error logs named dd_*msi*.txt in your %temp% directory? The log file you are currently looking in is not a verbose MSI log, so you will not see "return value 3" in that log. If you are unable to find the log with the error, please zip and send me any logs named %temp%\dd_*msi*.txt at Aaron.Stebner (at) Microsoft (dot) com and I will try to help you find the root cause.

Case study: How I approach debugging and fixing a setup failure

Aaron Stebner's WebLog — Fri, 08 Sep 2006 08:26:16 GMT

I received a mail from a customer this week regarding an installation failure that proved to be fairly...

re: How to locate the cause of error code 1603 in a verbose MSI log file

Bahadır Çambel — Sun, 26 Nov 2006 08:33:47 GMT

Hi Aaron ,

I'm getting a WFC not found error during the installation of the .Net Framework 3.0 Redist. Pack.

I recently tried to install the WFC , but couldn't achieved.

Could you please advice ?

Thanks in advance

//------------------//

[11/26/06,07:27:10] Windows Workflow Foundation: [2] Error: Installation failed for component Windows Workflow Foundation. MSI returned error code 1603

[11/26/06,07:27:40] WapUI: [2] DepCheck indicates Windows Workflow Foundation is not installed.

[11/26/06,07:27:40] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 was not attempted to be installed.

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Sun, 26 Nov 2006 22:33:20 GMT

Hi Bahadir - There is a full list of log files produced by the .NET Framework 3.0 setup package at http://blogs.msdn.com/astebner/archive/2006/10/30/net-framework-3-0-setup-log-files.aspx.

In this case, the log file named %temp%\dd_WF_3.0_x86retMSI*.txt should contain the exact error information for this failure. Can you please check and see if you have this log, and send it to me via email at Aaron.Stebner (at) Microsoft (dot) com so I can take a look and see if I can figure anything out?

re: How to locate the cause of error code 1603 in a verbose MSI log file

nirajswaminarayan — Sat, 31 Mar 2007 17:44:09 GMT

To resolve this issue, reinstall all .Net 3.0 product by using .Net 3.0 Uninstaller tool.

Open machine.config file of .Net 2.0 Framework and change encoding format from UTF-8 to UTF-16.

Link to article describing how to interpret Windows Installer log files

Aaron Stebner's WebLog — Thu, 05 Apr 2007 06:14:10 GMT

I often get asked questions about how to read, interpret and find error information in verbose Windows

Custom Action Guidelines

Heath Stewart's Blog — Sat, 21 Apr 2007 05:07:35 GMT

Rob Mensching, father of Windows Installer XML (WiX), blogs about why managed custom actions are a bad

Custom Action Guidelines

Heath Stewart's Blog — Wed, 04 Jul 2007 00:59:50 GMT

Rob Mensching, father of Windows Installer XML (WiX), blogs about why managed custom actions are a bad

Problems when installing .NET Framework 3.5 (Pre-Release Version)

Adrian Roman — Thu, 02 Aug 2007 15:10:19 GMT

Problems when installing .NET Framework 3.5 (Pre-Release Version)

Neat Tip To Enable Verbose Installer Logging

Dan's Archive — Tue, 25 Sep 2007 15:17:43 GMT

Neat Tip To Enable Verbose Installer Logging

re: How to locate the cause of error code 1603 in a verbose MSI log file

caranosian — Fri, 19 Oct 2007 23:33:21 GMT

I have been trying unsuccessfully to install .NET Framework 3.0 on a clean (newly imaged) Windows XP box with current SP and patches. The machine has Office 2003, Visual Studio.NET and some MSDNs installed. No matter what I have tried I keep getting the error code 1603 message in the log, and a search for info on this led me here.

I followed the verbose logging instructions you provided and recreated the error twice, so I now have 2 of these verbose logs, but neither of them has a "return value 3", so I am not getting anywhere with this.

Can I email them to you to see if there is something else I am missing?

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Sat, 20 Oct 2007 01:35:27 GMT

Hi Caranosian - The .NET Framework 3.0 creates its own set of logs, so the verbose logging instructions that I provided won't cause additional logs to be created in this case. You can find a list of logs created by .NET Framework 3.0 setup at http://blogs.msdn.com/astebner/archive/2006/10/30/net-framework-3-0-setup-log-files.aspx. If you have trouble finding the source of the error in those logs, please zip and send them to me and I'll try to take a look. You can send them to Aaron.Stebner (at) microsoft (dot) com.

re: How to locate the cause of error code 1603 in a verbose MSI log file

shagpub — Sat, 01 Dec 2007 16:13:08 GMT

Hi, I'm having this error when installing .Net Framework 3.0 on Windows XP

Error 25015.Failed to install assembly 'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\System.Management.dll' because of system error: The system cannot find the path specified.

It's kinda weird since I can see the file there in that folder. Thx you

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Mon, 03 Dec 2007 08:11:23 GMT

Hi Shagpub - I'd suggest trying the steps listed at http://blogs.msdn.com/astebner/archive/2005/10/11/479928.aspx to clean off and re-install the .NET Framework 2.0, and then hopefully the .NET Framework 3.0 will install correctly after that.

If those steps do not help, then one of the following might also be useful:

http://blogs.msdn.com/astebner/archive/2006/09/04/739820.aspx

http://blogs.msdn.com/astebner/archive/2006/11/25/disabling-services-with-msconfig-to-work-around-setup-failures.aspx

Possible workaround for errors during installation of Document Explorer 2005 and 2008

Aaron Stebner's WebLog — Mon, 10 Dec 2007 20:20:56 GMT

Every once in a while, I hear from a customer who has encountered an error while trying to install Document

Possible workaround for errors during installation of Document Explorer 2005 and 2008

Noticias externas — Mon, 10 Dec 2007 21:22:50 GMT

Every once in a while, I hear from a customer who has encountered an error while trying to install Document

MSDN Blog Postings » Possible workaround for errors during installation of Document Explorer 2005 and 2008

Mon, 10 Dec 2007 21:51:24 GMT

PingBack from http://msdnrss.thecoderblogs.com/2007/12/10/possible-workaround-for-errors-during-installation-of-document-explorer-2005-and-2008/

Steps I use to diagnose .NET Framework 3.0 installation failures related to the ServiceModelReg.exe custom action

Aaron Stebner's WebLog — Fri, 28 Mar 2008 22:52:57 GMT

I often get questions from fellow employees or customers who find my blog regarding how to troubleshoot

re: How to locate the cause of error code 1603 in a verbose MSI log file

alvinashcraft — Wed, 04 Jun 2008 21:55:06 GMT

Hi Aaron,

Can you tell me what is return code 3? I am getting this return code at the end of the Popfly Explorer beta install when it's trying to register itself with VS2005. Thanks!

MSI (s) (54:F8) [14:42:39:205]: Executing op: CustomActionSchedule(Action=Launch_VS_80_DEVENV,ActionType=3122,Source=C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\DevEnv.exe,Target=/setup,)

MSI (s) (54:F8) [14:43:59:273]: Note: 1: 1722 2: Launch_VS_80_DEVENV 3: C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\DevEnv.exe 4: /setup

Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action Launch_VS_80_DEVENV, location: C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\DevEnv.exe, command: /setup

MSI (s) (54:F8) [14:44:00:927]: Product: Microsoft Popfly Explorer Beta (1.0.30319.0) -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action Launch_VS_80_DEVENV, location: C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\DevEnv.exe, command: /setup

Action ended 14:44:00: InstallFinalize. Return value 3.

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Thu, 05 Jun 2008 00:25:35 GMT

Hi Alvinashcraft - Return code 3 is a generic error code that is generated when any Windows Installer action fails. In this case, the devenv.exe /setup custom action is failing during PopFly setup on your system. That action is designed to register new VS packages, project and item templates.

What I typically do to try to debug that type of failure is to run it manually outside of the setup with logging enabled and see if it fails there. For example, you can run this:

"C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\DevEnv.exe" /setup /log %temp%\devenv_activity.log

Then you can look in %temp%\devenv_activity.log to see if there are any errors or warnings.

It is also possible that this will only fail during setup. If that is the case, you'll need to try to run it manually with logging enabled during a setup session. To do that, you'll need to use the MsiBreak environment variable described at http://blogs.msdn.com/astebner/archive/2005/06/17/430320.aspx. You need to set the environment variable to Launch_VS_80_DEVENV since that is the action that is failing. After setting the environment variable, you can run the setup, and when the pop-up dialog appears, you can try to run the same command line I listed earlier to run devenv.exe /setup /log %temp%\devenv_activity.log and look for errors and warnings.

Hopefully this helps.

Information about the err.exe tool I use to look up error codes when debugging setup issues

Aaron Stebner's WebLog — Tue, 17 Jun 2008 18:53:51 GMT

When I am attempting to investigate a setup-related failure, I typically end up looking at verbose log

.NET 3.0 install throws WCF errors still, after cleaning tool, reg edit etc

melamason — Tue, 09 Sep 2008 19:43:41 GMT

Hi Aaron,

I have had no luck installing .NET 3.0 on almost half of our domain's laptops - about 300. These are my troubleshooting efforts while trying to reinstall:

I have edited the registry to give Everyone full perms to the HKLM/SYSTEM/CurrentControlSet/Services/EventLog/Security/ServiceModel 3.0.0.0 and not been successful.

I have used your cleaning tool successfully, installed incremental versions and SPs up to 2.0 SP1 and the install still fails.

I've tried the "full" download dotnexfx3.exe and still failed.

Everything still throws the same error, WCF is not installed... I turned on verbose logging and in the MSI*.log, there is no "return code 3". There are several dd_wcf_ret MSI*.txt files that reference it. Here is the part of the file that I believe to have info for you:

Error 1402.Could not open key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Security\ServiceModel 3.0.0.0. System error 5. Verify that you have sufficient access to that key, or contact your support personnel.

MSI (s) (A0:C4) [21:27:07:104]: User policy value 'DisableRollback' is 0

MSI (s) (A0:C4) [21:27:07:104]: Machine policy value 'DisableRollback' is 0

Action ended 21:27:07: InstallFinalize. Return value 3.

I'm getting nowhere. Can you help?

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Wed, 10 Sep 2008 02:03:11 GMT

Hi Melamason - You sent me some log files via email, and in one of them, I see the 1402 access denied error listed in your comment - in that case, you need to make sure that the local system account and the Administrators group on the computer both have full control over the registry key in question in order to correct the access denied error.

In the other 3 of the log files, I see an error in the ServiceModelReg.exe custom action. I usually recommend the steps listed at http://blogs.msdn.com/astebner/archive/2008/03/28/8342307.aspx. For your logs, I've already done steps 1-3 in that blog post to narrow down the action that is causing the error, and you'll need to try steps 4 and 5 to see if you can find the cause of that error.

Hopefully this helps.

Visual Studio 2008 SP1 Installation Errors and Error Code 1603 « Stuff I geek with

Mon, 01 Dec 2008 03:41:17 GMT

PingBack from http://justindevine.wordpress.com/2008/11/30/visual-studio-2008-sp1-installation-errors-and-error-code-1603/

.Net Framework 3.0 error code 1603

Ijaas Yunoos — Thu, 11 Dec 2008 14:33:43 GMT

Hi Arron,

I am having trouble installing .Net Framework 3.0, i had the same error with framework 3.5 so i did a complete uninstall of previous installations using your cleanup tool. I was able to reinstalled version 2.0 adn 2.0 sp1 but i get the error code 1603 when trying to install 3.0 here is the <a href="http://dporiginals.co.cc/dd_wcf_retMSI47BF.txt">Verbose log</a>. I would greatly apreciate if you could help me out here.

Thanks,

Ijaas

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Thu, 11 Dec 2008 22:25:47 GMT

Hi Ijaas Yunoos - Your log file shows that the ServiceModelReg custom action is failing on your system, and that causes .NET 3.0 setup to fail. I have posted some ideas about how to troubleshoot that type of failure at http://blogs.msdn.com/astebner/archive/2008/03/28/8342307.aspx. I've already done steps 1-3 for you, so you can skip to step 4.

Alternatively, you can also try to install the .NET Framework 3.5 SP1 instead of the original 3.5. The 3.5 SP1 installer will install 3.0 SP2 behind the scenes as a prerequisite, and 3.0 SP2 has some modified setup logic that will not cause the entire installation to fail if this ServiceModelReg custom action fails.

Hopefully one of these helps.

re: How to locate the cause of error code 1603 in a verbose MSI log file

Ijaas Yunoos — Fri, 12 Dec 2008 05:46:20 GMT

Thanks Arron,

I used the easy method of installing 3.5 Sp1 and it worked.

Thanks.

Installing .NET 3.5 | keyongtech

Installing .NET 3.5 | keyongtech — Sun, 18 Jan 2009 20:22:14 GMT

PingBack from http://www.keyongtech.com/3249920-installing-net-3-5-a

re: How to locate the cause of error code 1603 in a verbose MSI log file

tomas portnoy — Wed, 21 Jan 2009 21:35:46 GMT

I did everything I found on the net to resolve this problem but nothing worked!! I'm tired! I'm on it for 3 days now!

I have uninstall all traces of frameworks on my computer (Normal uninstall, then manually uninstall reg keys and folder and then clean up tool) Then I successfully install Framework 1.0, 2.0 then 2.0 SP1 with all updates and now I can't install Framework 3.0 or 3.5!

I'm always getting errors and rolling back actions then!

P.S. I have windows XP Pro SP3 with all updates and IIS is not installed.

Her are the Errors for the Net Framework 3.0 Version:

EventType : visualstudio8setup P1 : 10860

P2 : 3.5.21022.08_orcas_x86_net P3 : pr P4 : inst P5 : f

P6 : gencomp734_{168d82f8-ac6b-4b55-804f-2ae51ac4b P7 : baseret_failure

P8 : - P9 : 1603 P10 : -

dd_dotnetfx3error.txt

[01/21/09,17:38:18] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603

[01/21/09,17:39:54] Microsoft .NET Framework 3.0SP1 x86: [2] Error code 1603 for this component means "Erreur irrécupérable lors de l'installation." ( Traduction "Fatal Error during the installation")

[01/21/09,17:39:54] Microsoft .NET Framework 3.0SP1 x86: [2] Setup Failed on component Microsoft .NET Framework 3.0SP1 x86

[01/21/09,17:40:10] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0SP1 x86 is not installed.

Here is the Verbose log file:

http://www.filemail.com/fr/dl.aspx?id=FPHMQOOVEEHPJMJ

Here are the errors when I try to install the 3.5 SP1 Version:

EventType : visualstudio8setup P1 : 35101

P2 : 3.5.30729.01_orcas_x86_net P3 : mc P4 : inst P5 : f

P6 : writeregistryvalues P7 : - P8 : 1603 P9 : -

P10 : gencomp780_{12cd

dd_dotnetfx3.5SP1error.txt

[01/21/09,19:17:03] Microsoft .NET Framework 3.0 SP2 x86: [2] Error: Installation failed for component Microsoft .NET Framework 3.0 SP2 x86. MSI returned error code 1603

[01/21/09,19:19:28] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 SP2 x86 is not installed.

[01/21/09,19:31:05] Microsoft .NET Framework 3.0 SP2 x86: [2] Error: Installation failed for component Microsoft .NET Framework 3.0 SP2 x86. MSI returned error code 1603

[01/21/09,19:32:04] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 SP2 x86 is not installed.

I would appreciate any help. I'm desperate!

Thank you for all.

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Thu, 22 Jan 2009 07:01:02 GMT

Hi Tomas Portnoy - The .NET Framework installers configure their own verbose logging, so using the registry key to enable verbose logging and then searching for msi*.log doesn't work for these setups. Can you please use the list of log files at http://blogs.msdn.com/astebner/archive/2008/04/30/8445569.aspx to find the .NET Framework setup log files from your system, and then zip and upload them to a file server so I can try to take a look?

re: How to locate the cause of error code 1603 in a verbose MSI log file

tomas portnoy — Fri, 23 Jan 2009 00:06:42 GMT

Thank you for respondig so quiclky Aaron. I followed the link you gave me and did everything said in it.

I only did it for the NET Framework 3.5 (Because I almost have the same errors for the 3.0 and I tink the 3.5 installation fail when it's installing the 3.0 so...)

I found 3 files.

Here is the link.

http://www.filemail.com/fr/dl.aspx?id=ANODMMDNJSZXODE

If you find something to fix it, then you will be a god to me.

Thank you.

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Fri, 23 Jan 2009 08:28:46 GMT

Hi Tomas Portnoy - Thanks for posting these logs. There is an additional log file that is needed to narrow down this failure further. From the logs you posted, this is the name and location of the additional log that we need to look at next:

[01/22/09,20:46:43] Microsoft .NET Framework 3.0 SP2 x86: Enabling MSI log file: C:\DOCUME~1\PROLET~1\LOCALS~1\Temp\dd_NET_Framework30_Setup21A2.txt

Can you zip and post that log as well?

re: How to locate the cause of error code 1603 in a verbose MSI log file

tomas portnoy — Fri, 23 Jan 2009 13:03:09 GMT

Hi Aaron. I take a look at the dd_NET_Framework30_Setup21A2.txt file and searched for the "return value 3" string.

I found it and take another look at the string just above:

Microsoft .NET Framework 3.0 Service Pack 2 -- Erreur 1402. Impossible d’ouvrir la clé HKEY_LOCAL_MACHINE\Software\Classes\.xps\PersistentHandler. Erreur système 5. Vérifiez que vous disposez des droits d’accès nécessaires.

It was saying that the reg key was unable to be open, so i gave me the rights of "HKEY_LOCAL_MACHINE\Software\Classes\.xps\" from the regedit pannel, and the installation goes fine!!

It's annoying to see how often the keys are restricted even when you're the administrator!

Thank you for you help sir. I wounldn't be able to do nothing without your help...

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Fri, 23 Jan 2009 20:18:54 GMT

Hi Tomas Portnoy - I'm glad to hear that you were about to find the cause of and the fix for this issue. I agree - it is really unfortunate that ACLs can be removed for the Administrators group like this and can cause installers to fail in very cryptic ways.

re: How to locate the cause of error code 1603 in a verbose MSI log file

bmort — Mon, 16 Feb 2009 05:09:58 GMT

Hello Aaron,

I am having this same problem! Everytime I try run Visual Studio 2008, I get mass errors and then it loads but I can not create a project.. So I uninstalled and now when I reinstall I get the error!

I have done the verbose logging (I think) which I will email to you.. Any help would be appreciated!

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Mon, 16 Feb 2009 08:36:42 GMT

Hi BMort - I received an email from you, but the log you sent is not a verbose log file from VS 2008 setup though. There is an important note listed in the instructions in this blog post, and it links to http://blogs.msdn.com/astebner/archive/2008/02/27/7927123.aspx. That blog post explains that some installers enable their own verbose logging, and when that happens, the technique of enabling logging using the registry value and then looking for msi*.log does not work. You can find the names and locations of the verbose log files created by VS 2008 setup at http://blogs.msdn.com/astebner/archive/2007/07/31/4156781.aspx.

.NET Framework 3.5 SP1 setup will fail if it is run by a user account that starts with a # character

Aaron Stebner's WebLog — Sat, 07 Mar 2009 03:50:36 GMT

I was working with our product support team on an interesting .NET Framework 3.5 SP1 installation failure

.Net 1.0 setup fails with Error 1603

ZachSmith — Fri, 13 Mar 2009 01:49:54 GMT

Here are the results from the verbose MSI log:

MSI (s) (2C!44) [17:39:01:906]: Closing MSIHANDLE (39) of type 790531 for thread 2372

MSI (s) (2C:48) [17:39:02:000]: Closing MSIHANDLE (38) of type 790536 for thread 348

MSI (s) (2C:5C) [17:39:02:062]: Executing op: ActionStart(Name=SelfRegModules,Description=Registering modules,Template=File: [1], Folder: [2])

Action 17:39:02: SelfRegModules. Registering modules

MSI (s) (2C:5C) [17:39:02:172]: Executing op: ProgressTotal(Total=3,Type=1,ByteEquivalent=1300000)

MSI (s) (2C:5C) [17:39:02:218]: Executing op: SetTargetFolder(Folder=C:\WINDOWS\system32\)

MSI (s) (2C:5C) [17:39:02:265]: Executing op: RegSelfReg(File=mscoree.dll,FileID=FL_mscoree_dll_____X86.3643236F_FC70_11D3_A536_0090278A1BB8)

SelfRegModules: File: mscoree.dll, Folder: C:\WINDOWS\system32\

MSI (s) (2C:5C) [17:39:03:078]: Executing op: SetTargetFolder(Folder=C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\)

MSI (s) (2C:5C) [17:39:03:140]: Executing op: RegSelfReg(File=mscordbi.dll,FileID=FL_mscordbi_dll_____X86.3643236F_FC70_11D3_A536_0090278A1BB8)

SelfRegModules: File: mscordbi.dll, Folder: C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\

MSI (s) (2C:5C) [17:39:03:359]: Executing op: RegSelfReg(File=mscorsec.dll,FileID=FL_mscorsec_dll_____X86.3643236F_FC70_11D3_A536_0090278A1BB8)

SelfRegModules: File: mscorsec.dll, Folder: C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\

MSI (s) (2C:5C) [17:39:03:546]: Executing op: ActionStart(Name=CA_ComRegSystemData.3643236F_FC70_11D3_A536_0090278A1BB8,,)

Action 17:39:03: CA_ComRegSystemData.3643236F_FC70_11D3_A536_0090278A1BB8.

MSI (s) (2C:5C) [17:39:03:671]: Executing op: CustomActionSchedule(Action=CA_ComRegSystemData.3643236F_FC70_11D3_A536_0090278A1BB8,ActionType=3073,Source=BinaryData,Target=_QuietExec@4,CustomActionData=C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\RegAsm.exe C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\System.Data.dll;System.Data.dll;C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\)

MSI (s) (2C:5C) [17:39:03:750]: Creating MSIHANDLE (40) of type 790536 for thread 348

MSI (s) (2C:28) [17:39:03:812]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI7D.tmp, Entrypoint: _QuietExec@4

MSI (s) (2C!70) [17:39:03:843]: Creating MSIHANDLE (41) of type 790531 for thread 2416

1: C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\RegAsm.exe C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\System.Data.dll

MSI (s) (2C!70) [17:39:05:765]: Creating MSIHANDLE (42) of type 790531 for thread 2416

1: ERROR: Process returned non-0 value! CMDLINE: C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\RegAsm.exe C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\System.Data.dll

MSI (s) (2C!70) [17:39:05:999]: Closing MSIHANDLE (42) of type 790531 for thread 2416

1: Failed

MSI (s) (2C!70) [17:39:06:078]: Closing MSIHANDLE (41) of type 790531 for thread 2416

MSI (s) (2C:28) [17:39:06:109]: Closing MSIHANDLE (40) of type 790536 for thread 348

Any ideas on what the issue might be?

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Wed, 18 Mar 2009 01:26:51 GMT

Hi ZachSmith - This is the action that is causing .NET Framework 1.0 to fail:

C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\RegAsm.exe C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705\System.Data.dll

RegAsm is essentially trying to write some registry keys for System.Data.dll. I'm not sure why that action would fail though. What OS are you seeing this happen on?

If you haven't yet, I'd suggest trying to use the steps listed at http://blogs.msdn.com/astebner/archive/2008/03/07/8108332.aspx to remove all versions of the .NET Framework, then install the .NET Framework 3.5 SP1 from the link at http://www.microsoft.com/downloads/details.aspx?familyid=AB99342F-5D1A-413D-8319-81DA479AB0D7.

After installing 3.5 SP1, I'd suggest trying again to install the .NET Framework 1.0 and see if it works better after that.

Possible workaround for RGB9RAST install failure when deploying the .NET Framework 3.0 or 3.5

Aaron Stebner's WebLog — Fri, 08 May 2009 06:42:31 GMT

I have heard from a few folks recently (such as this blog comment and this forum post ) who have run

re: How to locate the cause of error code 1603 in a verbose MSI log file

ryani210693 — Wed, 29 Jul 2009 05:35:47 GMT

Hi.

I had no luck trying this...i searched the log file but no "return value 3" was found, so could i email the log to you?

I've had no luck installing .NET Framework 3.5 SP1 for days on end now...just constant error and failing and crashing of the setup.exe.

Thanks, Ryan.

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Wed, 29 Jul 2009 07:18:45 GMT

Hi Ryani210693 - Can you please use the tool described at http://blogs.msdn.com/astebner/archive/2007/08/01/4172276.aspx to gather your .NET Framework 3.5 SP1 setup log files, then post the file vslogs.cab that this tool produces on a file server (such as http://skydrive.live.com) and then reply here with a link to the log files? I will download them and take a look and see what I can figure out about the root cause of the setup failure from there.

re: How to locate the cause of error code 1603 in a verbose MSI log file

ryani210693 — Thu, 30 Jul 2009 01:54:08 GMT

Hi.

The file is located at http://www.nowwebsitedesign.co.uk/other/vslogs.cab

Cheers for your help on this! Much appreciated. Ryan.

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Thu, 30 Jul 2009 02:32:28 GMT

Hi Ryani210693 - The logs you attached show that you're running Windows Vista, but that the OS component for the .NET Framework 3.0 is not enabled. .NET Framework 3.5 SP1 tries to enable that OS component by running the following command:

C:\Windows\system32\OCSetup.exe NetFx3

However, that command is failing on your system. The cbs.log file that you included in your logs shows this error:

2009-07-29 03:49:47, Info CBS Pkgmgr: Installing selectable updates for package: Windows Foundation...

2009-07-29 03:49:48, Info CBS Mark store corruption flag because of package: Package_for_KB905866~31bf3856ad364e35~x86~~6.0.27.0. hr: 0x800b0100

2009-07-29 03:49:48, Error CBS Pkgmgr: Failed installing selectable updates for: Windows Foundation, hr: 0x800b0100

2009-07-29 03:49:48, Info CBS Pkgmgr: return code: 0x800b0100

I would suggest trying to use the CheckSUR tool with the steps listed in the blog post at http://blogs.msdn.com/astebner/archive/2009/01/09/9303167.aspx to try to solve this.

Hopefully this helps.

re: How to locate the cause of error code 1603 in a verbose MSI log file

ryani210693 — Thu, 30 Jul 2009 12:20:42 GMT

Thanks for that.

Here is the log from the CheckSUR

=================================

Checking System Update Readiness.

Binary Version 6.0.6001.22375

Package Version 5.0

2009-07-30 03:31

Checking Deployment Packages

Checking Package Manifests and catalogs.

Checking package watchlist.

Checking component watchlist.

Checking packages.

(f) CBS MUM Missing 0x00000002 servicing\packages\Package_for_KB905866_client_1~31bf3856ad364e35~x86~~6.0.27.0.mum

(f) CBS MUM Missing 0x00000002 servicing\packages\Package_for_KB905866_client~31bf3856ad364e35~x86~~6.0.27.0.mum

(f) CBS MUM Missing 0x00000002 servicing\packages\Package_for_KB905866~31bf3856ad364e35~x86~~6.0.27.0.mum

Checking component store

Summary:

Seconds executed: 3832

Found 3 errors

CBS MUM Missing Total Count: 3

Do I delete them registry folders or just the "InstallName" .mum key?

Thanks, Ryan.

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Thu, 30 Jul 2009 21:40:16 GMT

Hi Ryani210693 - What I'd suggest doing in this scenario is renaming the sub-keys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\<package_name> that refer to those 3 .mum files. I'd suggest renaming rather than deleting - you can rename them back in case there something goes wrong. After renaming, you can try again to install the .NET Framework 3.0 OS component by running OptionalFeatures.exe, checking the item named Microsoft .NET Framework 3.0 (it doesn't matter if the 3 child items under that are checked or not), and clicking OK to try to install it.

re: How to locate the cause of error code 1603 in a verbose MSI log file

ryani210693 — Fri, 31 Jul 2009 00:01:55 GMT

Hi.

I would give that a go...but the OptionalFeatures.exe list of items shows blank strangely? I looked this up and came across the System File Checker Scan- http://support.microsoft.com/kb/931712

I ran the scan but it said it could not fix some corrupt files, but said that the same CBS type logs were created again. I feel like I'm going round in circles!

Do i have to go through the OptionalFeatures.exe? Can i simply downlaod the .NET Framework 3.5 SP1 package?

Apologies for the many questions...thanks, for your help! Ryan.

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Fri, 31 Jul 2009 00:18:26 GMT

Hi Ryani210693 - If your Windows Features dialog is still blank after renaming those registry values, then that means there is still something wrong with your OS update installation engine, and .NET 3.5 SP1 will end up failing for the same reason.

I described how I have solved that issue with the blank Windows Features dialog in the blog post I previously linked to - http://blogs.msdn.com/astebner/archive/2009/01/09/9303167.aspx. Can you try to re-run CheckSUR and see if it shows any additional errors and try to work around those as well?

re: How to locate the cause of error code 1603 in a verbose MSI log file

ryani210693 — Fri, 31 Jul 2009 03:01:41 GMT

When attempting to actually rename the keys i get this error- http://www.grabup.com/uploads/4100311A07732009B901E3002E04.png?direct

I've ran regedit as administrator and also tried to change permissions, but similar error messages occur.

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Fri, 31 Jul 2009 06:38:35 GMT

Hi Ryani210693 - I'd suggest trying to rename the subkey instead of just the InstallName value. If that gives the same error, you may need to right-click on the sub-key, choose Permissions... and grant your user account full control over that sub-key so that you can successfully rename it.

re: How to locate the cause of error code 1603 in a verbose MSI log file

ryani210693 — Fri, 31 Jul 2009 16:33:20 GMT

Hi.

I managed to successfully change permissions and rename the keys.

I loaded up OptionalFeatures.exe once again yet the list remains blank.

I shall re-run the CheckSUR and report back!

Thanks, Ryan.

re: How to locate the cause of error code 1603 in a verbose MSI log file

ryani210693 — Fri, 31 Jul 2009 17:22:35 GMT

Hi.

I have now deleted the keys after making a backup, and the OptionalFeatures.exe now shows the list.

I have ticked the Microsoft .NET Framework 3.0 option, and there were no errors or the like. So does this mean it is installed? I cannot see it in the list of installed programs/features?

Is it now possible for me to install 3.5 SP1 on top of this without any errors?

Thanks for your help once again, Ryan.

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Fri, 31 Jul 2009 18:56:07 GMT

Hi Ryani210693 - OS components that are listed in the Windows Features dialog only appear there and are not listed in the Programs and Features dialog (that is reserved for applications you install afterwards, not for OS components).

Now that you've gotten the .NET Framework 3.0 component enabled, you should be able to run .NET Framework 3.5 SP1 setup on your system. If you try it and still encounter errors, please post an updated set of log files so I can take a further look.

One other thing - now that you've fixed the blank Windows Features dialog that you were seeing, I suggest checking Windows Update for any hotfixes that you might be missing. In the cases I've seen in the past, when a system is in the state that the Windows Features dialog is blank, Windows Update will think that it doesn't need to offer you any hotfixes, so you might be missing some important security fixes on this system as a result.

re: How to locate the cause of error code 1603 in a verbose MSI log file

ryani210693 — Sat, 01 Aug 2009 02:15:54 GMT

Hi.

Success! Both installed and running fine. The help has been extremely valuable and a great method of looking at the logs that may help in the future for any problems!

I had to delete the keys, not just rename them for this to work. Then OptionalFeatures.exe worked, allowing me to have 3.0 installed. On top of that, Windows Update then successfully installed 3.5 SP1 that was waiting to be installed.

Thanks once again for the help! Ryan.

re: How to locate the cause of error code 1603 in a verbose MSI log file

Russiawolf — Tue, 11 Aug 2009 00:32:43 GMT

Hi! I am unable to install the .NET Framework 3.0 on my Windows XP Pro laptop. I followed the above steps and I do a dd_wcf_retMSI704C.txt file that got created.

MSI (s) (6C:E0) [15:15:58:712]: Hello, I'm your 32bit Elevated custom action server.

MSI (s) (6C:E4) [15:16:10:852]: User policy value 'DisableRollback' is 0

MSI (s) (6C:E4) [15:16:10:852]: Machine policy value 'DisableRollback' is 0

Action ended 15:16:10: InstallFinalize. Return value 3.

MSI (s) (6C:E4) [15:16:10:852]: Executing op: Header(Signature=1397708873,Version=301,Timestamp=990542326,LangId=0,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)

MSI (s) (6C:E4) [15:16:10:852]: Executing op: DialogInfo(Type=0,Argument=0)

MSI (s) (6C:E4) [15:16:10:852]: Executing op: DialogInfo(Type=1,Argument=Windows Communication Foundation)

MSI (s) (6C:E4) [15:16:10:852]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])

MSI (s) (6C:E4) [15:16:10:852]: Executing op: ActionStart(Name=DD_CA_InstallXwsRegExe_X86.3643236F_FC70_11D3_A536_0090278A1BB8,,)

MSI (s) (6C:E4) [15:16:10:852]: Executing op: ProductInfo(ProductKey={491DD792-AD81-429C-9EB4-86DD3D22E333},ProductName=Windows Communication Foundation,PackageName=wcf.msi,Language=0,Version=50336154,Assignment=1,ObsoleteArg=0,,,PackageCode={A63B31E5-2445-4C91-BD89-4532D7F4D434},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0)

MSI (s) (6C:E4) [15:16:10:868]: Executing op: ActionStart(Name=DD_CA_InstallXwsRegExe_RB_X86.3643236F_FC70_11D3_A536_0090278A1BB8,,)

MSI (s) (6C:E4) [15:16:10:868]: Executing op: CustomActionRollback(Action=DD_CA_InstallXwsRegExe_RB_X86.3643236F_FC70_11D3_A536_0090278A1BB8,ActionType=1345,Source=BinaryData,Target=QuietExec,CustomActionData=C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe /u /x /y /v;dummy;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\)

MSI (s) (6C:38) [15:16:10:899]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI36.tmp, Entrypoint: QuietExec

MSI (s) (6C:E4) [15:16:14:133]: Executing op: ActionStart(Name=WriteRegistryValues,Description=Writing system registry values,Template=Key: [1], Name: [2], Value: [3])

MSI (s) (6C:E4) [15:16:14:133]: Executing op: RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\SMSvcHost 3.0.0.0\Performance,,BinaryType=0)

Any help would be appreciated.

re: How to locate the cause of error code 1603 in a verbose MSI log file

astebner — Tue, 11 Aug 2009 01:14:03 GMT

Hi Russiawolf - It looks like you're running into a failure with the same custom action that I described in the blog post at http://blogs.msdn.com/astebner/archive/2008/03/28/8342307.aspx. I'd suggest trying the steps listed there to see if they help you in this scenario.