locked
WSUS server 2012 R2 - two client with problems RRS feed

  • Question

  • Scenario:

    Old Wsus server on 2008 R2 without problems

    New Wsus server om 2012 R2 fresh installed

    Domain GPO for Wsus parameters and target group.

    DB on other server (SQL server)

    More of 200 client without problems (from Windows Vista to Windows server 2012 R2).

    Now we have a new server, fresh installed, Windows 2008 R2 Enterprise (it must be a Exchange DAG member, we cannot install other operating system version) that don't report the status and a old server that stopped report when new Wsus server has been installed.

    The WindowsUpdateLog of the server that has stopped reporting:

    2016-08-31 15:44:07:485 1016 1094 AU Triggering AU detection through DetectNow API
    2016-08-31 15:44:07:485 1016 1094 AU Triggering Online detection (non-interactive)
    2016-08-31 15:44:07:485 1016 c50 AU #############
    2016-08-31 15:44:07:485 1016 c50 AU ## START ##  AU: Search for updates
    2016-08-31 15:44:07:485 1016 c50 AU #########
    2016-08-31 15:44:07:501 1016 c50 AU <<## SUBMITTED ## AU: Search for updates [CallId = {BB2B740A-BA56-4D26-9067-8F5C337A3CBA}]
    2016-08-31 15:44:07:501 1016 1b10 Agent *************
    2016-08-31 15:44:07:501 1016 1b10 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-08-31 15:44:07:501 1016 1b10 Agent *********
    2016-08-31 15:44:07:501 1016 1b10 Agent   * Online = Yes; Ignore download priority = No
    2016-08-31 15:44:07:501 1016 1b10 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2016-08-31 15:44:07:501 1016 1b10 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2016-08-31 15:44:07:501 1016 1b10 Agent   * Search Scope = {Machine}
    2016-08-31 15:44:07:579 1016 1b10 Setup Checking for agent SelfUpdate
    2016-08-31 15:44:07:579 1016 1b10 Setup Client version: Core: 7.6.7601.23453  Aux: 7.6.7601.23453
    2016-08-31 15:44:07:610 1016 1b10 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2016-08-31 15:44:07:642 1016 1b10 Misc  Microsoft signed: NA
    2016-08-31 15:44:07:657 1016 1b10 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP2379.tmp with dwProvFlags 0x00000080:
    2016-08-31 15:44:07:688 1016 1b10 Misc  Microsoft signed: NA
    2016-08-31 15:44:07:704 1016 1b10 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2016-08-31 15:44:07:720 1016 1b10 Misc  Microsoft signed: NA
    2016-08-31 15:44:07:813 1016 1b10 Setup Determining whether a new setup handler needs to be downloaded
    2016-08-31 15:44:07:813 1016 1b10 Setup SelfUpdate handler is not found.  It will be downloaded
    2016-08-31 15:44:07:813 1016 1b10 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-08-31 15:44:07:845 1016 1b10 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is not applicable
    2016-08-31 15:44:07:845 1016 1b10 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-08-31 15:44:07:876 1016 1b10 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is not applicable
    2016-08-31 15:44:07:876 1016 1b10 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-08-31 15:44:07:923 1016 1b10 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is not applicable
    2016-08-31 15:44:07:923 1016 1b10 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2016-08-31 15:44:08:110 1016 1b10 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2016-08-31 15:44:08:110 1016 1b10 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://susserver.xxxyyyzzz.it/ClientWebService/client.asmx
    2016-08-31 15:44:08:173 1016 1b10 PT WARNING: Cached cookie has expired or new PID is available
    2016-08-31 15:44:08:173 1016 1b10 PT Initializing simple targeting cookie, clientId = b1212b2e-96d0-4bbd-aa31-8d8ec9c77468, target group = Server, DNS name = srvweb03.xxxyyyzzz.it
    2016-08-31 15:44:08:173 1016 1b10 PT   Server URL = http://susserver.xxxyyyzzz.it/SimpleAuthWebService/SimpleAuth.asmx
    2016-08-31 15:48:21:796 1016 1b10 Misc WARNING: Send failed with hr = 80072ee2.
    2016-08-31 15:48:21:796 1016 1b10 Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2016-08-31 15:48:21:796 1016 1b10 Misc FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2
    2016-08-31 15:48:21:796 1016 1b10 PT   + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
    2016-08-31 15:48:21:796 1016 1b10 PT   + Caller provided credentials = No
    2016-08-31 15:48:21:796 1016 1b10 PT   + Impersonate flags = 0
    2016-08-31 15:48:21:796 1016 1b10 PT   + Possible authorization schemes used =
    2016-08-31 15:48:21:796 1016 1b10 PT WARNING: SyncUpdates failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
    2016-08-31 15:48:21:796 1016 1b10 PT WARNING: PTError: 0x80072ee2
    2016-08-31 15:48:21:796 1016 1b10 PT WARNING: SyncUpdates_WithRecovery failed.: 0x80072ee2
    2016-08-31 15:48:21:796 1016 1b10 PT WARNING: Sync of Updates: 0x80072ee2
    2016-08-31 15:48:21:796 1016 1b10 PT WARNING: SyncServerUpdatesInternal failed: 0x80072ee2
    2016-08-31 15:48:21:796 1016 1b10 Agent   * WARNING: Failed to synchronize, error = 0x80072EE2
    2016-08-31 15:48:21:812 1016 1b10 Agent   * WARNING: Exit code = 0x80072EE2
    2016-08-31 15:48:21:812 1016 1b10 Agent *********
    2016-08-31 15:48:21:812 1016 1b10 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-08-31 15:48:21:812 1016 1b10 Agent *************
    2016-08-31 15:48:21:812 1016 1b10 Agent WARNING: WU client failed Searching for update with error 0x80072ee2
    2016-08-31 15:48:21:827 1016 1a3c AU >>##  RESUMED  ## AU: Search for updates [CallId = {BB2B740A-BA56-4D26-9067-8F5C337A3CBA}]
    2016-08-31 15:48:21:827 1016 1a3c AU   # WARNING: Search callback failed, result = 0x80072EE2
    2016-08-31 15:48:21:827 1016 1a3c AU   # WARNING: Failed to find updates with error code 80072EE2
    2016-08-31 15:48:21:827 1016 1a3c AU #########
    2016-08-31 15:48:21:827 1016 1a3c AU ##  END  ##  AU: Search for updates [CallId = {BB2B740A-BA56-4D26-9067-8F5C337A3CBA}]
    2016-08-31 15:48:21:827 1016 1a3c AU #############
    2016-08-31 15:48:21:827 1016 1a3c AU Successfully wrote event for AU health state:0
    2016-08-31 15:48:21:827 1016 1a3c AU AU setting next detection timeout to 2016-08-31 18:48:21
    2016-08-31 15:48:21:827 1016 1a3c AU Successfully wrote event for AU health state:0
    2016-08-31 15:48:21:827 1016 1a3c AU Successfully wrote event for AU health state:0
    2016-08-31 15:48:26:812 1016 1b10 Report REPORT EVENT: {64630D37-4FB5-4196-9826-0BDA2B229797} 2016-08-31 15:48:21:812+0200 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80072ee2 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80072ee2.
    2016-08-31 15:48:26:843 1016 1b10 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2016-08-31 15:48:26:843 1016 1b10 Report WER Report sent: 7.6.7601.23453 0x80072ee2(0) 0000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdates {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2016-08-31 16:02:17:947 1016 1b10 Report Uploading 1 events using cached cookie, reporting URL = http://susserver.xxxyyyzzz.it/ReportingWebService/ReportingWebService.asmx
    2016-08-31 16:02:17:963 1016 1b10 Report Reporter successfully uploaded 1 events.

    And this is the log of the new fresh installed server:

    2016-08-31 13:34:36:445  848 79c AU #############
    2016-08-31 13:34:36:445  848 79c AU ## START ##  AU: Search for updates
    2016-08-31 13:34:36:445  848 79c AU #########
    2016-08-31 13:34:36:445  848 79c AU <<## SUBMITTED ## AU: Search for updates [CallId = {E24622D9-D58B-46DA-9A29-31687550613F}]
    2016-08-31 13:34:36:445  848 364 Agent *************
    2016-08-31 13:34:36:445  848 364 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-08-31 13:34:36:445  848 364 Agent *********
    2016-08-31 13:34:36:445  848 364 Agent   * Online = Yes; Ignore download priority = No
    2016-08-31 13:34:36:445  848 364 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2016-08-31 13:34:36:445  848 364 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2016-08-31 13:34:36:445  848 364 Agent   * Search Scope = {Machine}
    2016-08-31 13:34:36:476  848 364 Setup Checking for agent SelfUpdate
    2016-08-31 13:34:36:476  848 364 Setup Client version: Core: 7.6.7600.320  Aux: 7.6.7600.320
    2016-08-31 13:34:36:507  848 364 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2016-08-31 13:34:36:523  848 364 Misc  Microsoft signed: NA
    2016-08-31 13:34:36:523  848 364 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\TMP5391.tmp with dwProvFlags 0x00000080:
    2016-08-31 13:34:36:523  848 364 Misc  Microsoft signed: NA
    2016-08-31 13:34:36:523  848 364 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2016-08-31 13:34:36:538  848 364 Misc  Microsoft signed: NA
    2016-08-31 13:34:36:538  848 364 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab with dwProvFlags 0x00000080:
    2016-08-31 13:34:36:538  848 364 Misc  Microsoft signed: NA
    2016-08-31 13:34:36:554  848 364 Setup Determining whether a new setup handler needs to be downloaded
    2016-08-31 13:34:36:554  848 364 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe with dwProvFlags 0x00000080:
    2016-08-31 13:34:36:554  848 364 Misc  Microsoft signed: NA
    2016-08-31 13:34:36:554  848 364 Setup SelfUpdate handler update NOT required: Current version: 7.6.7600.320, required version: 7.6.7600.320
    2016-08-31 13:34:36:554  848 364 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-08-31 13:34:36:976  848 364 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-08-31 13:34:36:976  848 364 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-08-31 13:34:36:992  848 364 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-08-31 13:34:36:992  848 364 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320"
    2016-08-31 13:34:37:023  848 364 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320" is already installed.
    2016-08-31 13:34:37:023  848 364 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2016-08-31 13:34:39:320  848 364 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2016-08-31 13:34:39:320  848 364 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://susserver.xxxyyyzzz.it/ClientWebService/client.asmx
    2016-08-31 13:34:39:398  848 364 PT WARNING: Cached cookie has expired or new PID is available
    2016-08-31 13:34:39:398  848 364 PT Initializing simple targeting cookie, clientId = 07356f47-e8cf-4e40-8cee-e93366e5225f, target group = Server, DNS name = srvexchmb04.xxxyyyzzz.it
    2016-08-31 13:34:39:398  848 364 PT   Server URL = http://susserver.xxxyyyzzz.it/SimpleAuthWebService/SimpleAuth.asmx
    2016-08-31 13:36:52:381  848 364 Misc WARNING: Send failed with hr = 80072ee2.
    2016-08-31 13:36:52:381  848 364 Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2016-08-31 13:36:52:381  848 364 Misc FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2
    2016-08-31 13:36:52:381  848 364 PT   + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
    2016-08-31 13:36:52:381  848 364 PT   + Caller provided credentials = No
    2016-08-31 13:36:52:381  848 364 PT   + Impersonate flags = 0
    2016-08-31 13:36:52:381  848 364 PT   + Possible authorization schemes used =
    2016-08-31 13:36:52:381  848 364 PT WARNING: SyncUpdates failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
    2016-08-31 13:36:52:381  848 364 PT WARNING: PTError: 0x80072ee2
    2016-08-31 13:36:52:381  848 364 PT WARNING: SyncUpdates_WithRecovery failed.: 0x80072ee2
    2016-08-31 13:36:52:381  848 364 PT WARNING: Sync of Updates: 0x80072ee2
    2016-08-31 13:36:52:381  848 364 PT WARNING: SyncServerUpdatesInternal failed: 0x80072ee2
    2016-08-31 13:36:52:381  848 364 Agent   * WARNING: Failed to synchronize, error = 0x80072EE2
    2016-08-31 13:36:52:381  848 364 Agent   * WARNING: Exit code = 0x80072EE2
    2016-08-31 13:36:52:381  848 364 Agent *********
    2016-08-31 13:36:52:381  848 364 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-08-31 13:36:52:381  848 364 Agent *************
    2016-08-31 13:36:52:381  848 364 Agent WARNING: WU client failed Searching for update with error 0x80072ee2
    2016-08-31 13:36:52:412  848 66c AU >>##  RESUMED  ## AU: Search for updates [CallId = {E24622D9-D58B-46DA-9A29-31687550613F}]
    2016-08-31 13:36:52:412  848 66c AU   # WARNING: Search callback failed, result = 0x80072EE2
    2016-08-31 13:36:52:412  848 66c AU   # WARNING: Failed to find updates with error code 80072EE2
    2016-08-31 13:36:52:412  848 66c AU #########
    2016-08-31 13:36:52:412  848 66c AU ##  END  ##  AU: Search for updates [CallId = {E24622D9-D58B-46DA-9A29-31687550613F}]
    2016-08-31 13:36:52:412  848 66c AU #############
    2016-08-31 13:36:52:412  848 66c AU Successfully wrote event for AU health state:0
    2016-08-31 13:36:52:412  848 66c AU AU setting next detection timeout to 2016-08-31 16:36:52
    2016-08-31 13:36:52:412  848 66c AU Successfully wrote event for AU health state:0
    2016-08-31 13:36:52:412  848 66c AU Successfully wrote event for AU health state:0
    2016-08-31 13:36:57:381  848 364 Report REPORT EVENT: {13DF8E25-AFD5-4C4F-8F52-B1C5B5CFB70A} 2016-08-31 13:36:52:381+0200 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80072ee2 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80072ee2.
    2016-08-31 13:36:57:381  848 364 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2016-08-31 13:36:57:381  848 364 Report WER Report sent: 7.6.7600.320 0x80072ee2 00000000-0000-0000-0000-000000000000 Scan 101 Managed
    2016-08-31 13:36:57:381  848 364 Report CWERReporter finishing event handling. (00000000)
    2016-08-31 13:40:54:410  848 364 PT WARNING: Cached cookie has expired or new PID is available
    2016-08-31 13:40:54:410  848 364 PT Initializing simple targeting cookie, clientId = 07356f47-e8cf-4e40-8cee-e93366e5225f, target group = Server, DNS name = srvexchmb04.xxxyyyzzz.it
    2016-08-31 13:40:54:410  848 364 PT   Server URL = http://susserver.xxxyyyzzz.it/SimpleAuthWebService/SimpleAuth.asmx
    2016-08-31 13:40:54:457  848 364 Report Uploading 1 events using cached cookie, reporting URL = http://susserver.xxxyyyzzz.it/ReportingWebService/ReportingWebService.asmx
    2016-08-31 13:40:54:473  848 364 Report Reporter successfully uploaded 1 events.
    2016-08-31 17:17:47:817  848 79c AU AU setting next sqm report timeout to 2016-09-01 15:17:47
    2016-08-31 17:30:28:972  848 79c AU AU was unable to detect updates for more than 48 hours
    2016-08-31 17:30:33:972  848 890 Report REPORT EVENT: {04E37E67-2A83-46CA-BC5B-C47A890D246F} 2016-08-31 17:30:28:972+0200 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Failure Software Synchronization Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
    2016-08-31 17:30:33:972  848 890 Report CWERReporter finishing event handling. (00000000)

    Any ideas?

    Thanks

    Milena

    Wednesday, August 31, 2016 3:41 PM

Answers

  • Hi,

    I have found the problem!

    Wsus server had not the ammount of memory that it needed.

    The Wsus pool crashed many time because its memory limit. Now it have a limit of 6 GB RAM and all works!

    Best Regards.

    Monday, September 5, 2016 1:01 PM

All replies

  • Hi LFN_Nikita,

    1. Please check the DNS settings, enable the new WSUS client can resolve the WSUS server's FQDN, also check the network connection between them;

    2. If the network connection is well, while the new clients still doesn't report the it, please reset windows update components on it:

    Reset windows update components

    https://support.microsoft.com/en-us/kb/971058

    3. On the old WSUS client with problem, after resetting windows update components, also delete SoftwareDistribution folder:

    1) In cmd, run net stop wuauserv;

    2) Find C:\Windows\SoftwareDistribution, delete it;

    3) In cmd, run net start wuauserv;

    4. New added computers may take a period of time to report to the WSUS server, so please wait around one day, check if the new added WSUS client will report to the WSUS server within one day after doing the above steps.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Thursday, September 1, 2016 6:08 AM
  • Thanks, but DNS are ok. More 200 wsus-client (20 new domain server also) report without problems.

    I have make the reset of windows update component the first day (sorry, I had not write it) and I have repeted them more times.

    Milena.

    Thursday, September 1, 2016 8:07 AM
  • you should check with WSUS ClientDiag tool 
    Thursday, September 1, 2016 8:12 AM
  • I have downloaded Wsus Client Diag but this tool seems work only on 32 bit OS.

    In another thread I have read "I'm assuming you're running a 32-bit server, since you've reported results from the Client Diagnostic Tool (which is a 32-bit only utility)."

    This is the output:

    C:\Windows>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

    GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002

    The system cannot find the file specified.

    Now I'm searching for SolarWinds utility.

    I'll post the result.

    Thursday, September 1, 2016 10:07 AM
  • Hi LFN_Nikita,

    You may also try windows update troubleshooter, it may fix some general issues.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, September 2, 2016 8:21 AM
  • Hi,

    I have found the problem!

    Wsus server had not the ammount of memory that it needed.

    The Wsus pool crashed many time because its memory limit. Now it have a limit of 6 GB RAM and all works!

    Best Regards.

    Monday, September 5, 2016 1:01 PM
  • Hi LFN_Nikita,

    Glad to hear you have solved the issue and thanks for sharing the solution with us. Now, you may mark your solution as answer.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, September 6, 2016 9:46 AM