Re: + Proxy list used = proxy:8080 (WindowsUpdate.log)

[[ Forwarded to WSUS newsgroup
(microsoft.public.windows.server.update_services) via crosspost as a
convenience to OP.

On the web:
http://www.microsoft.com/communities...pdate_services

In your newsreader:
news://msnews.microsoft.com/microsof...pdate_services
]]

Claude Lachapelle wrote:
> I would like to know where Automatic Updates are getting this setting
> (Proxyservernameort), since I never configured a proxy on this server,
> and
> the one specified do not exist anymore in the the company.
>
> And due to that, Automatic Updates are failing all communications with the
> WSUS server...
>
> So, I cleared ALL Connections configuration under Internet Settings in the
> registry, run proxycfg -d, re-installed Automatic Updates with the special
> rundll command, reset the SoftwareDistribution directory many times,
> reboot
> the server, STILL HAVE THE SAME PROBLEM:
>
> + Proxy list used = proxy:8080
>
> Where Automatic Updates are getting this setting?
>
> Thanks.
>
> Claude Lachapelle
> System Administrator, MCSE

> Claude Lachapelle wrote:
>> I would like to know where Automatic Updates are getting this setting
>> (Proxyservernameort), since I never configured a proxy on this server,
>> and the one specified do not exist anymore in the the company.

The WUA (Automatic Updates) uses the WinHTTP proxy configuration.

On WinXP/2003 machines (and earlier) you can view these settings with the
simple command: PROXYCFG

On WinVista/2008 machines, you'll need to use 'netsh winhttp show proxy'

>> So, I cleared ALL Connections configuration under Internet Settings in
>> the
>> registry, run proxycfg -d, re-installed Automatic Updates with the
>> special
>> rundll command, reset the SoftwareDistribution directory many times,
>> reboot the server, STILL HAVE THE SAME PROBLEM:
>>
>> + Proxy list used = proxy:8080
>>
>> Where Automatic Updates are getting this setting?

In that case.. almost certainly from a POLICY.

>> Claude Lachapelle
>> System Administrator, MCSE


--
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/pro...awrence.Garvin

> Claude Lachapelle wrote:

>> I would like to know where Automatic Updates are getting this setting
>> (Proxyservernameort), since I never configured a proxy on this
>> server, and the one specified do not exist anymore in the the company.

Could you please run the WSUS client diagnostics tool on the affected client and
post the results?

<http://technet.microsoft.com/en-us/wsus/bb466192.aspx>

http://technet.microsoft.com/en-us/wsus/bb466192.aspx

Also post the results of running proxycfg with no arguments.

Harry.

>>
>> And due to that, Automatic Updates are failing all communications with
>> the
>> WSUS server...
>>
>> So, I cleared ALL Connections configuration under Internet Settings in
>> the
>> registry, run proxycfg -d, re-installed Automatic Updates with the
>> special
>> rundll command, reset the SoftwareDistribution directory many times,
>> reboot
>> the server, STILL HAVE THE SAME PROBLEM:
>>
>> + Proxy list used = proxy:8080
>>
>> Where Automatic Updates are getting this setting?
>>
>> Thanks.
>>
>> Claude Lachapelle
>> System Administrator, MCSE
>

GPRESULT, and no GPO contain proxy information, only WSUS settings. Very
strange, and here the result of PROXYCFG command:

Current WinHTTP proxy settings under:
HKEY_LOCAL_MACHINE\
SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\
WinHttpSettings :

Direct access (no proxy server).

Another not easy one... eheheheheh!

"Lawrence Garvin [MVP]" wrote:

> > Claude Lachapelle wrote:
> >> I would like to know where Automatic Updates are getting this setting
> >> (Proxyservernameort), since I never configured a proxy on this server,
> >> and the one specified do not exist anymore in the the company.
>
> The WUA (Automatic Updates) uses the WinHTTP proxy configuration.
>
> On WinXP/2003 machines (and earlier) you can view these settings with the
> simple command: PROXYCFG
>
> On WinVista/2008 machines, you'll need to use 'netsh winhttp show proxy'
>
> >> So, I cleared ALL Connections configuration under Internet Settings in
> >> the
> >> registry, run proxycfg -d, re-installed Automatic Updates with the
> >> special
> >> rundll command, reset the SoftwareDistribution directory many times,
> >> reboot the server, STILL HAVE THE SAME PROBLEM:
> >>
> >> + Proxy list used = proxy:8080
> >>
> >> Where Automatic Updates are getting this setting?
>
> In that case.. almost certainly from a POLICY.
>
> >> Claude Lachapelle
> >> System Administrator, MCSE
>
>
> --
> 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/pro...awrence.Garvin
>
>

Here the result of ClientDiag.exe:

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 5.7.3790.3959 . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 3 : Notify Prior to 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://wsus01.domain.com
WUStatusServer = http://wsus01.domain.com
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS

GetAUSettingsRegistry(false, TEXT("SusServerVersion"), &dwSusVersion) failed
wit
h hr=0x80070002

The system cannot find the file specified.

Here what we got in WindowsUpdate.log:

2009-05-08 09:15:40-0400 800 c64 Service status is now SERVICE_RUNNING
2009-05-08 09:16:25-0400 800 c64 start delayed initialization of WU client
2009-05-08 09:16:25-0400 800 c64 BatchFlushAge = 16290.
2009-05-08 09:16:25-0400 800 c64 SamplingValue = 203, sampling required = Yes
2009-05-08 09:16:25-0400 800 c64 Reopened existing event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{4FAA8C FD-6315-4049-AF0A-BC5802CDFC22}.bin for writing.
2009-05-08 09:16:25-0400 800 c64 Successfully initialized event uploader
for server 3da21691-e39d-4da6-8a4b-b43877bcb1b7.
2009-05-08 09:16:26-0400 800 c64 Client Call Recorder finished delayed
initialization
2009-05-08 09:16:26-0400 800 c64 AU finished delayed initialization
2009-05-08 09:16:26-0400 800 34c Successfully opened event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{3CF0BE 48-7311-4BFD-98FD-0F534AE013E4}.bin for reading.
2009-05-08 09:16:26-0400 800 34c Failed to upload events with hr = 8024f001.
2009-05-08 09:16:26-0400 800 34c Successfully opened event cache file at
C:\WINDOWS\SoftwareDistribution\EventCache\{3CF0BE 48-7311-4BFD-98FD-0F534AE013E4}.bin for reading.
2009-05-08 09:16:26-0400 800 34c Failed to upload events with hr = 8024f001.
2009-05-08 09:25:28-0400 800 b68 Triggering AU detection through DetectNow
api
2009-05-08 09:25:28-0400 800 c64 AU received event of type: 1
2009-05-08 09:25:28-0400 800 c64 WU client succeeds
CClientCallRecorder::BeginFindUpdatesEx from AutomaticUpdates with call id
{50BD85FC-E2B1-46D0-9811-2083E7D2A8D8}
2009-05-08 09:25:28-0400 800 34c WU client executing call
{50BD85FC-E2B1-46D0-9811-2083E7D2A8D8} of type Search Call
2009-05-08 09:25:49-0400 800 34c SendRequest failed with hr = 80072efd.
Proxy List used: <proxy:8080> Bypass List used : <(null)> Auth Schemes used :
<>
2009-05-08 09:25:49-0400 800 34c WinHttp: SendRequestUsingProxy failed for
<http://wsus01.domain.com/SelfUpdate/wuident.cab>. error 0x80072efd
2009-05-08 09:25:49-0400 800 34c WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
2009-05-08 09:25:49-0400 800 34c WinHttp:
SendRequestToServerForFileInformation failed with 0x80072efd
2009-05-08 09:25:49-0400 800 34c WinHttp: ShouldFileBeDownloaded failed
with 0x80072efd
2009-05-08 09:26:10-0400 800 34c SendRequest failed with hr = 80072efd.
Proxy List used: <proxy:8080> Bypass List used : <(null)> Auth Schemes used :
<>
2009-05-08 09:26:10-0400 800 34c WinHttp: SendRequestUsingProxy failed for
<http://wsus01.domain.com/SelfUpdate/wuident.cab>. error 0x80072efd
2009-05-08 09:26:10-0400 800 34c WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
2009-05-08 09:26:10-0400 800 34c WinHttp:
SendRequestToServerForFileInformation failed with 0x80072efd
2009-05-08 09:26:10-0400 800 34c WinHttp: ShouldFileBeDownloaded failed
with 0x80072efd

Server proxy do not exist anymore...

Where it is getting this settings (not in GPOs, PROXYCFG return nothing, I
searched the registry and files, reset the SoftwareDistribution directory,
reinstall the Automatic Updates client)?

Thanks.

"Harry Johnston [MVP]" wrote:

> > Claude Lachapelle wrote:
>
> >> I would like to know where Automatic Updates are getting this setting
> >> (Proxyservernameort), since I never configured a proxy on this
> >> server, and the one specified do not exist anymore in the the company.
>
> Could you please run the WSUS client diagnostics tool on the affected client and
> post the results?
>
> <http://technet.microsoft.com/en-us/wsus/bb466192.aspx>
>
> http://technet.microsoft.com/en-us/wsus/bb466192.aspx
>
> Also post the results of running proxycfg with no arguments.
>
> Harry.
>
> >>
> >> And due to that, Automatic Updates are failing all communications with
> >> the
> >> WSUS server...
> >>
> >> So, I cleared ALL Connections configuration under Internet Settings in
> >> the
> >> registry, run proxycfg -d, re-installed Automatic Updates with the
> >> special
> >> rundll command, reset the SoftwareDistribution directory many times,
> >> reboot
> >> the server, STILL HAVE THE SAME PROBLEM:
> >>
> >> + Proxy list used = proxy:8080
> >>
> >> Where Automatic Updates are getting this setting?
> >>
> >> Thanks.
> >>
> >> Claude Lachapelle
> >> System Administrator, MCSE
> >
>

