Client can not connect to WSUS server (error 0x80072EFD)

[Dandando]

We found recently over 70% client can not connect to WSUS server with error
0x80072EFD. But newly installed pc has no probleam to connect wsus and get
patch. anyone can help? below is the log from on client pc.

Log:
2008-04-21 19:41:24:484 784 5a0 Report * Locale ID = 2052
2008-04-21 19:41:27:093 784 c9c Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <10.1.1.1:8887> Bypass List used : <<local>> Auth
Schemes used : <>
2008-04-21 19:41:27:093 784 c9c PT + Last proxy send request failed with
hr = 0x80072EFD, HTTP status code = 0
2008-04-21 19:41:27:093 784 c9c PT + Caller provided proxy = No
2008-04-21 19:41:27:093 784 c9c PT + Proxy list used = 10.1.1.1:8887
2008-04-21 19:41:27:093 784 c9c PT + Bypass list used = <local>
2008-04-21 19:41:27:093 784 c9c PT + Caller provided credentials = No
2008-04-21 19:41:27:093 784 c9c PT + Impersonate flags = 0
2008-04-21 19:41:27:093 784 c9c PT + Possible authorization schemes used
=
2008-04-21 19:41:27:093 784 c9c PT WARNING: GetConfig failure, error =
0x80072EFD, soap client error = 5, soap error code = 0, HTTP status code =
200
2008-04-21 19:41:27:093 784 c9c PT WARNING: PTError: 0x80072efd
2008-04-21 19:41:27:093 784 c9c PT WARNING: GetConfig_WithRecovery failed:
0x80072efd
2008-04-21 19:41:27:093 784 c9c PT WARNING: RefreshConfig failed:
0x80072efd
2008-04-21 19:41:27:093 784 c9c PT WARNING: RefreshPTState failed:
0x80072efd
2008-04-21 19:41:27:093 784 c9c PT WARNING: PTError: 0x80072efd
2008-04-21 19:41:27:093 784 c9c Report WARNING: Reporter failed to upload
events with hr = 80072efd.
2008-04-21 19:41:29:281 784 c9c Misc WARNING: SendRequest failed with hr =
80072efd. Proxy List used: <10.86.130.130:8887> Bypass List used : <<local>>
Auth Schemes used : <>
2008-04-21 19:41:29:281 784 c9c PT + Last proxy send request failed with
hr = 0x80072EFD, HTTP status code = 0
2008-04-21 19:41:29:281 784 c9c PT + Caller provided proxy = No
2008-04-21 19:41:29:281 784 c9c PT + Proxy list used = 10.1.1.1:8887
2008-04-21 19:41:29:281 784 c9c PT + Bypass list used = <local>
2008-04-21 19:41:29:281 784 c9c PT + Caller provided credentials = No
2008-04-21 19:41:29:281 784 c9c PT + Impersonate flags = 0
2008-04-21 19:41:29:281 784 c9c PT + Possible authorization schemes used
=
2008-04-21 19:41:29:281 784 c9c PT WARNING: GetConfig failure, error =
0x80072EFD, soap client error = 5, soap error code = 0, HTTP status code =
200
2008-04-21 19:41:29:281 784 c9c PT WARNING: PTError: 0x80072efd
2008-04-21 19:41:29:281 784 c9c PT WARNING: GetConfig_WithRecovery failed:
0x80072efd
2008-04-21 19:41:29:281 784 c9c PT WARNING: RefreshConfig failed:
0x80072efd
2008-04-21 19:41:29:281 784 c9c PT WARNING: RefreshPTState failed:
0x80072efd
2008-04-21 19:41:29:281 784 c9c PT WARNING: PTError: 0x80072efd
2008-04-21 19:41:29:281 784 c9c Report WARNING: Reporter failed to upload
events with hr = 80072efd.

[Dandando]

And some client with error 0x8024400e as below

