"eristoff" <> wrote in message
news:...
>
> When I said the same error codes I meant these:
> “2629.407: Update.exe extended error code = 0xf070
> 2629.407: Update.exe return code was masked to 0x643 for MSI custom
> action
> compliance.”
Those aren't interesting. Basically just codes saying it didn't work
but not telling you anything about why. The one that I extracted
from your link was the first error symptom and I suspect that if anybody
was familiar with ToGac.exe and its return codes that it would be
sufficient to know what it was telling us about your System.xml.dll
Perhaps even without such documentation it would have been enough
to know that there was something different about that module
compared to the previous one which was processed by the same utility:
System.Windows.Forms.dll E.g. perhaps you could have used one of
the .NET Framework admin tools to check on the status of both of those
modules. Etc.
>
> I started following this thread:
> http://www.m c s
> e.ms/showthread.php?threadid=1530401&perpage=10&pagenum ber=1
> Which is based on this MS article:
> http://www.microsoft.com/technet/scr.../help/wmi.mspx
> (the “*Windows Server 2003, Service Pack 1*” part)
>
> But it still didn’t worked…
>
> So, how did we do it? We downloaded the “*The WMI Diagnosis Utility*“
> http://www.microsoft.com/downloads/d...displaylang=en
> And basically searched for the missing files and placed them on the
> right folders…
>
> SP1 instaled… finally.
Good work. But I'm curious why did you used that diagnostic tool
(for WMI specifically) instead of a more general one for the .NET Framework?
Anyways, thanks for reporting your solution.
Robert
---
>
>
> --
> eristoff
> ------------------------------------------------------------------------
> eristoff's Profile: http://forums.techarena.in/member.php?userid=18023
> View this thread: http://forums.techarena.in/showthread.php?t=336010
>
> http://www.techarena.in
>