"Claude Lachapelle" <> wrote in message
news:05A57433-97E6-48D7-AA97-...

> GetAUSettingsRegistry(false, TEXT("SusServerVersion"), &dwSusVersion) failed with hr=0x80070002
>
> The system cannot find the file specified.


Typical MS incomplete diagnostic? What I would try is running
ProcMon to see if it can help identify *which* file is "specified". ; )


Good luck

Robert Aldwinckle
---

"Robert Aldwinckle" <> wrote in message
news:...
>
> "Claude Lachapelle" <> wrote in
> message news:05A57433-97E6-48D7-AA97-...
>
>> GetAUSettingsRegistry(false, TEXT("SusServerVersion"), &dwSusVersion)
>> failed with hr=0x80070002
>>
>> The system cannot find the file specified.
>
>
> Typical MS incomplete diagnostic? What I would try is running
> ProcMon to see if it can help identify *which* file is "specified". ; )

Robert, no file is specified here... this error is caused by a failure
reading the registry... GetAUSettingsRegistry().

Incidentally, the *only* file retrieved from the WSUS Server by the CDT is
well known -- it's the wuaucomp.cab file in the folder tree appropriate to
the platform where the CDT is being executed.

In this case, the CDT never got to that step, having failed trying to read
the registry.

--
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/pro...awrence.Garvin

"Claude Lachapelle" <> wrote in
message news:05A57433-97E6-48D7-AA97-...
> Here the result of ClientDiag.exe:
>
> 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 5.7.3790.3959 . . . . . . . . . . . PASS

First thing to note is that this client is not running the current version
of the WUA.

What that also tells me is that this client has *NEVER* been updated.

So, let's back up a second and talk about exactly when/how this client was
built.

And, on the off chance that you're going to tell me what I think might have
happened...
I'll offer this post as a possible resolution:

http://support.microsoft.com/kb/956708 (Note: while the error codes do not
match, if the description in the Symptoms section matches reality -- e.g.
this is a fresh machine installed to XP SP2 and immediately upgraded to XP
SP3 -- then this is the fix you need.)



--
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/pro...awrence.Garvin

Claude,

I've noticed that the error messages in the log are coming from a different
process than the Automatic Updates service process. I don't think the AU
service normally spawns a subprocess in this situation, so I suspect some other
program is involved; if so, it'll be that program that is providing the proxy
information, and those errors probably isn't related to the issue with
contacting the WSUS server.

If I'm right, the part of the log you've posted doesn't contain the information
we'd need to diagnose the WSUS server issue. However, Lawrence has already
pointed out the most common cause, so do try his suggestion and see if it helps.

If it doesn't, answers to these questions may help us:

What version of WSUS are you running? Does the faulty client appear in the WSUS
server, and if so, what is the last report date? How long has the current WSUS
server been running and what did you use before that? How long since the faulty
client was installed?

Also, a better log fragment would help:

1) Wait until the log hasn't had any new entries for twenty minutes or so. (If
this doesn't happen, that's an interesting fact in itself, so let us know!)

2) Run wuauclt /detectnow

3) Repeat step 1

4) Post the contents of the log starting from step 2 and going all the way to
the end.

Harry.

Claude Lachapelle wrote:

> Here the result of ClientDiag.exe:
>
> 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 5.7.3790.3959 . . . . . . . . . . . PASS
> This version is WSUS 2.0
>
> Checking AU Settings
> AU Option is 3 : Notify Prior to 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://wsus01.domain.com
> WUStatusServer = http://wsus01.domain.com
> UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
>
> GetAUSettingsRegistry(false, TEXT("SusServerVersion"), &dwSusVersion) failed
> wit
> h hr=0x80070002
>
> The system cannot find the file specified.
>
> Here what we got in WindowsUpdate.log:
>
> 2009-05-08 09:15:40-0400 800 c64 Service status is now SERVICE_RUNNING
> 2009-05-08 09:16:25-0400 800 c64 start delayed initialization of WU client
> 2009-05-08 09:16:25-0400 800 c64 BatchFlushAge = 16290.
> 2009-05-08 09:16:25-0400 800 c64 SamplingValue = 203, sampling required = Yes
> 2009-05-08 09:16:25-0400 800 c64 Reopened existing event cache file at
> C:\WINDOWS\SoftwareDistribution\EventCache\{4FAA8C FD-6315-4049-AF0A-BC5802CDFC22}.bin for writing.
> 2009-05-08 09:16:25-0400 800 c64 Successfully initialized event uploader
> for server 3da21691-e39d-4da6-8a4b-b43877bcb1b7.
> 2009-05-08 09:16:26-0400 800 c64 Client Call Recorder finished delayed
> initialization
> 2009-05-08 09:16:26-0400 800 c64 AU finished delayed initialization
> 2009-05-08 09:16:26-0400 800 34c Successfully opened event cache file at
> C:\WINDOWS\SoftwareDistribution\EventCache\{3CF0BE 48-7311-4BFD-98FD-0F534AE013E4}.bin for reading.
> 2009-05-08 09:16:26-0400 800 34c Failed to upload events with hr = 8024f001.
> 2009-05-08 09:16:26-0400 800 34c Successfully opened event cache file at
> C:\WINDOWS\SoftwareDistribution\EventCache\{3CF0BE 48-7311-4BFD-98FD-0F534AE013E4}.bin for reading.
> 2009-05-08 09:16:26-0400 800 34c Failed to upload events with hr = 8024f001.
> 2009-05-08 09:25:28-0400 800 b68 Triggering AU detection through DetectNow
> api
> 2009-05-08 09:25:28-0400 800 c64 AU received event of type: 1
> 2009-05-08 09:25:28-0400 800 c64 WU client succeeds
> CClientCallRecorder::BeginFindUpdatesEx from AutomaticUpdates with call id
> {50BD85FC-E2B1-46D0-9811-2083E7D2A8D8}
> 2009-05-08 09:25:28-0400 800 34c WU client executing call
> {50BD85FC-E2B1-46D0-9811-2083E7D2A8D8} of type Search Call
> 2009-05-08 09:25:49-0400 800 34c SendRequest failed with hr = 80072efd.
> Proxy List used: <proxy:8080> Bypass List used : <(null)> Auth Schemes used :
> <>
> 2009-05-08 09:25:49-0400 800 34c WinHttp: SendRequestUsingProxy failed for
> <http://wsus01.domain.com/SelfUpdate/wuident.cab>. error 0x80072efd
> 2009-05-08 09:25:49-0400 800 34c WinHttp:
> SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
> 2009-05-08 09:25:49-0400 800 34c WinHttp:
> SendRequestToServerForFileInformation failed with 0x80072efd
> 2009-05-08 09:25:49-0400 800 34c WinHttp: ShouldFileBeDownloaded failed
> with 0x80072efd
> 2009-05-08 09:26:10-0400 800 34c SendRequest failed with hr = 80072efd.
> Proxy List used: <proxy:8080> Bypass List used : <(null)> Auth Schemes used :
> <>
> 2009-05-08 09:26:10-0400 800 34c WinHttp: SendRequestUsingProxy failed for
> <http://wsus01.domain.com/SelfUpdate/wuident.cab>. error 0x80072efd
> 2009-05-08 09:26:10-0400 800 34c WinHttp:
> SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
> 2009-05-08 09:26:10-0400 800 34c WinHttp:
> SendRequestToServerForFileInformation failed with 0x80072efd
> 2009-05-08 09:26:10-0400 800 34c WinHttp: ShouldFileBeDownloaded failed
> with 0x80072efd
>
> Server proxy do not exist anymore...
>
> Where it is getting this settings (not in GPOs, PROXYCFG return nothing, I
> searched the registry and files, reset the SoftwareDistribution directory,
> reinstall the Automatic Updates client)?
>
> Thanks.
>
> "Harry Johnston [MVP]" wrote:
>
>>> Claude Lachapelle wrote:
>>>> I would like to know where Automatic Updates are getting this setting
>>>> (Proxyservernameort), since I never configured a proxy on this
>>>> server, and the one specified do not exist anymore in the the company.
>> Could you please run the WSUS client diagnostics tool on the affected client and
>> post the results?
>>
>> <http://technet.microsoft.com/en-us/wsus/bb466192.aspx>
>>
>> http://technet.microsoft.com/en-us/wsus/bb466192.aspx
>>
>> Also post the results of running proxycfg with no arguments.
>>
>> Harry.
>>
>>>> And due to that, Automatic Updates are failing all communications with
>>>> the
>>>> WSUS server...
>>>>
>>>> So, I cleared ALL Connections configuration under Internet Settings in
>>>> the
>>>> registry, run proxycfg -d, re-installed Automatic Updates with the
>>>> special
>>>> rundll command, reset the SoftwareDistribution directory many times,
>>>> reboot
>>>> the server, STILL HAVE THE SAME PROBLEM:
>>>>
>>>> + Proxy list used = proxy:8080
>>>>
>>>> Where Automatic Updates are getting this setting?
>>>>
>>>> Thanks.
>>>>
>>>> Claude Lachapelle
>>>> System Administrator, MCSE

