Security Update for Microsoft .NET Framework, Version 1.0 SP3, English (KB886906) will not install

Every night, one Server 2003 machine records the following in the eventlog:"
Installation Ready: The following updates are downloaded and ready for
installation. This computer is currently scheduled to install these updates
on Monday, February 28, 2005 at 5:00 AM. - Security Update for Microsoft
..NET Framework, Version 1.0 SP3, English (KB886906)"

A bit later, you see where it fails and it records the following two errors
messages (shown below). Any idea how to fix it?

Arch

Event Type: Error
Event Source: Automatic Updates
Event Category: Installation
Event ID: 20
Date: 02/28/2005
Time: 4:59:52 AM
User: N/A
Computer:
Description:
Installation Failure: Windows failed to install the following update.
- Security Update for Microsoft .NET Framework, Version 1.0 SP3, English
(KB886906)

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 11706
Date: 02/28/2005
Time: 4:59:51 AM
User: N/A
Computer:
Description:
Product: Microsoft .NET Framework (English) -- Error 1706.No valid source
could be found for product Microsoft .NET Framework (English). The Windows
installer cannot continue.
Data:
0000: 7b 42 34 33 33 35 37 41 {B43357A
0008: 41 2d 33 41 36 44 2d 34 A-3A6D-4
0010: 44 39 34 2d 42 35 36 45 D94-B56E
0018: 2d 34 33 43 34 34 44 30 -43C44D0
0020: 39 45 35 34 38 7d 9E548}

Several of this have been asking about this same issue here. The MVP
*swears* that only 6 people in the entire world have been affected by it. I
guess you're number 7. :^ \

Yours truly,
Uncle Beer

Well, I may like to add here,,,

I first encountered dotnet updates issue back in Sep 2004 (don't exactly
remember the dates), when the first of updates on dotnet were released after
xp sp2. I remember then that I had to first get rid of both dotnets (version
1.0 and 1.1) from my pc and then install them again. (Removing them was
painful though)..

Now again as I received the dotnet updates notification on my pc, I knew
something was in the pipeline. As expected, I had to remove them manually,
and install them one by one alongwith the servicepacks plus hotfixes.
(Version 1.0 + SP1 + SP2 + hotfix for SP2 + SP3 + hotfix for sp3. Likewise
Version 1.1 + SP1 + hotfix).

For those of you who are facing this problem, I am posting the link that
will help you manually remove these and then you will have to download the
redistributable and service packs and install them one after the other.

http://support.microsoft.com/default...b;en-us;824643


"uncle beer" <> wrote in message
news:cvvhhq$8qt$...
> Several of this have been asking about this same issue here. The MVP
> *swears* that only 6 people in the entire world have been affected by it.
> I guess you're number 7. :^ \
>
> Yours truly,
> Uncle Beer
>

To say that it has only happened to 7 people is very inaccurate by Microsoft.
What are they doing? Counting for every 100 people it counts as 1 or are
they really clueless to how many users are complaining of the same issue?


"Usman" wrote:

> Well, I may like to add here,,,
>
> I first encountered dotnet updates issue back in Sep 2004 (don't exactly
> remember the dates), when the first of updates on dotnet were released after
> xp sp2. I remember then that I had to first get rid of both dotnets (version
> 1.0 and 1.1) from my pc and then install them again. (Removing them was
> painful though)..
>
> Now again as I received the dotnet updates notification on my pc, I knew
> something was in the pipeline. As expected, I had to remove them manually,
> and install them one by one alongwith the servicepacks plus hotfixes.
> (Version 1.0 + SP1 + SP2 + hotfix for SP2 + SP3 + hotfix for sp3. Likewise
> Version 1.1 + SP1 + hotfix).
>
> For those of you who are facing this problem, I am posting the link that
> will help you manually remove these and then you will have to download the
> redistributable and service packs and install them one after the other.
>
> http://support.microsoft.com/default...b;en-us;824643
>
>
> "uncle beer" <> wrote in message
> news:cvvhhq$8qt$...
> > Several of this have been asking about this same issue here. The MVP
> > *swears* that only 6 people in the entire world have been affected by it.
> > I guess you're number 7. :^ \
> >
> > Yours truly,
> > Uncle Beer
> >
>
>
>

I guess that makes me number 8

I've been trying since the NET framework security update was first made
available ... it hasn't been successful on ANY of our four computers.

The security update for NET framework has attempted at least twice a week on
each of the machines and has failed each and every time.

I'd like to figure out how to tell the damned thing I'm not interested in
updating NET framework any more until they (MS) gets the damned installer
fixed so that it will function properly.

"uncle beer" wrote:

> Several of this have been asking about this same issue here. The MVP
> *swears* that only 6 people in the entire world have been affected by it. I
> guess you're number 7. :^ \
>
> Yours truly,
> Uncle Beer
>
>
>

I've had a support request into MS since 2/16 and haven't had a
resolution yet.

Bill
"Scorpion~" <Scorpion~@discussions.microsoft.com> wrote in message
news:ACF73285-DC27-4AFB-B747-...
I guess that makes me number 8

I've been trying since the NET framework security update was first made
available ... it hasn't been successful on ANY of our four computers.

The security update for NET framework has attempted at least twice a
week on
each of the machines and has failed each and every time.

I'd like to figure out how to tell the damned thing I'm not interested
in
updating NET framework any more until they (MS) gets the damned
installer
fixed so that it will function properly.

"uncle beer" wrote:

> Several of this have been asking about this same issue here. The MVP
> *swears* that only 6 people in the entire world have been affected by
> it. I
> guess you're number 7. :^ \
>
> Yours truly,
> Uncle Beer
>
>
>

"Bill Sharpe" <> wrote in message
news:...
> I've had a support request into MS since 2/16 and haven't had a
> resolution yet.

Perhaps you could try the suggestions for diagnostics that I gave
to David Jenkins? His symptom might be different but the technique
should be the same.

http://www.microsoft.com/windowsxp/e...3-3b616a064f3f

I would be especially interested in any reports which make use of the
idea of adding logging options to the msiexec command. However,
I don't think it should be necessary to go that far to get this problem
resolved, especially if you don't care if it is going to be done manually
instead of automatically. Others have done it apparently by uninstalling
and starting over; for example:

http://www.microsoft.com/windowsxp/e...7-dafbfe792b3d

(Web interface search for
blackmischief msiexec
)


Good luck

Robert Aldwinckle
---