"Euclid" <Euclid@discussions.microsoft.com> wrote in message
news:5018C409-277D-464A-8A22-731F9560D12F@microsoft.com...
> Robert,
>
> I'd just like to say you're a STAR!!...
>
> I followed your advice about trying to diagnose my symptom and decided to
> plough through the WU log and came across the following..
>
> 2005-11-10 21:29:54 1644 7bc Agent WARNING: Failed to evaluate Installed
> rule, updateId = {ED300F67-421C-4C08-B3BA-F35C55F3B427}.100, error =
> 0x80040154
> 2005-11-10 21:29:54 1644 7bc Agent WARNING: Failed to evaluate Installed
> rule, updateId = {794F5418-EDF1-44D6-97F4-8D693BC4CD97}.17, error = 0x80040154
> 2005-11-10 21:29:54 1644 7bc EEHndlr FATAL: MSI DLL version is 3.0. Version
> 3.1 is required.
> 2005-11-10 21:29:54 1644 7bc Agent WARNING: Failed to evaluate Installed
> rule, updateId = {6248B8B1-FFEB-DBD9-887A-2ACF53B09DFE}.102, error =
> 0x80241001
> 2005-11-10 21:29:54 1644 7bc EEHndlr FATAL: MSI DLL version is 3.0. Version
> 3.1 is required.
That's a clear message for you. <w>
So, there was no 0x80070005 code after all?
FYI searching for just the 0x80241001 code finds this answer
from TaurArian [MVP] in August:
http://www.microsoft.com/communities...074&sloc=en-us
>
> I did a search for msi.dll and replaced the offending file in
> c:\windows\system32\ with version 3.1 also found on c drive. Rebooted and
> updated windows no problem.
>
> Once again thanks for your time and effort invested in my problem, that goes
> for you arionly also.
I only suggested you try a rational approach. You took it.
Well done!
Thanks for the feedback.
Robert
---
>
> I'm one happy bunny again,
> Denis
>
> "Robert Aldwinckle" wrote:
>
>> "Euclid" <Euclid@discussions.microsoft.com> wrote in message
>> news:A3233225-B684-448E-B691-4AF37E23237B@microsoft.com...
>> > Hi,
>> > I've recently upgraded my graphics card and soundcard and had cause to
>> > repair win xp sp2 installation. Now when i visit the win update i get the
>> > above error.
>> >
>> > Are the two related?. win xp sp2 was previously activated successfully prior
>> > to the installation of the two cards.
>> >
>> > How do I go about fixing my problem?
>>
>>
>> If Arionly's tip to try using the WU troubleshooter doesn't lead to
>> a resolution, try a search?
>>
>> Since you are using the web interface to newsgroups you can do that
>> simply by pressing Alt-7 and entering the code in the search input box.
>>
>> Hmm... that's a bit overwhelming, even using the filters. ;}
>>
>>
>> Instead try using Google Groups:
>>
>> http://groups.google.com/group/micro...ead5ae515d0dce
>>
>> (Google Groups search for
>> (0x80070005 OR 80070005) (MSFT OR MVP) group:microsoft.*.windowsupdate
>> - sorted by date to try to capture current thinking
>> )
>>
>>
>> The most useful thing you could do though, if just taking stabs at others'
>> reported resolutions doesn't help, is start diagnosing your symptom,
>> e.g. search for any files which were updated on that day which contain
>> instances of that 80070005 string. You could also search for the
>> decimal equivalent -2147024891 but usually when it appears the hex
>> is given too. I suggest that more general approach to finding logs, etc.
>> because sometimes the diagnostics filenames are obscure, especially
>> when an unusual install is being done.
>>
>>
>> HTH
>>
>> Robert Aldwinckle
>> ---
>>
>>
>>