I went to the Windows Update site, and the Automatic Updates client have been
update (server rebooted after). So I assume we got the latest version...

The problem is on the WSUS server itself, and never the computer appear in
the WSUS console, it seem that the proxy settings (proxy:8080) block the
communication to itself!

This server is brand new (VMWare virtual machine), 1 month old only, it is
running Windows Server 2003 Enterprise 64-bit SP2, and all the Windows
updates have been applied. The Automatic Updates client never function
properly... the reason why I'm actually working on it.

Here the content of the WindowsUpdate.log just after the Automatic Updates
client have been updated (Microsoft Windows Update web site) and the command
wuauclt /detectnow have been issued:

2009-05-12 11:00:35:562 784 778 Misc =========== Logging initialized
(build: 7.2.6001.788, tz: -0400) ===========
2009-05-12 11:00:35:562 784 778 Misc = Process:
C:\WINDOWS\System32\svchost.exe
2009-05-12 11:00:35:562 784 778 Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2009-05-12 11:00:35:562 784 778 Service *************
2009-05-12 11:00:35:812 784 778 Service ** START ** Service: Service startup
2009-05-12 11:00:35:812 784 778 Service *********
2009-05-12 11:00:36:203 784 778 Misc Registering binary:
C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wups.dll"
2009-05-12 11:00:36:625 784 778 Misc Registering binary:
C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wups2.dll"
2009-05-12 11:00:37:125 784 778 Misc Registering binary:
C:\WINDOWS\SysWOW64\regsvr32.exe /s "C:\WINDOWS\SysWow64\wuapi.dll"
2009-05-12 11:00:37:968 784 778 Misc Registering binary:
C:\WINDOWS\SysWOW64\regsvr32.exe /s "C:\WINDOWS\SysWow64\wups.dll"
2009-05-12 11:00:38:375 784 778 Misc Registering binary:
C:\WINDOWS\SysWOW64\regsvr32.exe /s "C:\WINDOWS\SysWow64\wups2.dll"
2009-05-12 11:00:39:171 784 778 Agent * WU client version 7.2.6001.788
2009-05-12 11:00:39:171 784 778 Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2009-05-12 11:00:39:171 784 778 Agent * Access type: No proxy
2009-05-12 11:00:39:203 784 778 Agent * Network state: Connected
2009-05-12 11:01:24:750 784 778 Agent *********** Agent: Initializing
Windows Update Agent ***********
2009-05-12 11:01:24:750 784 778 Agent *********** Agent: Initializing
global settings cache ***********
2009-05-12 11:01:24:750 784 778 Agent * WSUS server:
http://wsus01.domain.com
2009-05-12 11:01:24:750 784 778 Agent * WSUS status server:
http://wsus01.domain.com
2009-05-12 11:01:24:750 784 778 Agent * Target group: (Unassigned
Computers)
2009-05-12 11:01:24:750 784 778 Agent * Windows Update access disabled: No
2009-05-12 11:01:25:671 784 778 DnldMgr Download manager restoring 0
downloads
2009-05-12 11:01:25:671 784 778 AU ########### AU: Initializing Automatic
Updates ###########
2009-05-12 11:01:25:671 784 778 AU # WSUS server: http://wsus01.domain.com
2009-05-12 11:01:25:671 784 778 AU # Detection frequency: 22
2009-05-12 11:01:25:671 784 778 AU # Approval type: Pre-install notify
(Policy)
2009-05-12 11:01:25:671 784 778 AU # Auto-install minor updates: No (User
preference)
2009-05-12 11:01:25:718 784 778 Report *********** Report: Initializing
static reporting data ***********
2009-05-12 11:01:25:718 784 778 Report * OS Version = 5.2.3790.2.0.196882
2009-05-12 11:01:26:703 784 778 Report * Computer Brand = VMware, Inc.
2009-05-12 11:01:26:703 784 778 Report * Computer Model = VMware Virtual
Platform
2009-05-12 11:01:26:703 784 778 Report * Bios Revision = 6.00
2009-05-12 11:01:26:703 784 778 Report * Bios Name = Default System BIOS
2009-05-12 11:01:26:703 784 778 Report * Bios Release Date =
2007-09-06T00:00:00
2009-05-12 11:01:26:703 784 778 Report * Locale ID = 1033
2009-05-12 11:01:27:296 784 778 AU AU finished delayed initialization
2009-05-12 11:01:27:296 784 778 AU #############
2009-05-12 11:01:27:296 784 778 AU ## START ## AU: Search for updates
2009-05-12 11:01:27:296 784 778 AU #########
2009-05-12 11:01:27:343 784 778 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {91F41888-93C6-4199-B270-BF1EC31E884D}]
2009-05-12 11:01:28:343 784 1fc Agent *************
2009-05-12 11:01:28:343 784 1fc Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-05-12 11:01:28:343 784 1fc Agent *********
2009-05-12 11:01:28:343 784 1fc Agent * Online = No; Ignore download
priority = No
2009-05-12 11:01:28:343 784 1fc Agent * Criteria = "IsHidden=0 and
IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or
IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and
IsAssigned=1 or IsHidden=0 and IsInstalled=1 and
DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or
IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and
IsAssigned=1 and RebootRequired=1"
2009-05-12 11:01:28:343 784 1fc Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-05-12 11:01:28:343 784 1fc Agent * Search Scope = {Machine}
2009-05-12 11:01:28:546 784 1fc EEHndlr WARNING: Failed to populate
ServiceStartup entries in Cache: error 0x80070002

