WSUS 3.1 - client returned error 0x80070002

Hello, I am using WSUS 3.1. Computer with windows2003server(x64) has problem.
WSUS console sees the client, but will not offer any update. In his
windowsupdate.log is this message: "EEHndlr WARNING: Failed to populate
ServiceStartup entries in Cache: error 0x80070002". Other computers with
WindowsXP are fine. I tried to delete a directory
%windir%/softwaredistribution and the following registry entries:
SusClientId, SusClientIDValidation in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\WindowsUpdate,
reinstall windowsupdateagent, re-registered regsvr32
%windir%\syswow64\wups2.dll. But no solution ... :-(

addition: wsus client diagnostic tool reports error. Is located here
http://volny.cz/dan.dy/error_wsus.JPG

Any ideas? Thank you!

Having exact same issue / errors ..
All workstations and x86 servers update fine, only the other 2k3x64 servers
are having issues. multipule wsus servers - 1 on x86 the other on - x64.
Wsus - Cliendiag errors with:
GetAUSettingsRegistry(false, TEXT("SusServerVersion"), &dwSusVersion) failed
wit
h hr=0x80070002

The system cannot find the file specified.




"Danda" wrote:

> Hello, I am using WSUS 3.1. Computer with windows2003server(x64) has problem.
> WSUS console sees the client, but will not offer any update. In his
> windowsupdate.log is this message: "EEHndlr WARNING: Failed to populate
> ServiceStartup entries in Cache: error 0x80070002". Other computers with
> WindowsXP are fine. I tried to delete a directory
> %windir%/softwaredistribution and the following registry entries:
> SusClientId, SusClientIDValidation in
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\WindowsUpdate,
> reinstall windowsupdateagent, re-registered regsvr32
> %windir%\syswow64\wups2.dll. But no solution ... :-(
>
> addition: wsus client diagnostic tool reports error. Is located here
> http://volny.cz/dan.dy/error_wsus.JPG
>
> Any ideas? Thank you!

"PHD" <> wrote in message
news:2F7175F8-82EC-4602-8522-...
> Having exact same issue / errors ..
> All workstations and x86 servers update fine, only the other 2k3x64
> servers
> are having issues. multipule wsus servers - 1 on x86 the other on - x64.
> Wsus - Cliendiag errors with:
> GetAUSettingsRegistry(false, TEXT("SusServerVersion"), &dwSusVersion)
> failed
> wit
> h hr=0x80070002

The ClientDiagTool is 32-bit only; this looks like a run on an x64 machine.

Run the CDT on the x86 system and post the results. We'll go from there.



--
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 MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Lawrence,
Is there a CDT for the x64 (the x64 boxes happens to be 2k3r2 outlying
servers) .. was previously running on wsus 2.0 and upgraded to 3.0 sp1
x86 wrkstation seem to be working fine.

"Lawrence Garvin [MVP]" wrote:

> "PHD" <> wrote in message
> news:2F7175F8-82EC-4602-8522-...
> > Having exact same issue / errors ..
> > All workstations and x86 servers update fine, only the other 2k3x64
> > servers
> > are having issues. multipule wsus servers - 1 on x86 the other on - x64.
> > Wsus - Cliendiag errors with:
> > GetAUSettingsRegistry(false, TEXT("SusServerVersion"), &dwSusVersion)
> > failed
> > wit
> > h hr=0x80070002
>
> The ClientDiagTool is 32-bit only; this looks like a run on an x64 machine.
>
> Run the CDT on the x86 system and post the results. We'll go from there.
>
>
>
> --
> 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 MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

"PHD" <> wrote in message
news:F081CE9E-D9B7-4EE3-A417-...
> Lawrence,
> Is there a CDT for the x64

Unfortunately, no. I'm lobbying for a 64-bit version... but I've not yet
heard any encouraging responses.

> was previously running on wsus 2.0 and upgraded to 3.0 sp1

Well, here's a whole host of opportunities for things to go haywire.....
upgrading WSUSv2 to WSUSv3SP1. :-)

Let's start with the WSUSv3SP1 Release Notes. Have you reviewed the Release
Notes to verify that *nothing* documented in those dozens of pages is
applicable to your environment?

And the CDT from the x86 box would still be useful.

--
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 MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

I had to uninstall 2.0 and fresh install 3.0sp1 inorder to get it to work a
few weeks ago. No I really didn't review in detail. I'll check that out
later today.

from my wrkstation:

WSUS Client Diagnostics Tool

Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is running. . . PASS
Wuaueng.dll version 7.2.6001.788. . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use

Checking Connection to WSUS/SUS Server
WUServer = http://dc01:8530
WUStatusServer = http://dc01:8530
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Connection to server. . . . . . . . . . . . . . . . . . PASS
SelfUpdate folder is present. . . . . . . . . . . . . . PASS


"Lawrence Garvin [MVP]" wrote:

> "PHD" <> wrote in message
> news:F081CE9E-D9B7-4EE3-A417-...
> > Lawrence,
> > Is there a CDT for the x64
>
> Unfortunately, no. I'm lobbying for a 64-bit version... but I've not yet
> heard any encouraging responses.
>
> > was previously running on wsus 2.0 and upgraded to 3.0 sp1
>
> Well, here's a whole host of opportunities for things to go haywire.....
> upgrading WSUSv2 to WSUSv3SP1. :-)
>
> Let's start with the WSUSv3SP1 Release Notes. Have you reviewed the Release
> Notes to verify that *nothing* documented in those dozens of pages is
> applicable to your environment?
>
> And the CDT from the x86 box would still be useful.
>
> --
> 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 MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

