Re: SP2 Won't Install





Hi Mow

I take on board what you say.

However, in the partial log posted here neither FATAL or WARNING appear.
The system seems to believe the User cancelled when the user is unaware
that they cancelled! Of course only a part of the Log is posted here.

At your invitation a copy of the full log was posted by the OP to you
by email on 27 December. I have been watching for your reply but nothing
has appeared. I would be interested to know what you made of it?

Robert was picking me up for interpreting the extended error code =
0xf00d from the log to an 0x80242008 error code.

Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Hi Mow

I take on board what you say.

However, in the partial log posted here neither FATAL or WARNING appear.
The system seems to believe the User cancelled when the user is unaware
that they cancelled! Of course only a part of the Log is posted here.

At your invitation a copy of the full log was posted by the OP to you
by email on 27 December. I have been watching for your reply but nothing
has appeared. I would be interested to know what you made of it?

Robert was picking me up for interpreting the extended error code =
0xf00d from the log to an 0x80242008 error code.

Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~


----- Original Message ----- From: "MowGreen [MVP]" <mowgreen@xxxxxxxxxxxxx>
Newsgroups: microsoft.public.windowsupdate
Sent: Thursday, January 04, 2007 3:37 PM
Subject: Re: SP2 Won't Install


The problem is I understand that you get a lot of lines in these update logs which look like failures when they can be safely disregarded.

Yeppers, Gerry. Start at the *end* of the log and work backwards. Knowing which errors are meaningless and which contain a clue would confuse Sherlock Holmes.

From : http://support.microsoft.com/kb/902093

Locating Failures in the log file
If you received a specific error message on the Windows Update Web site, follow these steps:
1. Open the Windowsupdate.log log file in Notepad. 2. On the Edit menu, click Find, and then search for the specific error message. Note The Web site displays the final error message. This final error message may have been caused by a failure that is described earlier in the Windowsupdate.log log file.
Additionally, if you do not know which error occurred on the Windows update Web site or you want to find more information about a failure by Automatic Updates, search for the following key words:
• FATAL • WARNING Note Not all warnings are critical errors. Start with the fatal errors and then work to the top of the Windowsupdate.log log file to make sure that you have identified the correct error message.


MowGreen [MVP 2003-2007]
===============
*-343-* FDNY
Never Forgotten
===============




.



Relevant Pages

  • ndiscvt make failure
    ... Make of ndiscvt breaks with the following error message. ... Warning: Object directory not changed from original ... *** Error code 1 ...
    (freebsd-net)
  • RE: windows update
    ... You may receive an error message when you search for available updates on ... the Windows Update Web site 0x80072EE7 error code ...
    (microsoft.public.windowsupdate)
  • Re: MP.MSI exited with return code: 1603
    ... WARNING: Network service account not available, ... Method 'DeleteExtensionFileRecord' failed with error code ... Successfully created virtual directory application ...
    (microsoft.public.sms.setup)
  • Re: libXfont install problems from ports
    ... "FontEncPtr" ... fontencc.c:42: warning: nested extern declaration of `FontEncFromXLFD' ... *** Error code 1 ...
    (freebsd-questions)
  • Re: stress2 on other operating systems
    ... main.c:4: warning: type defaults to `int' in declaration of `__FBSDID' ... main.c:59: warning: implicit declaration of function `arc4random_stir' ... options.c:2: error: parse error before string constant ... *** Error code 1 ...
    (comp.unix.bsd.freebsd.misc)