Microsoft.NET Framework 2 problem

I did an XP Repair Install and the last pieces to update are
Microsoft .NET Framework 2.0 and 3.0 Service Packs 1. The problem is
they won't install.

It seems the cultprit is NET Framework 2.0. When I try to repair or
uninstall it (after uninstalling 3.0), the error message is "Patch
Package could not be opened. Verify that the patch package exists..."
When I try to install the 2.0 patch again, it says the program to be
upgraded may be missing. There's an MS bulletin (908077) on
troubleshooting 2.0 install problems, but none of the steps there work,
presumably for the same reason. MS Update is not picking up on the
problem at the 'checking computer' stage.

What do you suggest? Might reinstalling 2.0 on top work? If so, where
can I find a copy? I'm confused with the names, because there's a
redistributable version and compact version and perhaps others. Thanks.

RM

>I did an XP Repair Install and the last pieces to update are
>Microsoft .NET Framework 2.0 and 3.0 Service Packs 1. The problem is
>they won't install.
>
>It seems the cultprit is NET Framework 2.0. When I try to repair or
>uninstall it (after uninstalling 3.0), the error message is "Patch
>Package could not be opened. Verify that the patch package exists..."
>When I try to install the 2.0 patch again, it says the program to be
>upgraded may be missing. There's an MS bulletin (908077) on
>troubleshooting 2.0 install problems, but none of the steps there work,
>presumably for the same reason. MS Update is not picking up on the
>problem at the 'checking computer' stage.
>
>What do you suggest? Might reinstalling 2.0 on top work? If so, where
>can I find a copy? I'm confused with the names, because there's a
>redistributable version and compact version and perhaps others. Thanks.

How about a download and doing it manually?
2.0 SP1
http://www.microsoft.com/downloads/d...displaylang=en
3.0 SP1
http://www.microsoft.com/downloads/d...displaylang=en

- Thee Chicago Wolf

Thee Chicago Wolf <.@.> wrote:

> How about a download and doing it manually?
> 2.0 SP1
> http://www.microsoft.com/downloads/d...displaylang=en
> 3.0 SP1
> http://www.microsoft.com/downloads/d...displaylang=en

2.0 SP1 installed but 3.0 SP1 did not, so I tried 3.0 with the
same result. Are the SPs supposed to include the original numbered
version? Here's the error log from the attempted 3.0 install:


[01/24/08,15:02:39] Windows Communication Foundation: [2] Error:
Installation failed for component Windows Communication Foundation. MSI
returned error code 1603 [
01/24/08,15:02:46] WapUI: [2] DepCheck indicates Windows Communication
Foundation is not installed.
[01/24/08,15:02:46] WapUI: [2] DepCheck indicates Microsoft .NET
Framework 3.0 was not attempted to be installed.
[01/24/08,15:14:05] Windows Communication Foundation: [2] Error:
Installation failed for component Windows Communication Foundation. MSI
returned error code 1603
[01/24/08,15:14:13] WapUI: [2] DepCheck indicates Windows Communication
Foundation is not installed.
[01/24/08,15:14:13] WapUI: [2] DepCheck indicates Microsoft .NET
Framework 3.0 was not attempted to be installed.

>Thee Chicago Wolf <.@.> wrote:
>
>> How about a download and doing it manually?
>> 2.0 SP1
>> http://www.microsoft.com/downloads/d...displaylang=en
>> 3.0 SP1
>> http://www.microsoft.com/downloads/d...displaylang=en
>
>2.0 SP1 installed but 3.0 SP1 did not, so I tried 3.0 with the
>same result. Are the SPs supposed to include the original numbered
>version? Here's the error log from the attempted 3.0 install:
>
>
>[01/24/08,15:02:39] Windows Communication Foundation: [2] Error:
>Installation failed for component Windows Communication Foundation. MSI
>returned error code 1603 [
>01/24/08,15:02:46] WapUI: [2] DepCheck indicates Windows Communication
>Foundation is not installed.
>[01/24/08,15:02:46] WapUI: [2] DepCheck indicates Microsoft .NET
>Framework 3.0 was not attempted to be installed.
>[01/24/08,15:14:05] Windows Communication Foundation: [2] Error:
>Installation failed for component Windows Communication Foundation. MSI
>returned error code 1603
>[01/24/08,15:14:13] WapUI: [2] DepCheck indicates Windows Communication
>Foundation is not installed.
>[01/24/08,15:14:13] WapUI: [2] DepCheck indicates Microsoft .NET
>Framework 3.0 was not attempted to be installed.

