0x80072ee2 Error When Attempting Update

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Windows XP SP2 Here.. Using a central company SUS Server for AU, when
Defender attempts to update, returns a 0x80072ee2 error. WindowsUpdate.log
file below -- Any ideas?:

2006-02-14 16:19:10 2056 b48 COMAPI -------------
2006-02-14 16:19:10 2056 b48 COMAPI -- START -- COMAPI: Search [ClientId =
Windows Defender]
2006-02-14 16:19:10 2056 b48 COMAPI ---------
2006-02-14 16:19:10 2056 b48 COMAPI - Online = Yes; Ignore download
priority = No
2006-02-14 16:19:10 2056 b48 COMAPI - Criteria = "(IsInstalled = 0 and
IsHidden = 0 and CategoryIDs contains '0a487050-8b0f-4f81-b401-be4ceacd61cd')
or (IsInstalled = 0 and IsHidden = 0 and CategoryIDs contains
'8c3fcc84-7410-4a95-8b89-a166a0190486')"
2006-02-14 16:19:10 2056 b48 COMAPI - ServiceID =
{00000000-0000-0000-0000-000000000000}
2006-02-14 16:19:10 2056 b48 COMAPI <<-- SUBMITTED -- COMAPI: Search
[ClientId = Windows Defender]
2006-02-14 16:19:10 1112 738 Agent *************
2006-02-14 16:19:10 1112 738 Agent ** START ** Agent: Finding updates
[CallerId = Windows Defender]
2006-02-14 16:19:10 1112 738 Agent *********
2006-02-14 16:19:11 1112 738 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-02-14 16:19:11 1112 738 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://susserver.company.com/ClientWebService/client.asmx
2006-02-14 16:20:12 1112 738 Misc WARNING: SendRequest failed with hr =
80072ee2. Proxy List used: <192.168.1.3:3128> Bypass List used :
<.*;192.168.*;*.company.com;*.sec.company.local;<local>> Auth Schemes used :
<>
2006-02-14 16:20:12 1112 738 PT + Last proxy send request failed with hr =
0x80072EE2, HTTP status code = 0
2006-02-14 16:20:12 1112 738 PT + Caller provided proxy = No
2006-02-14 16:20:12 1112 738 PT + Proxy list used = 192.168.1.3:3128
2006-02-14 16:20:12 1112 738 PT + Bypass list used =
192.168.*;*.company.com;*.sec.company.local;<local>
2006-02-14 16:20:12 1112 738 PT + Caller provided credentials = No
2006-02-14 16:20:12 1112 738 PT + Impersonate flags = 0
2006-02-14 16:20:12 1112 738 PT + Possible authorization schemes used =
2006-02-14 16:20:12 1112 738 PT WARNING: GetConfig failure, error =
0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
2006-02-14 16:20:12 1112 738 PT WARNING: Sync of Updates: 0x80072ee2
2006-02-14 16:20:12 1112 738 Agent * WARNING: Failed to synchronize, error
= 0x80072EE2
2006-02-14 16:20:12 1112 738 Agent * WARNING: Exit code = 0x80072EE2
2006-02-14 16:20:12 1112 738 Agent *********
2006-02-14 16:20:12 1112 738 Agent ** END ** Agent: Finding updates
[CallerId = Windows Defender]
2006-02-14 16:20:12 1112 738 Agent *************
2006-02-14 16:20:12 1112 738 Agent WARNING: WU client failed Searching for
update with error 0x80072ee2
2006-02-14 16:20:12 2056 ca8 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = Windows Defender]
2006-02-14 16:20:12 2056 ca8 COMAPI - Updates found = 0
2006-02-14 16:20:12 2056 ca8 COMAPI - WARNING: Exit code = 0x00000000,
Result code = 0x80072EE2
2006-02-14 16:20:12 2056 ca8 COMAPI ---------
2006-02-14 16:20:12 2056 ca8 COMAPI -- END -- COMAPI: Search [ClientId =
Windows Defender]
2006-02-14 16:20:12 2056 ca8 COMAPI -------------
2006-02-14 16:20:12 2056 ac4 COMAPI WARNING: Operation failed due to earlier
error, hr=80072EE2
2006-02-14 16:20:12 2056 ac4 COMAPI FATAL: Unable to complete asynchronous
search. (hr=80072EE2)
2006-02-14 16:20:17 1112 738 Report REPORT EVENT:
{6009D3F8-7DCA-4EA1-A56A-C7DCBFBC2D1E} 2006-02-14
16:20:12-0500 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80072ee2 Windows
Defender Failure Software Synchronization Error: Agent failed detecting with
reason: 0x80072ee2
 
WSUS is required. In a pure SUS only environment, where Windows Update and
AU are locked out, I don't know what to recommend.
--

RickNY said:
Windows XP SP2 Here.. Using a central company SUS Server for AU, when
Defender attempts to update, returns a 0x80072ee2 error.
WindowsUpdate.log
file below -- Any ideas?:

2006-02-14 16:19:10 2056 b48 COMAPI -------------
2006-02-14 16:19:10 2056 b48 COMAPI -- START -- COMAPI: Search [ClientId
=
Windows Defender]
2006-02-14 16:19:10 2056 b48 COMAPI ---------
2006-02-14 16:19:10 2056 b48 COMAPI - Online = Yes; Ignore download
priority = No
2006-02-14 16:19:10 2056 b48 COMAPI - Criteria = "(IsInstalled = 0 and
IsHidden = 0 and CategoryIDs contains
'0a487050-8b0f-4f81-b401-be4ceacd61cd')
or (IsInstalled = 0 and IsHidden = 0 and CategoryIDs contains
'8c3fcc84-7410-4a95-8b89-a166a0190486')"
2006-02-14 16:19:10 2056 b48 COMAPI - ServiceID =
{00000000-0000-0000-0000-000000000000}
2006-02-14 16:19:10 2056 b48 COMAPI <<-- SUBMITTED -- COMAPI: Search
[ClientId = Windows Defender]
2006-02-14 16:19:10 1112 738 Agent *************
2006-02-14 16:19:10 1112 738 Agent ** START ** Agent: Finding updates
[CallerId = Windows Defender]
2006-02-14 16:19:10 1112 738 Agent *********
2006-02-14 16:19:11 1112 738 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2006-02-14 16:19:11 1112 738 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://susserver.company.com/ClientWebService/client.asmx
2006-02-14 16:20:12 1112 738 Misc WARNING: SendRequest failed with hr =
80072ee2. Proxy List used: <192.168.1.3:3128> Bypass List used :
<.*;192.168.*;*.company.com;*.sec.company.local;<local>> Auth Schemes used
:
<>
2006-02-14 16:20:12 1112 738 PT + Last proxy send request failed with hr
=
0x80072EE2, HTTP status code = 0
2006-02-14 16:20:12 1112 738 PT + Caller provided proxy = No
2006-02-14 16:20:12 1112 738 PT + Proxy list used = 192.168.1.3:3128
2006-02-14 16:20:12 1112 738 PT + Bypass list used =
192.168.*;*.company.com;*.sec.company.local;<local>
2006-02-14 16:20:12 1112 738 PT + Caller provided credentials = No
2006-02-14 16:20:12 1112 738 PT + Impersonate flags = 0
2006-02-14 16:20:12 1112 738 PT + Possible authorization schemes used =
2006-02-14 16:20:12 1112 738 PT WARNING: GetConfig failure, error =
0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code =
200
2006-02-14 16:20:12 1112 738 PT WARNING: Sync of Updates: 0x80072ee2
2006-02-14 16:20:12 1112 738 Agent * WARNING: Failed to synchronize,
error
= 0x80072EE2
2006-02-14 16:20:12 1112 738 Agent * WARNING: Exit code = 0x80072EE2
2006-02-14 16:20:12 1112 738 Agent *********
2006-02-14 16:20:12 1112 738 Agent ** END ** Agent: Finding updates
[CallerId = Windows Defender]
2006-02-14 16:20:12 1112 738 Agent *************
2006-02-14 16:20:12 1112 738 Agent WARNING: WU client failed Searching for
update with error 0x80072ee2
2006-02-14 16:20:12 2056 ca8 COMAPI >>-- RESUMED -- COMAPI: Search
[ClientId = Windows Defender]
2006-02-14 16:20:12 2056 ca8 COMAPI - Updates found = 0
2006-02-14 16:20:12 2056 ca8 COMAPI - WARNING: Exit code = 0x00000000,
Result code = 0x80072EE2
2006-02-14 16:20:12 2056 ca8 COMAPI ---------
2006-02-14 16:20:12 2056 ca8 COMAPI -- END -- COMAPI: Search [ClientId
=
Windows Defender]
2006-02-14 16:20:12 2056 ca8 COMAPI -------------
2006-02-14 16:20:12 2056 ac4 COMAPI WARNING: Operation failed due to
earlier
error, hr=80072EE2
2006-02-14 16:20:12 2056 ac4 COMAPI FATAL: Unable to complete asynchronous
search. (hr=80072EE2)
2006-02-14 16:20:17 1112 738 Report REPORT EVENT:
{6009D3F8-7DCA-4EA1-A56A-C7DCBFBC2D1E} 2006-02-14
16:20:12-0500 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80072ee2
Windows
Defender Failure Software Synchronization Error: Agent failed detecting
with
reason: 0x80072ee2
Click to expand...
 
Windows Update is not locked out though.. While we are configured for AU via
SUS, we can always manually go to Windows Update/Microsoft Update/Office
Update and update those products manually. It seems Windows Defender is
NOT allowing that to happen when initiating a manual update -- but rather, is
ONLY making attempts at the AU server specified in the registry -- even when
a manual update is attempted. I dont feel this is proper behavior.

Rick
 
You may know more about what is happening than I do. I have wondered
whether Microsoft might, in a managed environment, lock the updating to the
management tools--i.e. keep the users from doing an end-run around the
desired mechanism--but I don't know enough about this stuff to understand
the ins and outs of that question.

I'm hoping that one of the Microsoft folks will spot some of these SUS
environment questions and give us a clue about what should happen in that
situation.
--
 
Back
Top