Home Dashboard Directory Help
Search

.NET Framework 3.0 SP2 x86 is not installed by RonG49


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


0
0
Sign in
to vote
Type: Bug
ID: 345315
Opened: 5/21/2008 8:39:03 AM
Access Restriction: Public
1
Workaround(s)
view
3
User(s) can reproduce this bug

Description

I tried to install dotnetfx35.exe today (I have VS2008 installed) and I get the following errors:

[05/21/08,10:07:40] Microsoft .NET Framework 2.0a: [2] Error: Installation failed for component Microsoft .NET Framework 2.0a. MSI returned error code 1603
[05/21/08,10:42:41] 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
[05/21/08,10:43:02] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 SP2 x86 is not installed.
Details
Sign in to post a comment.
Posted by stevewuda on 1/20/2010 at 8:01 PM
I think that should be Thanks Johneo0o
Posted by stevewuda on 1/20/2010 at 7:59 PM
This worked for me as well, after 3 hours of hunting.
Thanks jTrout
Posted by Ali_CA on 1/29/2009 at 10:36 AM
jtrout is 100% correct. i spent a week to find out. some forums are saying to give permissions to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Security\ServiceModel 3.0.0.0 but it didnt worked,

so assigning permissions to HKEY_Local_Machine/System/CurrentControlSet/Services/EventLog/Security worked even i have Dot Net 3.0 Sp1 installed
Posted by Txnca on 11/21/2008 at 8:33 PM
Well, I feel like an idiot right now as I have figured out why I was getting that error. Seems if you don't install .NET Framework 3.5 you get this error when you try to install .NET Framework 3.5 SP1. Sometimes you just do everything backwards. LOL!
Posted by John.eo on 9/22/2008 at 2:51 PM
I had this same issue. After multiple installs failed, I uninstalling 2.0, 3.0 and 3.5 frameworks using the normal uninstall process and finally using Arron Stebner's .net framework cleanup tool. Uninstalling did not help and afterwards I was unable to reinstall the .NET 3.0 or 3.5 frameworks.     In the end it seems that adding "Full Permissions" for the "Adminstrators" group to the HKEY_Local_Machine/System/CurrentControlSet/Services/EventLog/Security Registry node fix the issue. After making that change everything installed without issue.


Hope that helps someone.
-John
Posted by jtrout on 6/10/2008 at 3:48 PM
You're not alone bud, I get the same thing on our development server:

[01/10/08,09:07:56] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[01/10/08,09:11:35] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
[06/09/08,14:01:34] 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
[06/09/08,14:29:04] 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
[06/09/08,14:45:15] 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
[06/09/08,14:45:25] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 SP2 x86 is not installed.
[06/10/08,16:18:42] 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
[06/10/08,16:19:20] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 SP2 x86 is not installed.
Posted by Microsoft on 5/28/2008 at 6:34 PM
We are closing this issue because we are unable to reproduce the issue in our labs based on the information provided. When you are available to send us the additional details that can help us to reproduce the problem, you may edit your issue via Connect and change the status to “Active.”

Thank you,
Visual Studio Product Team
Posted by Microsoft on 5/28/2008 at 6:34 PM
We are closing this issue because we are unable to reproduce the issue in our labs based on the information provided. When you are available to send us the additional details that can help us to reproduce the problem, you may edit your issue via Connect and change the status to “Active.”

Thank you,
Visual Studio Product Team
Posted by Microsoft on 5/22/2008 at 2:46 AM
Thanks for reporting the issue.
In order to fix the issue, we must first reproduce the issue in our labs. We are unable to reproduce the issue with the steps you provided. In your problem description, it is installing dotnetfx35.exe in VS2008,but in your repro steps it is installing l 3.5 SP1 in VS 2008 SP1. And if you have installed VS 2008 Sp1, there is no need to install .NET Framework 3.5 SP1.

It may help if you provide us with:
a) clear steps to reproduce the issue
b) setup log files

You can get the log files with the following steps:
1) Download collect.exe from the link below. http://blogs.msdn.com/heaths/attachment/8483493.ashx
2) You may choose to save the tool for later use, or to run directly.
3) The utility creates a compressed cabinet of all the VS and .NET logs to %TEMP%\vslogs.cab.

You can get more details about how to get the log files here:
http://blogs.msdn.com/heaths/archive/2008/05/09/visual-studio-and-net-log-collection-utility.aspx

If we do not receive a response from you after 7-days , we will automatically close your issue. There is no obligation to respond -- at any time you may edit your issue via Connect and change the status to “Active.”

Thanks again for your efforts and we look forward to hearing from you.
Visual Studio Product Team
Posted by Microsoft on 5/22/2008 at 2:30 AM
Thank you for your feedback. We are currently investigating. The investigation process normally takes 7-14 days. If this issue is urgent, please contact support directly (see http://support.microsoft.com).

If at any time your issue is closed unsatisfactorily, you may edit your issue via Connect and change the status to “Active.”

Thank you,
Visual Studio Product Team
Sign in to post a workaround.
Posted by John.eo on 9/22/2008 at 2:54 PM
Try adding "Full Control" for the "Adminstrators" group to HKEY_Local_Machine/System/CurrentControlSet/Services/EventLog/Security Registry node.