2008-04-21 19:55:54:149 784 c9c PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2008-04-21 19:55:54:149 784 c9c PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://10.1.1.32/ClientWebService/client.asmx
2008-04-21 19:55:54:653 784 c9c PT WARNING: Cached cookie has expired or
new PID is available
2008-04-21 19:55:54:653 784 c9c PT Initializing simple targeting cookie,
clientId = 86412d27-3723-41ee-bc9f-d8652aa20c57, target group =
"Workstations", DNS name = pc1.test.com
2008-04-21 19:55:54:653 784 c9c PT Server URL =
http://10.1.1.32/SimpleAuthWebService/SimpleAuth.asmx
2008-04-21 19:55:55:141 784 c9c PT WARNING: GetAuthorizationCookie failure,
error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP
status code = 200
2008-04-21 19:55:55:141 784 c9c PT WARNING: SOAP Fault: 0x000190
2008-04-21 19:55:55:141 784 c9c PT WARNING: faultstring:Fault occurred
2008-04-21 19:55:55:141 784 c9c PT WARNING:
ErrorCode:InternalServerError(5)
2008-04-21 19:55:55:141 784 c9c PT WARNING: Message:(null)
2008-04-21 19:55:55:141 784 c9c PT WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/Server/SimpleAuthWebService/GetAuthorizationCookie"
2008-04-21 19:55:55:141 784 c9c PT WARNING:
ID:721c83cd-90ed-44ae-a490-5d9d8161a2c9
2008-04-21 19:55:55:141 784 c9c PT WARNING: Failed to initialize Simple
Targeting Cookie: 0x8024400e
2008-04-21 19:55:55:141 784 c9c PT WARNING: PopulateAuthCookies failed:
0x8024400e
2008-04-21 19:55:55:141 784 c9c PT WARNING: RefreshCookie failed:
0x8024400e
2008-04-21 19:55:55:141 784 c9c PT WARNING: RefreshPTState failed:
0x8024400e
2008-04-21 19:55:55:141 784 c9c PT WARNING: Sync of Updates: 0x8024400e
2008-04-21 19:55:55:141 784 c9c PT WARNING: SyncServerUpdatesInternal
failed: 0x8024400e
2008-04-21 19:55:55:141 784 c9c Agent * WARNING: Failed to synchronize,
error = 0x8024400E
2008-04-21 19:55:55:141 784 c9c Agent * WARNING: Exit code = 0x8024400E
2008-04-21 19:55:55:141 784 c9c Agent *********
2008-04-21 19:55:55:141 784 c9c Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2008-04-21 19:55:55:141 784 c9c Agent *************
2008-04-21 19:55:55:141 784 c9c Agent WARNING: WU client failed Searching
for update with error 0x8024400e
2008-04-21 19:55:55:141 784 9e8 AU >>## RESUMED ## AU: Search for updates
[CallId = {F8AE9CA8-0699-41E7-9987-56EDD12ECCF4}]
2008-04-21 19:55:55:141 784 9e8 AU # WARNING: Search callback failed,
result = 0x8024400E
2008-04-21 19:55:55:141 784 9e8 AU # WARNING: Failed to find updates with
error code 8024400E
2008-04-21 19:55:55:141 784 9e8 AU #########
2008-04-21 19:55:55:141 784 9e8 AU ## END ## AU: Search for updates
[CallId = {F8AE9CA8-0699-41E7-9987-56EDD12ECCF4}]
2008-04-21 19:55:55:141 784 9e8 AU #############
2008-04-21 19:55:55:141 784 9e8 AU AU setting next detection timeout to
2008-04-21 15:25:01
2008-04-21 19:55:55:141 784 9e8 AU Setting AU scheduled install time to
2008-04-22 05:00:00
2008-04-21 19:56:00:176 784 c9c Report REPORT EVENT:
{A9B4C955-1999-4ECF-A269-0CAA25332549} 2008-04-21 19:55:55:141+0800 1 148
101 {00000000-0000-0000-0000-000000000000} 0 8024400e AutomaticUpdates
Failure Software Synchronization Windows Update Client failed to detect with
error 0x8024400e.

"Dandando" <danje...@msn.com> wrote in message
news:ey0HfV6o...@TK2MSFTNGP02.phx.gbl...

[tucum]

I have the same problem here
In other forums i've found a solution that works for XP and that would
probably work in vista
But its not the best solution because you'll loose the update history
Here is the link in case you want to try:
http://groups.google.com/group/microsoft.public.windowsupdate/browse_thread/thread/8ab601f19d242bd6/d83095a2fce372c5
I didn't try it. I'll wait for someone else's answer

--
André Matos

[Lawrence Garvin [MVP]]

"tucum" <tu...@discussions.microsoft.com> wrote in message
news:FC3409E4-7610-497A...@microsoft.com...

> I have the same problem here
> In other forums i've found a solution that works for XP and that would
> probably work in vista
> But its not the best solution because you'll loose the update history
> Here is the link in case you want to try:
> http://groups.google.com/group/microsoft.public.windowsupdate/browse_thread/thread/8ab601f19d242bd6/d83095a2fce372c5
> I didn't try it. I'll wait for someone else's answer