The 3.0 SP1 would include all that was in 3.0. There must be something
else going on with your machine then.

- Thee Chicago Wolf

Thee Chicago Wolf <.@.> wrote:

> The 3.0 SP1 would include all that was in 3.0. There must be something
> else going on with your machine then.

The other MS updates after the Repair went fine, so the problem seems
specific to .NET. The question is how to figure it out. Any
suggestions? Thanks.

RM

>Thee Chicago Wolf <.@.> wrote:

I tried 3.0SP1 again and it failed on setup. Looking at the error log
below, notice that all of these lines refer to failing on 2.0SP1, and
the third one down says the latter is not installed, even though it
looked to me like it had. But a check confirms it's not there. Doesn't
that suggest that the problem is with 2.0, as I found before? I
thought usually with MS apps, SPs need the original version to install,
even if the SP includes it.


[01/24/08,14:51:51] Microsoft .NET Framework 2.0SP1 x86: [2] Error code
1603 for this component means "Fatal error during installation. "
[01/24/08,14:51:51] Microsoft .NET Framework 2.0SP1 x86: [2] Setup
Failed on component Microsoft .NET Framework 2.0SP1 x86
[01/24/08,14:51:56] WapUI: [2] DepCheck indicates Microsoft .NET
Framework 2.0SP1 x86 is not installed. [01/24/08,16:16:40]
Microsoft .NET Framework 2.0SP1 x86: [2] Error code 1603 for this
component means "Fatal error during installation. "
[01/24/08,16:16:40] Microsoft .NET Framework 2.0SP1 x86: [2] Setup
Failed on component Microsoft .NET Framework 2.0SP1 x86
[01/24/08,16:16:45] WapUI: [2] DepCheck indicates Microsoft .NET
Framework 2.0SP1 x86 is not installed.

Sorry to follow up again, but the 2.0 SP1 installer says it's there,
but neither Add/Remove Programs nor another Uninstall application can
find it. Curious.

RM

Thee Chicago Wolf <.@.> wrote:

> The 3.0 SP1 would include all that was in 3.0. There must be something
> else going on with your machine then.

Try posting in one of the many microsoft.public.dotnet.framework.*
newsgroups. They would know more than the guys here.

*TimDaniels*

First, see http://support.microsoft.com/kb/923100 (ignore the title).

If no joy, see this recent post in Windows Update newsgroup by my colleague
MowGreen:
http://groups.google.com/group/micro...76de7769d04493
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/


romat@invalid.net wrote:
> I did an XP Repair Install and the last pieces to update are
> Microsoft .NET Framework 2.0 and 3.0 Service Packs 1. The problem is
> they won't install.
>
> It seems the cultprit is NET Framework 2.0. When I try to repair or
> uninstall it (after uninstalling 3.0), the error message is "Patch
> Package could not be opened. Verify that the patch package exists..."
> When I try to install the 2.0 patch again, it says the program to be
> upgraded may be missing. There's an MS bulletin (908077) on
> troubleshooting 2.0 install problems, but none of the steps there work,
> presumably for the same reason. MS Update is not picking up on the
> problem at the 'checking computer' stage.
>
> What do you suggest? Might reinstalling 2.0 on top work? If so, where
> can I find a copy? I'm confused with the names, because there's a
> redistributable version and compact version and perhaps others. Thanks.
>
> RM

"PA Bear [MS MVP]" <PABearMVP@gmail.com> wrote:

> First, see http://support.microsoft.com/kb/923100 (ignore the title).
>
> If no joy, see this recent post in Windows Update newsgroup by my colleague
> MowGreen:
> http://groups.google.com/group/micro...76de7769d04493
> --
> ~Robear Dyer (PA Bear)
> MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
> AumHa VSOP & Admin http://aumha.net
> DTS-L http://dts-l.net/

Execllent. Aaron Stebner's .NET cleanup tool quickly did the trick and
things are now up to date. Truly most valuable.

RM