locked
WSUS on W2K12R2 Getting WindowsUpdateFailure3, Event ID 1001 and error code 80244018 RRS feed

  • Question

  • Hello All,

    I have a brand new WSUS server running on W2K12R2.  It's completed it's initial sync, I've approved all valid updates and have configured group policy to point all clients to the WSUS Server using port 8530.  I can Telnet from a client to the server port 8530 and I can Telnet from the server back to the client on ports > 49152.  I can also connect to the WSUS server via browser at http://wsusservername.domain.com:8530  I don't get an error just a blank page, but it connects.  

    Being that I can connect to the server:port via several means I don't believe it to be a network, firewall or proxy issue.  I have turned off the Firewall and that didn't make any difference.  The WSUS server and the clients are all on the same network and the proxy configuration bypasses the proxy for all local addresses.

    As I said this is a brand new WSUS server.  All of the clients would be reporting in for the first time and as of yet don't show in the console as reporting in.  

    Here are the events from the windowsupdatelog for the last check for updates:

    2017-04-20 17:45:15:013 912 71c IdleTmr Incremented idle timer priority operation counter to 1
    2017-04-20 17:45:20:364 912 71c AU Triggering AU detection through DetectNow API
    2017-04-20 17:45:20:365 912 71c AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-download notify} added to AU services list
    2017-04-20 17:45:20:365 912 71c AU Triggering Online detection (interactive)
    2017-04-20 17:45:20:365 912 71c AU Adding timer: 
    2017-04-20 17:45:20:365 912 71c AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2017-04-20 17:45:20, not idle-only, not network-only
    2017-04-20 17:45:20:377 912 b14 AU #############
    2017-04-20 17:45:20:377 912 b14 AU ## START ##  AU: Search for updates
    2017-04-20 17:45:20:377 912 b14 AU #########
    2017-04-20 17:45:20:377 912 b14 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Pre-download notify} added to AU services list
    2017-04-20 17:45:20:377 912 b14 IdleTmr WU operation (CSearchCall::Init ID 9) started; operation # 86; does use network; is not at background priority
    2017-04-20 17:45:20:377 912 b14 IdleTmr Incremented idle timer priority operation counter to 2
    2017-04-20 17:45:20:377 912 b14 Agent *** START ***  Queueing Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 9]
    2017-04-20 17:45:20:377 912 b14 AU <<## SUBMITTED ## AU: Search for updates  [CallId = {5AE5AF6E-4EB9-4B9A-8591-BAA9CCE79956} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2017-04-20 17:45:20:378 912 d20 Agent ***  END  ***  Queueing Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 9]
    2017-04-20 17:45:20:378 912 d20 Agent *************
    2017-04-20 17:45:20:378 912 d20 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 9]
    2017-04-20 17:45:20:378 912 d20 Agent *********
    2017-04-20 17:45:20:378 912 d20 Agent  * Online = Yes; Ignore download priority = No
    2017-04-20 17:45:20:378 912 d20 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"
    2017-04-20 17:45:20:378 912 d20 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2017-04-20 17:45:20:378 912 d20 Agent  * Search Scope = {Machine & All Users}
    2017-04-20 17:45:20:378 912 d20 Agent  * Caller SID for Applicability: S-1-5-21-2086980656-2155760874-123708652-1120
    2017-04-20 17:45:20:378 912 d20 Agent  * RegisterService is set
    2017-04-20 17:45:20:378 912 d20 EP Got WSUS Client/Server URL: "http://ab-corp-wsus01.qcentive.corp:8530/ClientWebService/client.asmx"
    2017-04-20 17:45:20:384 912 d20 Setup Checking for agent SelfUpdate
    2017-04-20 17:45:20:384 912 d20 Setup Client version: Core: 7.9.9600.18628  Aux: 7.9.9600.18628
    2017-04-20 17:45:20:384 912 d20 EP Got WSUS SelfUpdate URL: "http://ab-corp-wsus01.qcentive.corp:8530/selfupdate"
    2017-04-20 17:45:20:410 912 d20 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190193
    2017-04-20 17:45:20:410 912 d20 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190193
    2017-04-20 17:45:20:410 912 d20 Misc WARNING: DownloadFileInternal failed for http://ab-corp-wsus01.qcentive.corp:8530/selfupdate/wuident.cab: error 0x80190193
    2017-04-20 17:45:20:410 912 d20 Setup FATAL: DownloadCab failed, err = 0x80190193
    2017-04-20 17:45:20:410 912 d20 Setup WARNING: SelfUpdate check failed to download package information, err = 0x80244018
    2017-04-20 17:45:20:410 912 d20 Setup FATAL: SelfUpdate check failed, err = 0x80244018
    2017-04-20 17:45:20:410 912 d20 Agent  * WARNING: Skipping scan, self-update check returned 0x80244018
    2017-04-20 17:45:20:411 912 d20 Agent  * WARNING: Exit code = 0x80244018
    2017-04-20 17:45:20:411 912 d20 Agent *********
    2017-04-20 17:45:20:411 912 d20 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdatesWuApp  Id = 9]
    2017-04-20 17:45:20:411 912 d20 Agent *************
    2017-04-20 17:45:20:411 912 d20 Agent WARNING: WU client failed Searching for update with error 0x80244018
    2017-04-20 17:45:20:411 912 d20 IdleTmr WU operation (CSearchCall::Init ID 9, operation # 86) stopped; does use network; is not at background priority
    2017-04-20 17:45:20:411 912 d20 IdleTmr Decremented idle timer priority operation counter to 1
    2017-04-20 17:45:20:411 912 5fc AU >>##  RESUMED  ## AU: Search for updates [CallId = {5AE5AF6E-4EB9-4B9A-8591-BAA9CCE79956} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2017-04-20 17:45:20:411 912 5fc AU  # WARNING: Search callback failed, result = 0x80244018
    2017-04-20 17:45:20:411 912 5fc AU #########
    2017-04-20 17:45:20:411 912 5fc AU ##  END  ##  AU: Search for updates  [CallId = {5AE5AF6E-4EB9-4B9A-8591-BAA9CCE79956} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
    2017-04-20 17:45:20:411 912 5fc AU #############
    2017-04-20 17:45:20:411 912 5fc AU All AU searches complete.
    2017-04-20 17:45:20:411 912 5fc AU  # WARNING: Failed to find updates with error code 80244018
    2017-04-20 17:45:20:411 912 5fc AU AU setting next detection timeout to 2017-04-20 22:45:20
    2017-04-20 17:45:20:411 912 5fc AU Adding timer: 
    2017-04-20 17:45:20:411 912 5fc AU    Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2017-04-20 22:45:20, not idle-only, not network-only
    2017-04-20 17:45:20:412 912 5fc AU  # Publishing WNF Per user update count event Count: 0 SID {S-1-5-21-3526837482-2081308648-1563589271-500} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
    2017-04-20 17:45:20:412 912 5fc AU  # Publishing WNF Per user update count event Count: 0 SID {S-1-5-21-2086980656-2155760874-123708652-1120} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
    2017-04-20 17:45:20:413 912 5fc AU Currently AUX is enabled - so not show any WU Upgrade notifications.
    2017-04-20 17:45:20:413 912 5fc AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2017-04-20 17:45:20:414 912 5fc AU WARNING: Failed to get Network Cost info from NLM, assuming network is NOT metered, error = 0x80240037
    2017-04-20 17:45:25:410 912 7c8 Report REPORT EVENT: {1761BD9D-8389-4A95-8175-AC19B444B18F} 2017-04-20 17:45:20:410-0000 1 148 [AGENT_DETECTION_FAILED] 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80244018 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80244018.
    2017-04-20 17:45:25:410 912 7c8 Report REPORT EVENT: {6072ED49-15A2-4FB6-B837-3965C18EC327} 2017-04-20 17:45:20:411-0000 1 148 [AGENT_DETECTION_FAILED] 101 {00000000-0000-0000-0000-000000000000} 0 80244018 AutomaticUpdatesWuApp Failure Software Synchronization Windows Update Client failed to detect with error 0x80244018.
    2017-04-20 17:45:25:410 912 7c8 Report WARNING: Failed to get ProtocolVersion: 8024043d
    2017-04-20 17:45:25:410 912 7c8 Report WARNING: Failed to get ProtocolVersion: 8024043d
    2017-04-20 17:45:25:412 912 7c8 Report CWERReporter::HandleEvents - WER report upload completed with WER status 0x8 (hr=0)
    2017-04-20 17:45:25:412 912 7c8 Report WER Report sent: 7.9.9600.18628 0x80244018(0) D67661EB-2423-451D-BF5D-13199E37DF28 Scan 1 0 SelfUpdate {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2017-04-20 17:45:25:414 912 7c8 Report CWERReporter::HandleEvents - WER report upload completed with WER status 0x8 (hr=0)
    2017-04-20 17:45:25:414 912 7c8 Report WER Report sent: 7.9.9600.18628 0x80244018(0) 00000000-0000-0000-0000-000000000000 Scan 0 1 AutomaticUpdatesWuApp {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2017-04-20 17:45:25:414 912 7c8 Report CWERReporter finished handling 2 events. (00000000)

    Any thoughts would be greatly appreciated.  I have not been able to find anything relevant to fix this problem.  Thank you!

    Bill

    Thursday, April 20, 2017 5:48 PM

Answers

  • Hi lamBillG,

    Based on my understanding, WSUS clients could show up in the WSUS server while unable to report to the WSUS server.

    Please do the following things, check what is the result after then:

    1. Check what is the version of the WSUS server, if the WSUS server haven't installed KB3095113 and KB3159706(with manual steps), please install the two KBs;

    2. Please run Server Cleanup Wizard on the WSUS server, if it still not work, also re-index WSUS database:

    https://technet.microsoft.com/en-us/library/dd939795(v=ws.10).aspx

    3. On the clients that do not report, please reset windows update components:

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

    4. After reset, run wuauclt /detect in cmd on clients, check if they will report to the WSUS server later;

    5. If it still not work, please check the AU settings in registry keys on the clients which locates in HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU, check if "NoAutoUpdate" is "0" and "UseWUServer" is "1".

    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.

    • Marked as answer by IamBillG Tuesday, April 25, 2017 3:19 PM
    Friday, April 21, 2017 6:11 AM
  • Hi lambillG,

    On WSUS 2012 R2, we may use the following method to reindex WSUS database:

    1.Download and install the following tools:

    Microsoft Command Line Utilities 11 for SQL Server:

    https://www.microsoft.com/en-us/download/details.aspx?id=36433

    ODBC driver 11 for SQL:

    https://www.microsoft.com/en-us/download/details.aspx?id=36434

    2. In CMD, direct to SQLCMD.exe path using command:

    cd C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn

     3. Cope the script and store it locally:

    https://gallery.technet.microsoft.com/scriptcenter/6f8cde49-5c52-4abd-9820-f1d270ddea61#content

    4. In CMD, run the following command:

    SQLCMD -E -S np:\\.\pipe\MICROSOFT##WID\tsql\query -i <script location>

    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.

    • Marked as answer by IamBillG Tuesday, April 25, 2017 3:19 PM
    Monday, April 24, 2017 7:46 AM

All replies

  • Hi lamBillG,

    Based on my understanding, WSUS clients could show up in the WSUS server while unable to report to the WSUS server.

    Please do the following things, check what is the result after then:

    1. Check what is the version of the WSUS server, if the WSUS server haven't installed KB3095113 and KB3159706(with manual steps), please install the two KBs;

    2. Please run Server Cleanup Wizard on the WSUS server, if it still not work, also re-index WSUS database:

    https://technet.microsoft.com/en-us/library/dd939795(v=ws.10).aspx

    3. On the clients that do not report, please reset windows update components:

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

    4. After reset, run wuauclt /detect in cmd on clients, check if they will report to the WSUS server later;

    5. If it still not work, please check the AU settings in registry keys on the clients which locates in HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU, check if "NoAutoUpdate" is "0" and "UseWUServer" is "1".

    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.

    • Marked as answer by IamBillG Tuesday, April 25, 2017 3:19 PM
    Friday, April 21, 2017 6:11 AM
  • Hi Anne,

    Thank you for the assistance.  I have done the following and am stuck at re-indexing the WSUS database.  I am using the Windows Internal Database but I think the SQL CMD version that I was able to find wants to use an MSSQL database?  Here is what has been done so far:

    1. Server Version - 6.3.9600.18324
    KB3095113 was not installed.
    KB3159706 was installed.  Installed it.

    2. Ran Server Cleanup Wizard - Still not working, error 80244018

    3. Re-index WSUS Database.  Installed SQLCMD Utility version 13.1,  had to install MSODBC13.1 for SQL to get SQLCMD to install.

    Ran  C:\Windows\system32>sqlcmd -S np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query -i c:\
    WsusDBMaintenance.sql  Received the following error.

    Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Named Pipes Provider: C
    ould not open a connection to SQL Server [2]. .
    Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login timeout expired.
    Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : A network-related or in
    stance-specific error has occurred while establishing a connection to SQL Server
    . Server is not found or not accessible. Check if instance name is correct and i
    f SQL Server is configured to allow remote connections. For more information see
     SQL Server Books Online..

    C:\Windows\system32>

    Thank you!

    Bill (IamBillG)

    Saturday, April 22, 2017 11:59 PM
  • Hi lambillG,

    On WSUS 2012 R2, we may use the following method to reindex WSUS database:

    1.Download and install the following tools:

    Microsoft Command Line Utilities 11 for SQL Server:

    https://www.microsoft.com/en-us/download/details.aspx?id=36433

    ODBC driver 11 for SQL:

    https://www.microsoft.com/en-us/download/details.aspx?id=36434

    2. In CMD, direct to SQLCMD.exe path using command:

    cd C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn

     3. Cope the script and store it locally:

    https://gallery.technet.microsoft.com/scriptcenter/6f8cde49-5c52-4abd-9820-f1d270ddea61#content

    4. In CMD, run the following command:

    SQLCMD -E -S np:\\.\pipe\MICROSOFT##WID\tsql\query -i <script location>

    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.

    • Marked as answer by IamBillG Tuesday, April 25, 2017 3:19 PM
    Monday, April 24, 2017 7:46 AM
  • Thank you Anne for all of your help.  This worked and the server and clients are all working properly now.  I really appreciate all of your assistance.  Have a great day!

    Kind Regards,

    Bill

    Tuesday, April 25, 2017 3:20 PM
  • Hi lamBillG,

    You are welcome and it's glad to hear it works.

    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, April 26, 2017 1:37 AM