WSUS 0x80072ee2 Error
Hi,
we have a WSUS version 3.2.7600.226 built on windows server 2003 SP2
It works fine for existing client machines.
there is a issue with new built machine. the log as below
#############
2016-06-07 21:57:37:483 1076 1398 AU ## START ## AU: Search for updates
2016-06-07 21:57:37:483 1076 1398 AU #########
2016-06-07 21:57:37:484 1076 1398 AU <<## SUBMITTED ## AU: Search for updates [CallId = {433C774D-C1DD-4A05-A223-A
2016-06-07 21:57:37:484 1076 1038 Agent *************
2016-06-07 21:57:37:484 1076 1038 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2016-06-07 21:57:37:484 1076 1038 Agent *********
2016-06-07 21:57:37:484 1076 1038 Agent * Online = Yes; Ignore download priority = No
2016-06-07 21:57:37:484 1076 1038 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installa
2016-06-07 21:57:37:484 1076 1038 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B
2016-06-07 21:57:37:484 1076 1038 Agent * Search Scope = {Machine}
2016-06-07 21:57:37:485 1076 1038 Setup Checking for agent SelfUpdate
2016-06-07 21:57:37:485 1076 1038 Setup Client version: Core: 7.6.7601.18979 Aux: 7.6.7601.18979
2016-06-07 21:57:39:758 1076 1038 Misc Validating signature for C:\windows\SoftwareDistrib
2016-06-07 21:57:39:761 1076 1038 Misc Microsoft signed: NA
2016-06-07 21:57:39:761 1076 1038 Misc WARNING: Cab does not contain correct inner CAB file.
2016-06-07 21:57:39:761 1076 1038 Misc Validating signature for C:\windows\SoftwareDistrib
2016-06-07 21:57:39:764 1076 1038 Misc Microsoft signed: NA
2016-06-07 21:57:39:765 1076 1038 Setup Wuident for the managed service is valid but not quorum-signed. Skipping selfupdate.
2016-06-07 21:57:39:765 1076 1038 Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
2016-06-07 21:57:39:765 1076 1038 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2016-06-07 21:57:39:815 1076 1038 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2016-06-07 21:57:39:815 1076 1038 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B
2016-06-07 21:57:39:827 1076 1038 PT WARNING: Cached cookie has expired or new PID is available
2016-06-07 21:57:39:827 1076 1038 PT Initializing simple targeting cookie, clientId = a3dec764-7280-4a4b-8aa2-ef
2016-06-07 21:57:39:827 1076 1038 PT Server URL = http://nxt10:8530/SimpleAuthWebService/SimpleAuth.asmx
2016-06-07 21:58:42:118 1076 1038 Misc WARNING: Send failed with hr = 80072ee2.
2016-06-07 21:58:42:118 1076 1038 Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2016-06-07 21:58:42:118 1076 1038 Misc FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2
2016-06-07 21:58:42:118 1076 1038 PT + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
2016-06-07 21:58:42:118 1076 1038 PT + Caller provided credentials = No
2016-06-07 21:58:42:118 1076 1038 PT + Impersonate flags = 0
2016-06-07 21:58:42:118 1076 1038 PT + Possible authorization schemes used =
2016-06-07 21:58:42:118 1076 1038 PT WARNING: SyncUpdates failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
2016-06-07 21:58:42:118 1076 1038 PT WARNING: PTError: 0x80072ee2
2016-06-07 21:58:42:118 1076 1038 PT WARNING: SyncUpdates_WithRecovery failed.: 0x80072ee2
2016-06-07 21:58:42:118 1076 1038 PT WARNING: Sync of Updates: 0x80072ee2
2016-06-07 21:58:42:118 1076 1038 PT WARNING: SyncServerUpdatesInternal failed: 0x80072ee2
2016-06-07 21:58:42:118 1076 1038 Agent * WARNING: Failed to synchronize, error = 0x80072EE2
2016-06-07 21:58:42:119 1076 1038 Agent * WARNING: Exit code = 0x80072EE2
2016-06-07 21:58:42:119 1076 1038 Agent *********
2016-06-07 21:58:42:119 1076 1038 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2016-06-07 21:58:42:119 1076 1038 Agent *************
It looks like a communication issue between the client machine and WSUS server. but I tried to disable firewalls on both machine, problem still persists.
I also tried to recreate susclientid by deleting HKEY_LOCAL_MACHINE\SOFTWAR
we have a WSUS version 3.2.7600.226 built on windows server 2003 SP2
It works fine for existing client machines.
there is a issue with new built machine. the log as below
#############
2016-06-07 21:57:37:483 1076 1398 AU ## START ## AU: Search for updates
2016-06-07 21:57:37:483 1076 1398 AU #########
2016-06-07 21:57:37:484 1076 1398 AU <<## SUBMITTED ## AU: Search for updates [CallId = {433C774D-C1DD-4A05-A223-A
2016-06-07 21:57:37:484 1076 1038 Agent *************
2016-06-07 21:57:37:484 1076 1038 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2016-06-07 21:57:37:484 1076 1038 Agent *********
2016-06-07 21:57:37:484 1076 1038 Agent * Online = Yes; Ignore download priority = No
2016-06-07 21:57:37:484 1076 1038 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installa
2016-06-07 21:57:37:484 1076 1038 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B
2016-06-07 21:57:37:484 1076 1038 Agent * Search Scope = {Machine}
2016-06-07 21:57:37:485 1076 1038 Setup Checking for agent SelfUpdate
2016-06-07 21:57:37:485 1076 1038 Setup Client version: Core: 7.6.7601.18979 Aux: 7.6.7601.18979
2016-06-07 21:57:39:758 1076 1038 Misc Validating signature for C:\windows\SoftwareDistrib
2016-06-07 21:57:39:761 1076 1038 Misc Microsoft signed: NA
2016-06-07 21:57:39:761 1076 1038 Misc WARNING: Cab does not contain correct inner CAB file.
2016-06-07 21:57:39:761 1076 1038 Misc Validating signature for C:\windows\SoftwareDistrib
2016-06-07 21:57:39:764 1076 1038 Misc Microsoft signed: NA
2016-06-07 21:57:39:765 1076 1038 Setup Wuident for the managed service is valid but not quorum-signed. Skipping selfupdate.
2016-06-07 21:57:39:765 1076 1038 Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
2016-06-07 21:57:39:765 1076 1038 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2016-06-07 21:57:39:815 1076 1038 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2016-06-07 21:57:39:815 1076 1038 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B
2016-06-07 21:57:39:827 1076 1038 PT WARNING: Cached cookie has expired or new PID is available
2016-06-07 21:57:39:827 1076 1038 PT Initializing simple targeting cookie, clientId = a3dec764-7280-4a4b-8aa2-ef
2016-06-07 21:57:39:827 1076 1038 PT Server URL = http://nxt10:8530/SimpleAuthWebService/SimpleAuth.asmx
2016-06-07 21:58:42:118 1076 1038 Misc WARNING: Send failed with hr = 80072ee2.
2016-06-07 21:58:42:118 1076 1038 Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2016-06-07 21:58:42:118 1076 1038 Misc FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2
2016-06-07 21:58:42:118 1076 1038 PT + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
2016-06-07 21:58:42:118 1076 1038 PT + Caller provided credentials = No
2016-06-07 21:58:42:118 1076 1038 PT + Impersonate flags = 0
2016-06-07 21:58:42:118 1076 1038 PT + Possible authorization schemes used =
2016-06-07 21:58:42:118 1076 1038 PT WARNING: SyncUpdates failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
2016-06-07 21:58:42:118 1076 1038 PT WARNING: PTError: 0x80072ee2
2016-06-07 21:58:42:118 1076 1038 PT WARNING: SyncUpdates_WithRecovery failed.: 0x80072ee2
2016-06-07 21:58:42:118 1076 1038 PT WARNING: Sync of Updates: 0x80072ee2
2016-06-07 21:58:42:118 1076 1038 PT WARNING: SyncServerUpdatesInternal failed: 0x80072ee2
2016-06-07 21:58:42:118 1076 1038 Agent * WARNING: Failed to synchronize, error = 0x80072EE2
2016-06-07 21:58:42:119 1076 1038 Agent * WARNING: Exit code = 0x80072EE2
2016-06-07 21:58:42:119 1076 1038 Agent *********
2016-06-07 21:58:42:119 1076 1038 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2016-06-07 21:58:42:119 1076 1038 Agent *************
It looks like a communication issue between the client machine and WSUS server. but I tried to disable firewalls on both machine, problem still persists.
I also tried to recreate susclientid by deleting HKEY_LOCAL_MACHINE\SOFTWAR
First I think you're missing this update:
https://support.microsoft.com/en-us/kb/2720211
Then after update and reboot, run:
C:\Program Files\Update Services\Tools\wsusutil.ex
This will reconfigure the WSUS IIS site to operate on port 80
C:\Program Files\Update Services\Tools\wsusutil.ex
This will reconfigure the WSUS IIS site to operate on port 8530
Even though it might have been port 8530 to being with, setting it to 80 then back to 8530, adjusts some IIS settings needed to make WSUS operate normally.
https://support.microsoft.com/en-us/kb/2720211
Then after update and reboot, run:
C:\Program Files\Update Services\Tools\wsusutil.ex
This will reconfigure the WSUS IIS site to operate on port 80
C:\Program Files\Update Services\Tools\wsusutil.ex
This will reconfigure the WSUS IIS site to operate on port 8530
Even though it might have been port 8530 to being with, setting it to 80 then back to 8530, adjusts some IIS settings needed to make WSUS operate normally.
You still have Server 2003 SP2? This is no more supported and end of life. What are your clients? Windows 7?
ASKER
Yes, still Windows 2003…. All client Windows 7 32bit
Hi,
Have you consider my post? and Kimputer one?? I wanted to make sure the internet connectivity is OK for you and Kimputer provided a solution for this issue in the case if your network connectivity is OK!!
But you only consider the last post and reply to it without following all posts and contents!! why? you don't have a time? if so do experts wil have a time to spend in writing an answer that will not be considered by the asker?
Regards.
Salah
Have you consider my post? and Kimputer one?? I wanted to make sure the internet connectivity is OK for you and Kimputer provided a solution for this issue in the case if your network connectivity is OK!!
But you only consider the last post and reply to it without following all posts and contents!! why? you don't have a time? if so do experts wil have a time to spend in writing an answer that will not be considered by the asker?
Regards.
Salah
ASKER
Sorry, salah. Thanks for the answer.
I don't think it is a internet issue. wsus server can still sync the new updates from upstream servers.
Wsus settings also haven't been changed recently
Kimputer, I will try your solution and let you know tomorrow
Ta
I don't think it is a internet issue. wsus server can still sync the new updates from upstream servers.
Wsus settings also haven't been changed recently
Kimputer, I will try your solution and let you know tomorrow
Ta
Hi,
To confirm Kimputer solution, have a look here
http://serverfault.com/questions/740833/wsus-clients-failing-to-get-updates-with-error-80072ee2
If you find erros in IIS as described on the screen shot, just follow Kimputer instructions.
Regards.
Salah
To confirm Kimputer solution, have a look here
http://serverfault.com/questions/740833/wsus-clients-failing-to-get-updates-with-error-80072ee2
If you find erros in IIS as described on the screen shot, just follow Kimputer instructions.
Regards.
Salah
ASKER
Hi,
I followed Kimputer's instructions and got the same error.
It only happens with new deployed machines. Old machines are working fine.
There are the old machines update log if that helps
I suspect the wsus server refused to receive new client update by some reasons.
#############
2016-06-08 23:34:31:805 1040 1a00 AU ## START ## AU: Search for updates
2016-06-08 23:34:31:805 1040 1a00 AU #########
2016-06-08 23:34:31:806 1040 1a00 AU <<## SUBMITTED ## AU: Search for updates [CallId = {DD9DA49E-4115-4E18-8569-6
2016-06-08 23:34:31:807 1040 1c30 Agent *************
2016-06-08 23:34:31:807 1040 1c30 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2016-06-08 23:34:31:807 1040 1c30 Agent *********
2016-06-08 23:34:31:807 1040 1c30 Agent * Online = Yes; Ignore download priority = No
2016-06-08 23:34:31:807 1040 1c30 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installa
2016-06-08 23:34:31:807 1040 1c30 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B
2016-06-08 23:34:31:807 1040 1c30 Agent * Search Scope = {Machine}
2016-06-08 23:34:31:834 1040 1c30 Setup Checking for agent SelfUpdate
2016-06-08 23:34:31:835 1040 1c30 Setup Client version: Core: 7.6.7601.19046 Aux: 7.6.7601.19046
2016-06-08 23:34:34:120 1040 1c30 Misc Validating signature for C:\windows\SoftwareDistrib
2016-06-08 23:34:34:129 1040 1c30 Misc Microsoft signed: NA
2016-06-08 23:34:34:130 1040 1c30 Misc WARNING: Cab does not contain correct inner CAB file.
2016-06-08 23:34:34:130 1040 1c30 Misc Validating signature for C:\windows\SoftwareDistrib
2016-06-08 23:34:34:133 1040 1c30 Misc Microsoft signed: NA
2016-06-08 23:34:34:135 1040 1c30 Setup Wuident for the managed service is valid but not quorum-signed. Skipping selfupdate.
2016-06-08 23:34:34:135 1040 1c30 Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
2016-06-08 23:34:34:135 1040 1c30 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2016-06-08 23:34:35:075 1040 1c30 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2016-06-08 23:34:35:075 1040 1c30 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B
2016-06-08 23:34:35:091 1040 1c30 PT WARNING: Cached cookie has expired or new PID is available
2016-06-08 23:34:35:092 1040 1c30 PT Initializing simple targeting cookie, clientId = 40437ef0-8c31-4a38-874d-0d
2016-06-08 23:34:35:092 1040 1c30 PT Server URL = http://nxt10:8530/SimpleAuthWebService/SimpleAuth.asmx
2016-06-08 23:34:57:244 1040 1c30 PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2016-06-08 23:34:57:244 1040 1c30 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B
2016-06-08 23:34:58:475 1040 1c30 Agent * Found 0 updates and 90 categories in search; evaluated appl. rules of 3873 out of 6596 deployed entities
2016-06-08 23:34:58:478 1040 1c30 Agent *********
2016-06-08 23:34:58:478 1040 1c30 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2016-06-08 23:34:58:478 1040 1c30 Agent *************
2016-06-08 23:34:58:481 1040 2cb8 AU >>## RESUMED ## AU: Search for updates [CallId = {DD9DA49E-4115-4E18-8569-6
2016-06-08 23:34:58:481 1040 2cb8 AU # 0 updates detected
2016-06-08 23:34:58:481 1040 2cb8 AU #########
2016-06-08 23:34:58:481 1040 2cb8 AU ## END ## AU: Search for updates [CallId = {DD9DA49E-4115-4E18-8569-6
2016-06-08 23:34:58:481 1040 2cb8 AU #############
I followed Kimputer's instructions and got the same error.
It only happens with new deployed machines. Old machines are working fine.
There are the old machines update log if that helps
I suspect the wsus server refused to receive new client update by some reasons.
#############
2016-06-08 23:34:31:805 1040 1a00 AU ## START ## AU: Search for updates
2016-06-08 23:34:31:805 1040 1a00 AU #########
2016-06-08 23:34:31:806 1040 1a00 AU <<## SUBMITTED ## AU: Search for updates [CallId = {DD9DA49E-4115-4E18-8569-6
2016-06-08 23:34:31:807 1040 1c30 Agent *************
2016-06-08 23:34:31:807 1040 1c30 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2016-06-08 23:34:31:807 1040 1c30 Agent *********
2016-06-08 23:34:31:807 1040 1c30 Agent * Online = Yes; Ignore download priority = No
2016-06-08 23:34:31:807 1040 1c30 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installa
2016-06-08 23:34:31:807 1040 1c30 Agent * ServiceID = {3DA21691-E39D-4DA6-8A4B-B
2016-06-08 23:34:31:807 1040 1c30 Agent * Search Scope = {Machine}
2016-06-08 23:34:31:834 1040 1c30 Setup Checking for agent SelfUpdate
2016-06-08 23:34:31:835 1040 1c30 Setup Client version: Core: 7.6.7601.19046 Aux: 7.6.7601.19046
2016-06-08 23:34:34:120 1040 1c30 Misc Validating signature for C:\windows\SoftwareDistrib
2016-06-08 23:34:34:129 1040 1c30 Misc Microsoft signed: NA
2016-06-08 23:34:34:130 1040 1c30 Misc WARNING: Cab does not contain correct inner CAB file.
2016-06-08 23:34:34:130 1040 1c30 Misc Validating signature for C:\windows\SoftwareDistrib
2016-06-08 23:34:34:133 1040 1c30 Misc Microsoft signed: NA
2016-06-08 23:34:34:135 1040 1c30 Setup Wuident for the managed service is valid but not quorum-signed. Skipping selfupdate.
2016-06-08 23:34:34:135 1040 1c30 Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
2016-06-08 23:34:34:135 1040 1c30 Setup SelfUpdate check completed. SelfUpdate is NOT required.
2016-06-08 23:34:35:075 1040 1c30 PT +++++++++++ PT: Synchronizing server updates +++++++++++
2016-06-08 23:34:35:075 1040 1c30 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B
2016-06-08 23:34:35:091 1040 1c30 PT WARNING: Cached cookie has expired or new PID is available
2016-06-08 23:34:35:092 1040 1c30 PT Initializing simple targeting cookie, clientId = 40437ef0-8c31-4a38-874d-0d
2016-06-08 23:34:35:092 1040 1c30 PT Server URL = http://nxt10:8530/SimpleAuthWebService/SimpleAuth.asmx
2016-06-08 23:34:57:244 1040 1c30 PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2016-06-08 23:34:57:244 1040 1c30 PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B
2016-06-08 23:34:58:475 1040 1c30 Agent * Found 0 updates and 90 categories in search; evaluated appl. rules of 3873 out of 6596 deployed entities
2016-06-08 23:34:58:478 1040 1c30 Agent *********
2016-06-08 23:34:58:478 1040 1c30 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2016-06-08 23:34:58:478 1040 1c30 Agent *************
2016-06-08 23:34:58:481 1040 2cb8 AU >>## RESUMED ## AU: Search for updates [CallId = {DD9DA49E-4115-4E18-8569-6
2016-06-08 23:34:58:481 1040 2cb8 AU # 0 updates detected
2016-06-08 23:34:58:481 1040 2cb8 AU #########
2016-06-08 23:34:58:481 1040 2cb8 AU ## END ## AU: Search for updates [CallId = {DD9DA49E-4115-4E18-8569-6
2016-06-08 23:34:58:481 1040 2cb8 AU #############
Hi,
The new clients are similar to old ones?
Regards.
Salah
The new clients are similar to old ones?
Regards.
Salah
Hi,
Please confirm that the new cumputer are listed in WSUS computer list and you did approve the related updates to be installed?
Regards.
Salah
Please confirm that the new cumputer are listed in WSUS computer list and you did approve the related updates to be installed?
Regards.
Salah
ASKER
Hi Salah,
Only new clients have the issue, Old ones work perfectly.
I did put new clients to the computer group which already has approved updates.
But there is error machine on the machine says "this computer has not reported status yet"
Only new clients have the issue, Old ones work perfectly.
I did put new clients to the computer group which already has approved updates.
But there is error machine on the machine says "this computer has not reported status yet"
Hi,
You don't use GPO?
Regards.
You don't use GPO?
Regards.
ASKER
I do, but I manually assign machines to different groups.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi,
Did you solve the issue?
Salah
Did you solve the issue?
Salah
ASKER
Hi Salah,
Thank you for you help.
That solution didn't solve it.
it may be a bug that ms doesn't support ws 2003 anymore.
I have create a new wsus server on windows 2008R2 and running perfectly now.
Thank you for you help.
That solution didn't solve it.
it may be a bug that ms doesn't support ws 2003 anymore.
I have create a new wsus server on windows 2008R2 and running perfectly now.
The issue is not being between your WSUS and clients, but between WSUS and Internet!
DId you change any setting your WSUS server?, can you access Internet from your WSUS server?
Regards.
Salah