>> 2008-04-21 19:55:54:653 784 c9c PT Initializing simple targeting cookie,

>> clientId = 86412d27-3723-41ee-bc9f-d8652aa20c57,
>> target group = "Workstations",
>> DNS name = pc1.test.com

The most likely issue here is the use of quotation marks around the target
group name in the policy configuration.

Remove the quotation marks, and try again.

>> "Dandando" <danje...@msn.com> wrote in message
>> news:ey0HfV6o...@TK2MSFTNGP02.phx.gbl...
>> > We found recently over 70% client can not connect to WSUS server with
>> > error 0x80072EFD. But newly installed pc has no probleam to connect
>> > wsus
>> > and get patch. anyone can help? below is the log from on client pc.

>> > 2008-04-21 19:41:27:093 784 c9c Misc WARNING: SendRequest failed with

>> > hr
>> > = 80072efd. Proxy List used: <10.1.1.1:8887> Bypass List used :
>> > <<local>>
>> > Auth Schemes used : <>

In this instance, it's likely either a misconfigured proxy server, a
misconfigured proxy client, or an incompatible proxy scheme, given that the
proxy traffic is being routed through port 8887.

--
Lawrence Garvin, M.S., MCITP, MCBMSP, MCTS(x4), MCP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

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

[Dandando]

Thks all

My pobleam is cause by the quotation marks, i remove the quotation marks
in client side targeting in GPO and pc come back.

"Lawrence Garvin [MVP]" <ons...@postalias.news> wrote in message
news:A810238F-393A-495E...@microsoft.com...

[tucum]

Hello
I looked into the Windows Update log but i didn't find any quotation marks
In the target group i have only a blank space, i don't know if this is ok...
Below, a copy of part of the log in my computer:

2008-05-05 11:10:40:379 1084 10f0 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2008-05-05 11:10:40:379 1084 10f0 PT + ServiceId =