2009-05-12 11:01:28:562 784 1fc EEHndlr WARNING: Failed to populate
ServiceStartup entries in Cache: error 0x80070002

2009-05-12 11:01:28:593 784 1fc Agent * Found 0 updates and 0 categories
in search; evaluated appl. rules of 0 out of 0 deployed entities
2009-05-12 11:01:28:593 784 1fc Agent *********
2009-05-12 11:01:28:593 784 1fc Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-05-12 11:01:28:593 784 1fc Agent *************
2009-05-12 11:01:28:593 784 8b4 AU >>## RESUMED ## AU: Search for updates
[CallId = {91F41888-93C6-4199-B270-BF1EC31E884D}]
2009-05-12 11:01:28:593 784 8b4 AU # 0 updates detected
2009-05-12 11:01:28:593 784 8b4 AU #########
2009-05-12 11:01:28:593 784 8b4 AU ## END ## AU: Search for updates
[CallId = {91F41888-93C6-4199-B270-BF1EC31E884D}]
2009-05-12 11:01:28:593 784 8b4 AU #############
2009-05-12 11:01:32:281 784 1fc Report REPORT EVENT:
{BDF63CFB-C4F2-44F7-8298-0402DAD976B3} 2009-05-12
11:01:25:718-0400 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
2009-05-12 11:16:32:250 784 1fc Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <proxy:8080> Bypass List used : <(null)> Auth
Schemes used : <>
2009-05-12 11:16:32:250 784 1fc PT + Last proxy send request failed with
hr = 0x80072EFD, HTTP status code = 0
2009-05-12 11:16:32:250 784 1fc PT + Caller provided proxy = No
2009-05-12 11:16:32:250 784 1fc PT + Proxy list used = proxy:8080
2009-05-12 11:16:32:250 784 1fc PT + Bypass list used = <NULL>
2009-05-12 11:16:32:250 784 1fc PT + Caller provided credentials = No
2009-05-12 11:16:32:250 784 1fc PT + Impersonate flags = 0
2009-05-12 11:16:32:250 784 1fc PT + Possible authorization schemes used =
2009-05-12 11:16:32:250 784 1fc PT WARNING: GetConfig failure, error =
0x80072EFD, soap client error = 5, soap error code = 0, HTTP status code = 200
2009-05-12 11:16:32:250 784 1fc PT WARNING: PTError: 0x80072efd
2009-05-12 11:16:32:250 784 1fc PT WARNING: GetConfig_WithRecovery failed:
0x80072efd
2009-05-12 11:16:32:250 784 1fc PT WARNING: RefreshConfig failed: 0x80072efd
2009-05-12 11:16:32:250 784 1fc PT WARNING: RefreshPTState failed: 0x80072efd
2009-05-12 11:16:32:250 784 1fc PT WARNING: PTError: 0x80072efd
2009-05-12 11:16:32:250 784 1fc Report WARNING: Reporter failed to upload
events with hr = 80072efd.
2009-05-12 11:37:44:095 784 354 AU Triggering AU detection through
DetectNow API
2009-05-12 11:37:44:111 784 354 AU Triggering Online detection
(non-interactive)
2009-05-12 11:37:44:111 784 778 AU #############
2009-05-12 11:37:44:111 784 778 AU ## START ## AU: Search for updates
2009-05-12 11:37:44:111 784 778 AU #########
2009-05-12 11:37:44:111 784 778 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {C82651FD-2A43-43B9-B8E8-C2DE12AAFE09}]
2009-05-12 11:37:44:111 784 690 Agent *************
2009-05-12 11:37:44:111 784 690 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2009-05-12 11:37:44:111 784 690 Agent *********
2009-05-12 11:37:44:111 784 690 Agent * Online = Yes; Ignore download
priority = No
2009-05-12 11:37:44:111 784 690 Agent * Criteria = "IsHidden=0 and
IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or
IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and
IsAssigned=1 or IsHidden=0 and IsInstalled=1 and
DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or
IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and
IsAssigned=1 and RebootRequired=1"
2009-05-12 11:37:44:111 784 690 Agent * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2009-05-12 11:37:44:111 784 690 Agent * Search Scope = {Machine}
2009-05-12 11:38:05:424 784 690 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <proxy:8080> Bypass List used : <(null)> Auth
Schemes used : <>
2009-05-12 11:38:05:424 784 690 Misc WARNING: WinHttp:
SendRequestUsingProxy failed for
<http://wsus01.domain.com/selfupdate/wuident.cab>. error 0x80072efd
2009-05-12 11:38:05:424 784 690 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
2009-05-12 11:38:05:424 784 690 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80072efd
2009-05-12 11:38:05:424 784 690 Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80072efd
2009-05-12 11:38:26:424 784 690 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <proxy:8080> Bypass List used : <(null)> Auth
Schemes used : <>
2009-05-12 11:38:26:424 784 690 Misc WARNING: WinHttp:
SendRequestUsingProxy failed for
<http://wsus01.domain.com/selfupdate/wuident.cab>. error 0x80072efd
2009-05-12 11:38:26:424 784 690 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
2009-05-12 11:38:26:424 784 690 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80072efd
2009-05-12 11:38:26:424 784 690 Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80072efd
2009-05-12 11:38:47:424 784 690 Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <proxy:8080> Bypass List used : <(null)> Auth
Schemes used : <>
2009-05-12 11:38:47:424 784 690 Misc WARNING: WinHttp:
SendRequestUsingProxy failed for
<http://wsus01.domain.com/selfupdate/wuident.cab>. error 0x80072efd
2009-05-12 11:38:47:424 784 690 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
2009-05-12 11:38:47:424 784 690 Misc WARNING: WinHttp:
SendRequestToServerForFileInformation failed with 0x80072efd
2009-05-12 11:38:47:424 784 690 Misc WARNING: WinHttp:
ShouldFileBeDownloaded failed with 0x80072efd


