Clientdiag Fail with error hr=0x80070005
LENOBLE@discussions.microsoft.com Guillaume LENOBLE
I havre installed WSUS 3 SP1 on w2k3 Server
3200 computers are show in the admin console.
I am deploying Windows XP SP3 on my computers
For the moment, 450 computers are upgraded on SP3. However, 1800 Computers
are not download or install this service pack.
When i launch "clientdiag.exe", this error occurs :
pAutomaticUpdates->get_Settings(&pAutomaticUpdatesSettings) failed with
hr=0x80070005
In the file windowsupdate.log, i havre many error :
EEHndlr FATAL: MSI DLL version is 2.0. Version 3.1 is required.
2009-04-24 09:06:43:357 1040 668 Agent WARNING: Failed to evaluate Installed
rule, updateId = {EB658C03-7D9F-4BFA-8EF3-C113B7466E73}.100, hr = 80241001
2009-04-24 09:06:43:779 1040 668 EEHndlr FATAL: MSI DLL version is 2.0.
Version 3.1 is required.
2009-04-24 09:06:43:779 1040 668 Agent WARNING: Failed to evaluate Installed
rule, updateId = {1403F223-A63F-F572-82BA-C92391218055}.110, hr = 80241001
2009-04-24 09:06:43:810 1040 668 EEHndlr FATAL: MSI DLL version is 2.0.
Version 3.1 is required.
2009-04-24 09:06:43:810 1040 668 Agent WARNING: Failed to evaluate Installed
rule, updateId = {7880102A-F24D-4C01-8971-8D375BBC0F28}.100, hr = 80241001
2009-04-24 09:06:44:482 1040 668 EEHndlr FATAL: MSI DLL version is 2.0.
Version 3.1 is required.
2009-04-24 09:06:44:482 1040 668 Agent WARNING: Failed to evaluate Installed
rule, updateId = {2CDBFA44-E2CB-4455-B334-FCE74DED8EDA}.100, hr = 80241001
2009-04-24 09:06:44:529 1040 668 EEHndlr FATAL: MSI DLL version is 2.0.
Version 3.1 is required.
2009-04-24 09:06:44:529 1040 668 Agent WARNING: Failed to evaluate Installed
rule, updateId = {0A487050-8B0F-4F81-B401-BE4CEACD61CD}.109, hr = 80241001
2009-04-24 09:06:44:638 1040 668 EEHndlr FATAL: MSI DLL version is 2.0.
Version 3.1 is required.
2009-04-24 09:06:44:638 1040 668 Agent WARNING: Failed to evaluate Installed
rule, updateId = {0C6AF366-17FB-4125-A441-BE87992B953A}.100, hr = 80241001
2009-04-24 09:06:44:638 1040 668 EEHndlr FATAL: MSI DLL version is 2.0.
Version 3.1 is required.
2009-04-24 09:06:44:638 1040 668 Agent WARNING: Failed to evaluate Installed
rule, updateId = {06BDF56C-1360-4BB9-8997-6D67B318467C}.100, hr = 80241001
2009-04-24 09:06:44:998 1040 668 EEHndlr FATAL: MSI DLL version is 2.0.
Version 3.1 is required.
For informations , i've already approve Windows installer 3.1, BITS, etc...
(which is needed (according to wsus)).
Can you help me ? i don't have any idea.
Thanks in advance
Cordialy
Guillaume LENOBLE
(Ps: excuse for my english)
Lawrence Garvin [MVP]
message news:0832A210-25E1-4313...@microsoft.com...
> I am deploying Windows XP SP3 on my computers
> For the moment, 450 computers are upgraded on SP3. However, 1800 Computers
> are not download or install this service pack.
>
> When i launch "clientdiag.exe", this error occurs :
> pAutomaticUpdates->get_Settings(&pAutomaticUpdatesSettings) failed with
> hr=0x80070005
The 0x80070005 is generally an Access Denied error. Running on what looks
like a call to get registry configuration data, I'd check to make sure the
registry hasn't been "secured". The HKLM\Software\Policies key needs to be
readable by all authenticated users and the SYSTEM account.
But this could also be a manifestation (side-effect) of the issue described
below, which I'm more inclined to think is the cause in your situation.
> In the file windowsupdate.log, i havre many error :
>
> EEHndlr FATAL: MSI DLL version is 2.0. Version 3.1 is required.
This is exactly what it says. The Windows Installer has not been upgraded to
v3.1.
> For informations , i've already approve Windows installer 3.1, BITS,
> etc...
> (which is needed (according to wsus)).
Yes, approving it is good, but that doesn't get it installed if there is a
precluding issue.
Among other things, there is a known issue when applying XP Service Pack 3
directly to an XPSP2 slipstreamed installation (and I imagine it's likey to
also occur on downlevel XP installations as well). XP SP3 has a defect in
that it fails to properly register the WUPS2.DLL file The library doesn't
exist in downlevel WUA installations, but was introduced by a WUA build
significantly predating the release of SP3. SP3 adds the file (assuming it
already exists and is registered), but on a pure SP2 system this is not the
case.
See this article for more details: http://support.microsoft.com/kb/956708
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
Guillaume LENOBLE
I have registered all dlls and i have read kb956708. If i'm understand, I
should update windows installer and SUS client on my computers (3600
computers). But if WSUS don't work, how do I install the update software on
my computer? script, GPO, ?????
in advance Thank
cordialy
Guillaume LENOBLE (FRANCE)
Lawrence Garvin [MVP]
message news:F9DA8324-29DA-4F01...@microsoft.com...
> Thanks for you reply,
>
> I have registered all dlls and i have read kb956708. If i'm understand, I
> should update windows installer and SUS client on my computers (3600
> computers). But if WSUS don't work, how do I install the update software
> on
> my computer? script, GPO, ?????
If you're scenario is that SP3 was directly applied to a fresh XPSP2
installation, then the steps to remediate are in that KB article, and once
the desktop is fixed, the WSUS/WUA will take care of everything else.
If that's not the scenario, or something else is wrong, then the answer to
the question is you Fix the WSUS!
So, if you've performed the steps in KB956708 and it's still not working,
then we go back to the same diagnostic steps:
1. Run the Client Diagnostic Tool. Post the results.
2. Post the most recent detection event from %windir%\WindowsUpdate.log
And we'll look at the next possible issue.
Guillaume LENOBLE
i have upgraded windows installer (3.1) and agent client on the computer.
700 SP 3 are installed and 780 are downloaded. However, 1700 computers are
not applicable to SP3. I have verified if RDP 6 was installed. but no.
I don't understand why the SP3 isn't applicable. My computers are Windows XP
SP1 and SP2.
No error in the "Windowsupdate.log" on the affected computers.
can you continue to help me please ?
thanks in advance
Cordialy
Guillaume
![Harry Johnston [MVP]'s profile photo](http://lh3.googleusercontent.com/a-/ALV-UjWpkBAPqvc839nzAtvH7xG03OwcxExyoyKpBgg3G7rKJeLEHQ=s40-c)
Harry Johnston [MVP]
> i have upgraded windows installer (3.1) and agent client on the computer.
> 700 SP 3 are installed and 780 are downloaded. However, 1700 computers are
> not applicable to SP3. I have verified if RDP 6 was installed. but no.
> I don't understand why the SP3 isn't applicable. My computers are Windows XP
> SP1 and SP2.
> No error in the "Windowsupdate.log" on the affected computers.
Perhaps the machines are affected by the Intel/AMD cloning issue? This could
happen if (a) you used the preinstalled version of Windows from certain
manufacturers, most notably HP; or (b) you use cloning and don't have separate
images for Intel and AMD processors.
Harry.
Guillaume LENOBLE
I've verified, all my computers have Intel Processor and the ghost master
hadn't be realized with a preinstalled Windows version.
I have searched the name of Update which are required to install SP3 on a
windows XP SP1. How can i know that ?
Thanks
Guillaume
Lawrence Garvin [MVP]
> I have searched the name of Update which are required to install SP3 on a
> windows XP SP1. How can i know that ?
The best way to determine the updates you need to upgrade XPSP1 to XPSP3 is
to set up a test environment with a test WSUS Server, and then approve ALL
updates for the XPSP1 system. The Windows Update Agent will determine which
updates must actually be installed, and install them. Then you can review
the WSUS Console and the client's WindowsUpdate.log to see which updates are
required, and those are the ones you should approve in your production
environment.
For an example of how I did this to determine which updates were needed for
XPSP2 on an XPSP1 system, review this article:
http://wsusinfo.onsitechsolutions.com/articles/012.htm
Dave Mills
detected as needed and then repeat this un till there are no further updates
detected. The approved updates are those required. You can do this on the
production server if you like as these update will eventually be needed there
until all are applied.
On Mon, 11 May 2009 08:08:28 -0500, "Lawrence Garvin [MVP]"
<lawr...@news.postalias> wrote:
>"Guillaume LENOBLE" <Guillaum...@discussions.microsoft.com> wrote in
>message news:E2AC0329-D0A3-4637...@microsoft.com...
>
>> I have searched the name of Update which are required to install SP3 on a
>> windows XP SP1. How can i know that ?
>
>The best way to determine the updates you need to upgrade XPSP1 to XPSP3 is
>to set up a test environment with a test WSUS Server, and then approve ALL
>updates for the XPSP1 system. The Windows Update Agent will determine which
>updates must actually be installed, and install them. Then you can review
>the WSUS Console and the client's WindowsUpdate.log to see which updates are
>required, and those are the ones you should approve in your production
>environment.
>
>For an example of how I did this to determine which updates were needed for
>XPSP2 on an XPSP1 system, review this article:
>http://wsusinfo.onsitechsolutions.com/articles/012.htm
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
Guillaume LENOBLE
I have approuved the SP2 for few computers with a limited date in the past
(to apply SP2 immediatly). This method install SP2 and reboot the computers 5
minutes after. After the reboot the computer detect the SP3. However, if i
force the installation, the computer reboot. I don't want this. I can not
allow an automatic restart of my production computers. What is the method ?
in a other hand, i should deleted softwaredistribution folder and restart
wuauserv service to detect SP2 for installation. how can I avoid doing this
on all my computers ?
Thanks for you help
Have a good day.
Guillaume
Dave Mills
<Guillaum...@discussions.microsoft.com> wrote:
>Hello,
>
>I have approuved the SP2 for few computers with a limited date in the past
>(to apply SP2 immediatly). This method install SP2 and reboot the computers 5
>minutes after. After the reboot the computer detect the SP3. However, if i
>force the installation, the computer reboot. I don't want this. I can not
>allow an automatic restart of my production computers. What is the method ?
If you install a service pack you must reboot the computer. Your only choice is
to set the installation happen at the scheduled time (3 am by default) or to
install the service pack manually. I would do the latter and simple install SP3
without installing SP2 at all.
Guillaume LENOBLE
To solve the problem, we chose to go through to install SP2 after SP3. This
works for many computer.
but 800 computers not download SP2. There is no error in the files
"windowsupdates.log" and "softwaredistribution.log"
Have an idea to help me.
Best regards
Dave Mills
I would not expect SP2 to install if SP3 is already installed.
. Using WSUS On Wed, 3 Jun 2009 02:33:01 -0700, Guillaume LENOBLE