{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =

http://numsrvcom01/ClientWebService/client.asmx
2008-05-05 11:10:41:000 1084 10f0 PT WARNING: Cached cookie has expired or
new PID is available
2008-05-05 11:10:41:000 1084 10f0 PT Initializing simple targeting cookie,
clientId = 8857e030-02d6-4244-93b0-1e1a140a23c2, target group = , DNS name =
nc-desenv01.numericon.com.br
2008-05-05 11:10:41:000 1084 10f0 PT Server URL =
http://numsrvcom01/SimpleAuthWebService/SimpleAuth.asmx
2008-05-05 11:10:41:026 1084 10f0 PT WARNING: GetAuthorizationCookie

failure, error = 0x8024400E, soap client error = 7, soap error code = 400,
HTTP status code = 200

2008-05-05 11:10:41:027 1084 10f0 PT WARNING: SOAP Fault: 0x000190
2008-05-05 11:10:41:027 1084 10f0 PT WARNING: faultstring:Fault occurred
2008-05-05 11:10:41:027 1084 10f0 PT WARNING:
ErrorCode:InternalServerError(5)
2008-05-05 11:10:41:027 1084 10f0 PT WARNING: Message:(null)
2008-05-05 11:10:41:027 1084 10f0 PT WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/Server/SimpleAuthWebService/GetAuthorizationCookie"
2008-05-05 11:10:41:027 1084 10f0 PT WARNING:
ID:4da8707c-ad39-4c50-ac31-a77e4205e56c
2008-05-05 11:10:41:027 1084 10f0 PT WARNING: Failed to initialize Simple
Targeting Cookie: 0x8024400e
2008-05-05 11:10:41:027 1084 10f0 PT WARNING: PopulateAuthCookies failed:
0x8024400e
2008-05-05 11:10:41:027 1084 10f0 PT WARNING: RefreshCookie failed: 0x8024400e
2008-05-05 11:10:41:027 1084 10f0 PT WARNING: RefreshPTState failed:
0x8024400e
2008-05-05 11:10:41:027 1084 10f0 PT WARNING: Sync of Updates: 0x8024400e
2008-05-05 11:10:41:027 1084 10f0 PT WARNING: SyncServerUpdatesInternal
failed: 0x8024400e
2008-05-05 11:10:41:027 1084 10f0 Agent * WARNING: Failed to synchronize,
error = 0x8024400E
2008-05-05 11:10:41:056 1084 10f0 Agent * WARNING: Exit code = 0x8024400E
--
André Matos

[Lawrence Garvin [MVP]]

"tucum" <tu...@discussions.microsoft.com> wrote in message

news:67FCFBE8-A509-4680...@microsoft.com...

> Hello
> I looked into the Windows Update log but i didn't find any quotation marks
> In the target group i have only a blank space, i don't know if this is
> ok...

> 2008-05-05 11:10:41:000 1084 10f0 PT Initializing simple targeting cookie,

> clientId = 8857e030-02d6-4244-93b0-1e1a140a23c2,
> target group = ,
> DNS name = nc-desenv01.numericon.com.br

The blank space means that the client knows nothing about any assigned
target group.

This could be because you've not configured client-side targeting via Group
Policy,
or because the Group Policy that is configured is not being properly
applied,
or there is a flaw in the Group Policy causing it to be ignored by the
WUA,
or because you're using server-side targeting and the machine is
actually in "Unassigned Computers".

[tucum]

Thanks for your answer and sorry for my late reply
Can the situations you described cause the 8024400E error?
--
André Matos

[Lawrence Garvin [MVP]]

"tucum" <tu...@discussions.microsoft.com> wrote in message

news:7751F736-D052-4470...@microsoft.com...

>> > 2008-05-05 11:10:41:000 1084 10f0 PT Initializing simple targeting
>> > cookie,
>> > clientId = 8857e030-02d6-4244-93b0-1e1a140a23c2,
>> > target group = ,
>> > DNS name = nc-desenv01.numericon.com.br
>>
>> The blank space means that the client knows nothing about any assigned
>> target group.
>>
>> This could be because you've not configured client-side targeting via
>> Group
>> Policy,
>> or because the Group Policy that is configured is not being properly
>> applied,
>> or there is a flaw in the Group Policy causing it to be ignored by
>> the
>> WUA,
>> or because you're using server-side targeting and the machine is
>> actually in "Unassigned Computers".

> Thanks for your answer and sorry for my late reply

> Can the situations you described cause the 8024400E error?

Not likely....

0x8024400e - SUS E PT SOAP SERVER
The message was OK but server couldn't process at the moment

[Ben Radlinski]

I'm getting the 0x80072EFD error, but I actually know why...some of my
clients are still pointing at the old WSUS server address.

I've changed the address in the default domain policy and searched for
any other policies that might contain the old address and have found
nothing. I've run gpupdate /force and wuauclt /detectnow on all the
problem clients and despite the fact that they indicate the gp has been
applied successfully the old address still shows up in the log file. I
tried creating a new gp object for the domain and the systems will still
not update. I guess this is more of a GP question, but what could I be
doing wrong?

Thanks.

Ben

[Augusto Alvarez]

Try using on each client where do you have the error the "Resultant Set of
Policy" snap-ip (open mmc and add it). This will give you the exact policies
that are actually applying on that client, and if you dont find the update
policy pointing to your WSUS that might be the issue.

Hope it helps,

Cheers

--

augusto alvarez | it pro | southworks s.r.l.
http://blogs.southworks.net/aalvarez

"Ben Radlinski" <ben3...@gmail.com> wrote in message
news:eBIOR%23O7IH...@TK2MSFTNGP03.phx.gbl...

[Ben Radlinski]

I forgot to mention that I'd done that as well. It's showing that the
system is getting the policy with the old address, but indicates it's
the same policy, "default domain policy" under "Winning GPO". I'm confused.

[Augusto Alvarez]

Try running "gpupdate /force" and then check your event viewer, should
appear some error about not being able to apply domain policies.

If it does, then check on the Event ID number.

Cheers

--

augusto alvarez | it pro | southworks s.r.l.
http://blogs.southworks.net/aalvarez

"Ben Radlinski" <ben3...@gmail.com> wrote in message

news:%23qbWpOP...@TK2MSFTNGP05.phx.gbl...

[Ben Radlinski]

That's the thing. It says the policy was applied successfully.

[Augusto Alvarez]

You have a different GPO applied to the domain besides the Default Domain
Policy?

Enforce the WSUS GPO, this way you'll be certain that no other high level
policy is being applied on the clients (unless that this high level GPO is
already enforced on the domain)

Cheers

--

augusto alvarez | it pro | southworks s.r.l.
http://blogs.southworks.net/aalvarez

"Ben Radlinski" <ben3...@gmail.com> wrote in message

news:%23BpS7HQ...@TK2MSFTNGP04.phx.gbl...

[Ben Radlinski]

Thanks for that...creating its own policy and enforcing made it work.

I appreciate the help.