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

Hi!

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

[[ 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... date_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" <ClaudeLachapelle@discussions.microsoft.com> wrote in message
news:05A57433-97E6-48D7-AA97-0B1EA59A3B5F@microsoft.com...

> 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" <robald@techemail.com> wrote in message
news:Okd3NNC0JHA.1716@TK2MSFTNGP03.phx.gbl...
>
> "Claude Lachapelle" <ClaudeLachapelle@discussions.microsoft.com> wrote in
> message news:05A57433-97E6-48D7-AA97-0B1EA59A3B5F@microsoft.com...
>
>> 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" <ClaudeLachapelle@discussions.microsoft.com> wrote in
message news:05A57433-97E6-48D7-AA97-0B1EA59A3B5F@microsoft.com...
> 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