"Harry Johnston [MVP]" wrote:

> Claude,
>
> I've noticed that the error messages in the log are coming from a different
> process than the Automatic Updates service process. I don't think the AU
> service normally spawns a subprocess in this situation, so I suspect some other
> program is involved; if so, it'll be that program that is providing the proxy
> information, and those errors probably isn't related to the issue with
> contacting the WSUS server.
>
> If I'm right, the part of the log you've posted doesn't contain the information
> we'd need to diagnose the WSUS server issue. However, Lawrence has already
> pointed out the most common cause, so do try his suggestion and see if it helps.
>
> If it doesn't, answers to these questions may help us:
>
> What version of WSUS are you running? Does the faulty client appear in the WSUS
> server, and if so, what is the last report date? How long has the current WSUS
> server been running and what did you use before that? How long since the faulty
> client was installed?
>
> Also, a better log fragment would help:
>
> 1) Wait until the log hasn't had any new entries for twenty minutes or so. (If
> this doesn't happen, that's an interesting fact in itself, so let us know!)
>
> 2) Run wuauclt /detectnow
>
> 3) Repeat step 1
>
> 4) Post the contents of the log starting from step 2 and going all the way to
> the end.
>
> Harry.
>
> Claude Lachapelle wrote:
>
> > Here the result of ClientDiag.exe:
> >
> > 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 5.7.3790.3959 . . . . . . . . . . . PASS
> > This version is WSUS 2.0
> >
> > Checking AU Settings
> > AU Option is 3 : Notify Prior to 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://wsus01.domain.com
> > WUStatusServer = http://wsus01.domain.com
> > UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
> >
> > GetAUSettingsRegistry(false, TEXT("SusServerVersion"), &dwSusVersion) failed
> > wit
> > h hr=0x80070002
> >
> > The system cannot find the file specified.
> >
> > Here what we got in WindowsUpdate.log:
> >
> > 2009-05-08 09:15:40-0400 800 c64 Service status is now SERVICE_RUNNING
> > 2009-05-08 09:16:25-0400 800 c64 start delayed initialization of WU client
> > 2009-05-08 09:16:25-0400 800 c64 BatchFlushAge = 16290.
> > 2009-05-08 09:16:25-0400 800 c64 SamplingValue = 203, sampling required = Yes
> > 2009-05-08 09:16:25-0400 800 c64 Reopened existing event cache file at
> > C:\WINDOWS\SoftwareDistribution\EventCache\{4FAA8C FD-6315-4049-AF0A-BC5802CDFC22}.bin for writing.
> > 2009-05-08 09:16:25-0400 800 c64 Successfully initialized event uploader
> > for server 3da21691-e39d-4da6-8a4b-b43877bcb1b7.
> > 2009-05-08 09:16:26-0400 800 c64 Client Call Recorder finished delayed
> > initialization
> > 2009-05-08 09:16:26-0400 800 c64 AU finished delayed initialization
> > 2009-05-08 09:16:26-0400 800 34c Successfully opened event cache file at
> > C:\WINDOWS\SoftwareDistribution\EventCache\{3CF0BE 48-7311-4BFD-98FD-0F534AE013E4}.bin for reading.
> > 2009-05-08 09:16:26-0400 800 34c Failed to upload events with hr = 8024f001.
> > 2009-05-08 09:16:26-0400 800 34c Successfully opened event cache file at
> > C:\WINDOWS\SoftwareDistribution\EventCache\{3CF0BE 48-7311-4BFD-98FD-0F534AE013E4}.bin for reading.
> > 2009-05-08 09:16:26-0400 800 34c Failed to upload events with hr = 8024f001.
> > 2009-05-08 09:25:28-0400 800 b68 Triggering AU detection through DetectNow
> > api
> > 2009-05-08 09:25:28-0400 800 c64 AU received event of type: 1
> > 2009-05-08 09:25:28-0400 800 c64 WU client succeeds
> > CClientCallRecorder::BeginFindUpdatesEx from AutomaticUpdates with call id
> > {50BD85FC-E2B1-46D0-9811-2083E7D2A8D8}
> > 2009-05-08 09:25:28-0400 800 34c WU client executing call
> > {50BD85FC-E2B1-46D0-9811-2083E7D2A8D8} of type Search Call
> > 2009-05-08 09:25:49-0400 800 34c SendRequest failed with hr = 80072efd.
> > Proxy List used: <proxy:8080> Bypass List used : <(null)> Auth Schemes used :
> > <>
> > 2009-05-08 09:25:49-0400 800 34c WinHttp: SendRequestUsingProxy failed for
> > <http://wsus01.domain.com/SelfUpdate/wuident.cab>. error 0x80072efd
> > 2009-05-08 09:25:49-0400 800 34c WinHttp:
> > SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
> > 2009-05-08 09:25:49-0400 800 34c WinHttp:
> > SendRequestToServerForFileInformation failed with 0x80072efd
> > 2009-05-08 09:25:49-0400 800 34c WinHttp: ShouldFileBeDownloaded failed
> > with 0x80072efd
> > 2009-05-08 09:26:10-0400 800 34c SendRequest failed with hr = 80072efd.
> > Proxy List used: <proxy:8080> Bypass List used : <(null)> Auth Schemes used :
> > <>
> > 2009-05-08 09:26:10-0400 800 34c WinHttp: SendRequestUsingProxy failed for
> > <http://wsus01.domain.com/SelfUpdate/wuident.cab>. error 0x80072efd
> > 2009-05-08 09:26:10-0400 800 34c WinHttp:
> > SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efd
> > 2009-05-08 09:26:10-0400 800 34c WinHttp:
> > SendRequestToServerForFileInformation failed with 0x80072efd
> > 2009-05-08 09:26:10-0400 800 34c WinHttp: ShouldFileBeDownloaded failed
> > with 0x80072efd
> >
> > Server proxy do not exist anymore...
> >
> > Where it is getting this settings (not in GPOs, PROXYCFG return nothing, I
> > searched the registry and files, reset the SoftwareDistribution directory,
> > reinstall the Automatic Updates client)?
> >
> > Thanks.
> >
> > "Harry Johnston [MVP]" wrote:
> >
> >>> Claude Lachapelle wrote:
> >>>> I would like to know where Automatic Updates are getting this setting
> >>>> (Proxyservernameort), since I never configured a proxy on this
> >>>> server, and the one specified do not exist anymore in the the company.
> >> Could you please run the WSUS client diagnostics tool on the affected client and
> >> post the results?
> >>
> >> <http://technet.microsoft.com/en-us/wsus/bb466192.aspx>
> >>
> >> http://technet.microsoft.com/en-us/wsus/bb466192.aspx
> >>
> >> Also post the results of running proxycfg with no arguments.
> >>
> >> Harry.
> >>
> >>>> And due to that, Automatic Updates are failing all communications with
> >>>> the
> >>>> WSUS server...
> >>>>
> >>>> So, I cleared ALL Connections configuration under Internet Settings in
> >>>> the
> >>>> registry, run proxycfg -d, re-installed Automatic Updates with the
> >>>> special
> >>>> rundll command, reset the SoftwareDistribution directory many times,
> >>>> reboot
> >>>> the server, STILL HAVE THE SAME PROBLEM:
> >>>>
> >>>> + Proxy list used = proxy:8080
> >>>>
> >>>> Where Automatic Updates are getting this setting?
> >>>>
> >>>> Thanks.
> >>>>
> >>>> Claude Lachapelle
> >>>> System Administrator, MCSE
>