"PHD" <> wrote in message
news:48FF2B1E-F039-42FE-B41A-...

>I had to uninstall 2.0 and fresh install 3.0sp1 inorder to get it to work a
> few weeks ago. No I really didn't review in detail. I'll check that out
> later today.

Well, if you fully uninstalled 2.0 and then installed 3.0 sp1, the "upgrade"
isn't an upgrade, and those issues are no longer relevant.

>
> from my wrkstation:
>
> WSUS Client Diagnostics Tool

The workstation is configured correctly.. and I misunderstood the entire
scenario from your original post.

> only the other 2k3x64 servers are having issues

To clarify my new understanding -- the *only* systems showing issues are the
Windows Server 2003 x64 systems. Yes?

Since the CDT is not useful on those systems, please perform this procedure
on one of those Win2003 x64 systems to get the necessary diagnostic
information:

1. Record the system time.
2. Restart the Automatic Updates Service (net stop/start wuauserv).
3. Run this command: wuauclt /resetauthorization /detectnow.
4. Wait 30 minutes.
5. Post all of the entries from the WindowsUpdate.log starting at the time
recorded in step #1.




--
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 MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

Hello Lawrence, I Ran the CDT on the x86 system and here is the results:

WSUS Client Diagnostics Tool

Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is not running. PASS
Wuaueng.dll version 7.2.6001.788. . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use

Checking Connection to WSUS/SUS Server
WUServer = http://BYZWIN:8530
WUStatusServer = http://BYZWIN:8530
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Connection to server. . . . . . . . . . . . . . . . . . PASS

WinHttpDownloadFileToMemory(szURLDest, NULL, 0, NULL, NULL, NULL,
&downloadBuffe
r) failed with hr=0x80072efd

A connection with the server could not be established

Press Enter to Complete


"Lawrence Garvin [MVP]" wrote:

> "PHD" <> wrote in message
> news:2F7175F8-82EC-4602-8522-...
> > Having exact same issue / errors ..
> > All workstations and x86 servers update fine, only the other 2k3x64
> > servers
> > are having issues. multipule wsus servers - 1 on x86 the other on - x64.
> > Wsus - Cliendiag errors with:
> > GetAUSettingsRegistry(false, TEXT("SusServerVersion"), &dwSusVersion)
> > failed
> > wit
> > h hr=0x80070002
>
> The ClientDiagTool is 32-bit only; this looks like a run on an x64 machine.
>
> Run the CDT on the x86 system and post the results. We'll go from there.
>
>
>
> --
> 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 MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>
>

I found that this error caused by a firewall. But I do not know which other
port must be allowed. Port 8530 to the server is allowed ...

"Danda" <> wrote in message
news:0934F636-A099-4144-8DBA-...
>I found that this error caused by a firewall. But I do not know which other
> port must be allowed. Port 8530 to the server is allowed ...

Port 80 must also be allowed.

In addition to the firewall as a possibility, also be sure that the client
machine is able to properly access the necessary DNS resources to resolve
the name BYZWIN, and that the WSUS Server knows how to properly route the
return traffic to the client.

--
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 MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin