locked
WSUS Servers - Issues RRS feed

  • Question

  • I have 400 computers along with 21 servers that I need to make sure stay updated.  I decided to use WSUS.  I installed in on Windows Server 2008 r2 / 32bit computer.  All the computers initially except 180 connected to the WSUS server and reported.  I set up automatic updates to download and update at 2:00 pm on a weekday where the company closes early.  The first day half of the computers got updated.  Now I am looking to do this again and I see that I have 56 computers that have not  yet reported!!  I have my GPO set up in my domain server to search every 10 hours and I also have at least 100 that have not connected in 7 days.  I really need some help getting this fixed.  I know I have some clients that have the 0x8024400E error when trying to search for updates, so they are failing.  I can't seem to find a reason or a fix for this error.  I have did the stop the service and deleting the softwaredistribution folder and restarting, still  not working.

    I really need some help here.

    Tuesday, November 8, 2016 9:14 PM

Answers

  • hi All,

    I checked the software distribution log file and as I was expecting there are some issues on this WSUS server. please check my comments below :

    - looking from most recent and backward seems there is a clear internal server error we are getting at the "reporting web service" :

    ===========================================

    2016-11-10 14:31:06.806 UTC Warning w3wp.35 SoapUtilities.CreateException ThrowException: actor =ID=101f46f6-bc60-4256-b8fc-3d7cba6c3ceb, ErrorCode=InternalServerError, Message=, Client=96114d73-a986-4145-8afe-59ed0e59e7ee
    2016-11-10 14:31:52.242 UTC Warning w3wp.29 SoapUtilities.CreateException ThrowException: actor = ID=e09b9985-0e0f-45b4-bdd9-4e643e45b94b, ErrorCode=ConfigChanged, Message=, Client=283067e5-7b43-4ec0-8ce5-266ac08af211
    2016-11-10 14:31:52.242 UTC Error w3wp.29 WebService.ReportEventBatch Exception occured in ReportEventBatch: Fault occurred
       at Microsoft.UpdateServices.Internal.Reporting.WebService.ReportEventBatch(Cookie cookie, DateTime clientTime, ReportingEvent[] eventBatch)

    ===========================================

    - also I can see some storage issue on this WSUS server!!!
    ==========================================

    2016-11-10 14:31:06.806 UTC Error w3wp.35 ClientImplementation.SyncUpdates System.ComponentModel.Win32Exception: Not enough storage is available to complete this operation

    ==========================================

    - some more errors indicating WSUS server internal issue :

    ===========================================
    2016-11-10 14:31:06.791 UTC Error w3wp.35 CabUtilities.ExpandMemoryCabToString ExpandMemoryCab failed with error code 2147942414
       at Microsoft.UpdateServices.Internal.CabUtilities.ExpandMemoryCabToString(Byte[] src)

    ===========================================

    - even WSUS is not able to sync updates due to storage issue :

    ============================================

    2016-11-10 14:25:45.322 UTC Error w3wp.5 ClientImplementation.SyncUpdates System.ComponentModel.Win32Exception: Not enough storage is available to complete this operation

    ============================================

    so I didn't go further but till this point I see you have 2 main things:

    a) WSUS server is having storage issue.. may be Harddisk is out of diskspace

    b) WSUS is having internal reporting service issue. could be related to same disk space issue or something else. by the way the disk space issue could cause WSUS database to be corrupt that will need to be examined by some database tools if you want to go further deep.

    so as I said above I believe you need to look into WSUS server first. make sure there is available disk space to sync updates.. open IIS console and make sure all webservices are started and working fine. basically open eventvwr and make sure WSUS is not throwing errors or high level warnings also.

    hope this helps

    Mahmoud

    • Proposed as answer by mahelsay Saturday, November 12, 2016 5:24 AM
    • Marked as answer by Salongec Tuesday, November 15, 2016 3:00 PM
    Friday, November 11, 2016 9:55 AM

All replies

  • Hi Salongec,

    1. What is the version of your WSUS server, if it's not the latest version of WSUS 3.0 SP2, I would recommend you install KB2938066 to upgrade your WSUS server. (If you have win10 clients, then you'd use WSUS 4.0, install on server 2012(R2) or Server 2016.)

    WSUS version:
    WSUS 3.0 (SP2): Build 3.2.7600.226
    WSUS 3.0 (SP2) + KB2720211: Build 3.2.7600.251
    WSUS 3.0 (SP2) + KB2734608: Build 3.2.7600.256
    WSUS 3.0 (SP2) + KB2828185: Build 3.2.7600.262
    WSUS 3.0 (SP2) + KB2938066: Build 3.2.7600.274

    2. On the clients do not report to the WSUS server, please do the following things:

    1) Run windows update troubleshooter, it may help solve general update issues;

    2) Reset windows update components:

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

    3) Check the version of WUA, if it not the latest version, please upgrade it:

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

    4) Also check network connection between WSUS server and WSUS clients.

    Best Regards,

    Anne


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

    Wednesday, November 9, 2016 2:40 AM
  • hi there,

    i'd recommend following:

    1- on one of the affected servers restart wuauserv service.  (to set a marker in the log file and please write down exact time in HH:MM)

    2- check for updates from control panel

    3-send me the whole C:\windows\windowsupdate.log file

    Thanks

    Mahmoud

    Microsoft CTS

    Wednesday, November 9, 2016 6:17 AM
  • Okay, I will try this.  I have version WSUS 3.0 (SP2) Build 3.2.7600.226  I will work on one computer since most of the computers not registered are across the state and not accessible to me that easily.  I was hoping the issue may be with the WSUS server since I can work on that from where I am.
    
    Wednesday, November 9, 2016 1:20 PM
  • 
    
    
    how do I attach a file?
    Wednesday, November 9, 2016 2:11 PM

  • 2016-11-09 08:35:09:565  956 1784 AU ## START ##  AU: Search for updates
    2016-11-09 08:35:09:565  956 1784 AU #########
    2016-11-09 08:35:09:565  956 1784 AU <<## SUBMITTED ## AU: Search for updates [CallId = {9FD461A9-9C4E-4A42-8F08-A357C39BBD55}]
    2016-11-09 08:35:09:565  956 b0c Agent *************
    2016-11-09 08:35:09:565  956 b0c Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-11-09 08:35:09:565  956 b0c Agent *********
    2016-11-09 08:35:09:565  956 b0c Agent   * Online = Yes; Ignore download priority = No
    2016-11-09 08:35:09:565  956 b0c 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-11-09 08:35:09:565  956 b0c Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2016-11-09 08:35:09:565  956 b0c Agent   * Search Scope = {Machine}
    2016-11-09 08:35:09:565  956 b0c Setup Checking for agent SelfUpdate
    2016-11-09 08:35:09:565  956 b0c Setup Client version: Core: 7.6.7600.320  Aux: 7.6.7600.320
    2016-11-09 08:35:09:580  956 b0c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2016-11-09 08:35:09:596  956 b0c Misc  Microsoft signed: NA
    2016-11-09 08:35:09:596  956 b0c Misc WARNING: Cab does not contain correct inner CAB file.
    2016-11-09 08:35:09:596  956 b0c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab with dwProvFlags 0x00000080:
    2016-11-09 08:35:09:596  956 b0c Misc  Microsoft signed: NA
    2016-11-09 08:35:09:596  956 b0c Setup Wuident for the managed service is valid but not quorum-signed. Skipping selfupdate.
    2016-11-09 08:35:09:596  956 b0c Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
    2016-11-09 08:35:09:596  956 b0c Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2016-11-09 08:35:09:658  956 b0c PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2016-11-09 08:35:09:658  956 b0c PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://ECWFAX:8530/ClientWebService/client.asmx
    2016-11-09 08:35:10:953  956 b0c PT WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
    2016-11-09 08:35:10:953  956 b0c PT WARNING: SOAP Fault: 0x000190
    2016-11-09 08:35:10:953  956 b0c PT WARNING:     faultstring:Fault occurred
    2016-11-09 08:35:10:953  956 b0c PT WARNING:     ErrorCode:InternalServerError(5)
    2016-11-09 08:35:10:953  956 b0c PT WARNING:     Message:(null)
    2016-11-09 08:35:10:953  956 b0c PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2016-11-09 08:35:10:953  956 b0c PT WARNING:     ID:500e6168-9947-488e-b3ec-dc8ac77ae58e
    2016-11-09 08:35:10:953  956 b0c PT WARNING: PTError: 0x8024400e
    2016-11-09 08:35:10:953  956 b0c PT WARNING: SyncUpdates_WithRecovery failed.: 0x8024400e
    2016-11-09 08:35:10:953  956 b0c PT WARNING: Sync of Updates: 0x8024400e
    2016-11-09 08:35:10:953  956 b0c PT WARNING: SyncServerUpdatesInternal failed: 0x8024400e
    2016-11-09 08:35:10:953  956 b0c Agent   * WARNING: Failed to synchronize, error = 0x8024400E
    2016-11-09 08:35:10:953  956 b0c Agent   * WARNING: Exit code = 0x8024400E
    2016-11-09 08:35:10:953  956 b0c Agent *********
    2016-11-09 08:35:10:953  956 b0c Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2016-11-09 08:35:10:953  956 b0c Agent *************
    2016-11-09 08:35:10:953  956 b0c Agent WARNING: WU client failed Searching for update with error 0x8024400e
    2016-11-09 08:35:10:953  956 1794 AU >>##  RESUMED  ## AU: Search for updates [CallId = {9FD461A9-9C4E-4A42-8F08-A357C39BBD55}]
    2016-11-09 08:35:10:953  956 1794 AU   # WARNING: Search callback failed, result = 0x8024400E
    2016-11-09 08:35:10:953  956 1794 AU   # WARNING: Failed to find updates with error code 8024400E
    2016-11-09 08:35:10:953  956 1794 AU #########
    2016-11-09 08:35:10:953  956 1794 AU ##  END  ##  AU: Search for updates [CallId = {9FD461A9-9C4E-4A42-8F08-A357C39BBD55}]
    2016-11-09 08:35:10:953  956 1794 AU #############
    2016-11-09 08:35:10:953  956 1794 AU Successfully wrote event for AU health state:0
    2016-11-09 08:35:10:953  956 1794 AU AU setting next detection timeout to 2016-11-09 18:35:10
    2016-11-09 08:35:10:953  956 1794 AU Setting AU scheduled install time to 2016-11-10 00:00:00
    2016-11-09 08:35:10:953  956 1794 AU Successfully wrote event for AU health state:0
    2016-11-09 08:35:10:953  956 1794 AU Successfully wrote event for AU health state:0
    2016-11-09 08:35:15:961  956 b0c Report REPORT EVENT: {AF077710-6E6E-405D-8D8A-DB3DA0FB67E4} 2016-11-09 08:35:10:953-0500 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400e AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x8024400e.
    2016-11-09 08:35:15:961  956 b0c Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2016-11-09 08:35:15:961  956 b0c Report WER Report sent: 7.6.7600.320 0x8024400e 00000000-0000-0000-0000-000000000000 Scan 101 Managed
    2016-11-09 08:35:15:961  956 b0c Report CWERReporter finishing event handling. (00000000)
    Wednesday, November 9, 2016 3:38 PM
  • hi Salongec,

    that log you copied and pasted above is not complete actually, however

    apparently update synchronizations with WSUS server is failing with error 0x8024400e.

    that error means:

    =================

    # for hex 0x8024400e / decimal -2145107954
      WU_E_PT_SOAP_SERVER                                            wuerror.h
    # Same as SOAP_E_SERVER - The SOAP message could not be
    # processed due to a server error; resend later.
    # 1 matches found for "0x8024400e"

    =================

    seems there are server issues here?

    anyway i'd recommend following:

    1- make sure WSUS server is fully updated itself to latest updates

    2- on one of the affected servers restart wuauserv service.  (to set a marker in the log file and please write down exact time in HH:MM)

    3- check for updates from control panel

    4-send me the whole C:\windows\windowsupdate.log file at mahelsay@gmail.com

    Thanks

    Mahmoud

    Wednesday, November 9, 2016 6:09 PM
  • Emailing now.
    Wednesday, November 9, 2016 8:37 PM
  • Hi Salongec,

    Have you also tried all the suggestions in my last reply? What is the result?

    Welcome to feed back if you get any progress.

    Best Regards,

    Anne


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

    Thursday, November 10, 2016 7:31 AM
  • HI all, due to technical issue I couldn't paste my reply here. I sent it to your email. feel free to check and revert back.

    Thanks

    Mahmoud

    Thursday, November 10, 2016 9:11 AM
  • hi All,

    I checked the software distribution log file and as I was expecting there are some issues on this WSUS server. please check my comments below :

    - looking from most recent and backward seems there is a clear internal server error we are getting at the "reporting web service" :

    ===========================================

    2016-11-10 14:31:06.806 UTC Warning w3wp.35 SoapUtilities.CreateException ThrowException: actor =ID=101f46f6-bc60-4256-b8fc-3d7cba6c3ceb, ErrorCode=InternalServerError, Message=, Client=96114d73-a986-4145-8afe-59ed0e59e7ee
    2016-11-10 14:31:52.242 UTC Warning w3wp.29 SoapUtilities.CreateException ThrowException: actor = ID=e09b9985-0e0f-45b4-bdd9-4e643e45b94b, ErrorCode=ConfigChanged, Message=, Client=283067e5-7b43-4ec0-8ce5-266ac08af211
    2016-11-10 14:31:52.242 UTC Error w3wp.29 WebService.ReportEventBatch Exception occured in ReportEventBatch: Fault occurred
       at Microsoft.UpdateServices.Internal.Reporting.WebService.ReportEventBatch(Cookie cookie, DateTime clientTime, ReportingEvent[] eventBatch)

    ===========================================

    - also I can see some storage issue on this WSUS server!!!
    ==========================================

    2016-11-10 14:31:06.806 UTC Error w3wp.35 ClientImplementation.SyncUpdates System.ComponentModel.Win32Exception: Not enough storage is available to complete this operation

    ==========================================

    - some more errors indicating WSUS server internal issue :

    ===========================================
    2016-11-10 14:31:06.791 UTC Error w3wp.35 CabUtilities.ExpandMemoryCabToString ExpandMemoryCab failed with error code 2147942414
       at Microsoft.UpdateServices.Internal.CabUtilities.ExpandMemoryCabToString(Byte[] src)

    ===========================================

    - even WSUS is not able to sync updates due to storage issue :

    ============================================

    2016-11-10 14:25:45.322 UTC Error w3wp.5 ClientImplementation.SyncUpdates System.ComponentModel.Win32Exception: Not enough storage is available to complete this operation

    ============================================

    so I didn't go further but till this point I see you have 2 main things:

    a) WSUS server is having storage issue.. may be Harddisk is out of diskspace

    b) WSUS is having internal reporting service issue. could be related to same disk space issue or something else. by the way the disk space issue could cause WSUS database to be corrupt that will need to be examined by some database tools if you want to go further deep.

    so as I said above I believe you need to look into WSUS server first. make sure there is available disk space to sync updates.. open IIS console and make sure all webservices are started and working fine. basically open eventvwr and make sure WSUS is not throwing errors or high level warnings also.

    hope this helps

    Mahmoud

    • Proposed as answer by mahelsay Saturday, November 12, 2016 5:24 AM
    • Marked as answer by Salongec Tuesday, November 15, 2016 3:00 PM
    Friday, November 11, 2016 9:55 AM
  • Any updates regarding above comments?

    Thanks

    Mahmoud


    Thanks Mahmoud

    Monday, November 14, 2016 6:46 AM