locked
WSUS console click "Synchronizations" crash console RRS feed

  • Question

  • hi,

    I got problem in WSUS console click "Synchronizations" get crash console, Windows Server 2016, WSUS.

    I try apply wsus-cleanup-updates-v4.ps1 but can't fix.

    It always crash on click "Synchronizations" after loading after 3 minutes, it crash and always loading 72%.

    Regards

    Thanks...KEN

    Monday, July 30, 2018 5:52 AM

Answers

  • Hello KEN,

     

    It looks like there is no problem with your settings of IIS. Please allow me to ask some more questions in order to collect more information.

     

    1. Does this error occur every time when clicking "synchronization"?
    2. Does this error occur when clicking other node?
    3. How often does your WSUS synchronize? Are there too many synchronization entry in history?

     

    And you may try following method to clear the synchronization history and try if it works.

     

    Clearing the Synchronization history in the WSUS console

    https://blogs.technet.microsoft.com/sus/2009/03/04/clearing-the-synchronization-history-in-the-wsus-console/

     

    Look forward to your feedback.

     

    Best Regards,

    Ray Jia

     


    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 lywwing Thursday, August 2, 2018 8:11 AM
    Tuesday, July 31, 2018 3:14 AM

All replies

  • Hello lywwing,

     

    Glad to help.

     

    1. Check if you choose too much product or language in WSUS option.
    2. Increase the WSUSpool, check if it work.

     

    Hope that helps and look forward to your feedback.

     

    Best Regards,

    Ray Jia


    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, July 30, 2018 6:41 AM
  • hi Ray,

    I select Windows 10 prefix production, sliverlight, all office.

    I already had some tuning on IIS as below, but also same problem.

    Queue Length: 25000 from 1000
    Limit Interval (minutes): 15 from 5 
    "Service Unavailable" Response: TcpLevel from HttpLevel 
    Private Memory Limit (KB): 0 from 1843200

    executionTimeout to 02:00:00

    maxRequestLength to 204800

    Any idea?

    Regards

    Thanks...KEN

    Monday, July 30, 2018 8:26 AM
  • Hello KEN,

     

    It looks like there is no problem with your settings of IIS. Please allow me to ask some more questions in order to collect more information.

     

    1. Does this error occur every time when clicking "synchronization"?
    2. Does this error occur when clicking other node?
    3. How often does your WSUS synchronize? Are there too many synchronization entry in history?

     

    And you may try following method to clear the synchronization history and try if it works.

     

    Clearing the Synchronization history in the WSUS console

    https://blogs.technet.microsoft.com/sus/2009/03/04/clearing-the-synchronization-history-in-the-wsus-console/

     

    Look forward to your feedback.

     

    Best Regards,

    Ray Jia

     


    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 lywwing Thursday, August 2, 2018 8:11 AM
    Tuesday, July 31, 2018 3:14 AM
  • hi Ray,

    I am using WID instead of MSSQL.

    1. Yes.

    2. Previous click the node server, it can show the status, but after I run cleanup wizard, then click the node get crash console.

    3. WSUS is new setup, it auto check update every day.

    Regards

    Thanks...KEN

    Tuesday, July 31, 2018 8:16 AM
  • hi Ray,

    I see the WID log as below, it have login fail for user, does it related?

    2018-07-31 18:40:05.10 Server      Microsoft SQL Server 2014 - 12.0.2000.8 (X64) 
    Feb 20 2014 20:04:26 
    Copyright (c) Microsoft Corporation
    Windows Internal Database (64-bit) on Windows NT 6.3 <X64> (Build 14393: ) (Hypervisor)

    2018-07-31 18:40:05.12 Server      UTC adjustment: 8:00
    2018-07-31 18:40:05.13 Server      (c) Microsoft Corporation.
    2018-07-31 18:40:05.13 Server      All rights reserved.
    2018-07-31 18:40:05.13 Server      Server process ID is 3280.
    2018-07-31 18:40:05.13 Server      System Manufacturer: 'Microsoft Corporation', System Model: 'Virtual Machine'.
    2018-07-31 18:40:05.14 Server      Authentication mode is WINDOWS-ONLY.
    2018-07-31 18:40:05.14 Server      Logging SQL Server messages in file 'C:\Windows\WID\Log\error.log'.
    2018-07-31 18:40:05.14 Server      The service account is 'NT SERVICE\MSSQL$MICROSOFT##WID'. This is an informational message; no user action is required.
    2018-07-31 18:40:05.14 Server      Registry startup parameters: 
    -d C:\Windows\WID\Data\master.mdf
    -l C:\Windows\WID\Data\mastlog.ldf
    -e C:\Windows\WID\Log\error.log
    -K
    -T 1617
    -w 65535
    2018-07-31 18:40:05.14 Server      Command Line Startup Parameters:
    -S "MSWIN8.SQLWID"
    -s "MICROSOFT##WID"
    2018-07-31 18:40:05.21 Server      SQL Server detected 1 sockets with 4 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
    2018-07-31 18:40:05.21 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2018-07-31 18:40:05.21 Server      Detected 8189 MB of RAM. This is an informational message; no user action is required.
    2018-07-31 18:40:05.21 Server      Using conventional memory in the memory manager.
    2018-07-31 18:40:05.52 Server      Machine supports memory error recovery. SQL memory protection is enabled to recover from memory corruption.
    2018-07-31 18:40:06.18 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
    2018-07-31 18:40:09.44 Server      Query Store settings initialized with enabled = 1, 
    2018-07-31 18:40:09.67 Server      The maximum number of dedicated administrator connections for this instance is '1'
    2018-07-31 18:40:09.87 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2018-07-31 18:40:09.90 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2018-07-31 18:40:10.00 Server      Software Usage Metrics is disabled.
    2018-07-31 18:40:10.07 Server      CLR version v4.0.30319 loaded.
    2018-07-31 18:40:10.22 spid7s      Starting up database 'master'.
    2018-07-31 18:40:10.61 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2018-07-31 18:40:11.88 spid7s      The password regeneration attempt for SA was successful.
    2018-07-31 18:40:11.94 spid7s      Resource governor reconfiguration succeeded.
    2018-07-31 18:40:11.94 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2018-07-31 18:40:11.96 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2018-07-31 18:40:12.24 spid7s      SQL Trace ID 1 was started by login "sa".
    2018-07-31 18:40:12.30 spid7s      Server name is 'XXXX-WSUS-AP101\MICROSOFT##WID'. This is an informational message only. No user action is required.
    2018-07-31 18:40:12.44 spid12s     Starting up database 'mssqlsystemresource'.
    2018-07-31 18:40:12.44 spid19s     Starting up database 'SUSDB'.
    2018-07-31 18:40:12.44 spid18s     Starting up database 'msdb'.
    2018-07-31 18:40:12.46 spid16s     The service master key regeneration was successful.
    2018-07-31 18:40:12.48 spid16s     Server local connection provider is ready to accept connection on [ \\.\pipe\MICROSOFT##WID\tsql\query ].
    2018-07-31 18:40:12.48 spid16s     Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
    2018-07-31 18:40:12.49 spid12s     The resource database build version is 12.00.2000. This is an informational message only. No user action is required.
    2018-07-31 18:40:12.91 spid12s     Starting up database 'model'.
    2018-07-31 18:40:13.08 spid12s     Clearing tempdb database.
    2018-07-31 18:40:13.39 Logon       Error: 18401, Severity: 14, State: 1.
    2018-07-31 18:40:13.39 Logon       Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: <named pipe>]
    2018-07-31 18:40:13.89 spid12s     Starting up database 'tempdb'.
    2018-07-31 18:40:16.70 spid21s     The Service Broker endpoint is in disabled or stopped state.
    2018-07-31 18:40:16.70 spid21s     The Database Mirroring endpoint is in disabled or stopped state.
    2018-07-31 18:40:16.81 spid21s     Service Broker manager has started.
    2018-07-31 18:40:18.76 Logon       Error: 18401, Severity: 14, State: 1.
    2018-07-31 18:40:18.76 Logon       Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: <named pipe>]
    2018-07-31 18:40:18.98 spid7s      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2018-07-31 18:40:19.02 spid7s      Recovery is complete. This is an informational message only. No user action is required.
    2018-07-31 18:40:28.84 spid51      Starting up database 'SUSDB'.

    Regards

    Thanks...KEN

    Tuesday, July 31, 2018 12:45 PM
  • Hi Ken,

    It seems to be Authentication Issue, login failed for NT AUTHORITY\NETWORK SERVICE

    Please run the command in elevated mode in order:

    %drive%\Program Files\Update Services\Tools>wsusutil.exe reset

    %drive%\Program Files\Update Services\Tools>wsusutil.exe postinstall /servicing

    Post running the commands, please reboot

    Regards,

    Praveen Kumar Shaw


    Please remember to mark the replies as answers if they help.
    Tuesday, July 31, 2018 1:44 PM
  • hi Ray,

    With your suggestion to remove history record in WID, the crash if click "Synchronizations" is solved.

    But click "Security Updates" with filter status to "Any" the WSUS console also crash, is it the WID DB still have problem?

    Regards

    Thanks...KEN

    Wednesday, August 1, 2018 12:07 PM
  • hi Ray,

    After delete wsus of MMC cache file, it can show "Security Updates" with "Any" view, but it still crash if click "All Updates" with "Any" view. Any idea?

    Seems Windows Server 2016 WSUS seems have many issue then WS2012R2.

    Can we identify the WID or MMC console problem?

    Regards

    Thanks...KEN

    Thursday, August 2, 2018 9:21 AM
  • hi Ray,

    After delete wsus of MMC cache file, it can show "Security Updates" with "Any" view, but it still crash if click "All Updates" with "Any" view. Any idea?

    Seems Windows Server 2016 WSUS seems have many issue then WS2012R2.

    Can we identify the WID or MMC console problem?

    Regards

    Thanks...KEN

    Are you performing the proper WSUS maintenance including but not limited to running the Server Cleanup Wizard (SCW), declining superseded updates, running the SQL Indexing script, etc.?

    https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-8-wsus-server-maintenance/

    Also check out Sterling T's response on this thread to make sure you don't have a bad Unicode character in your database's computer information.

    https://social.technet.microsoft.com/Forums/ie/en-US/90dc15d3-c498-42b8-b36a-bd29be35cf99/wsus-console-unexpected-error-when-choosing-all-computers-folder?forum=winserverwsus


    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Monday, August 6, 2018 4:18 AM
  • Hi lywing,

    In your above settings the "Private Memory Limit (KB): 0 from 1843200" (This should be "Zero" , let it grow on its own, do not limit it).

    Also, WSUS should not show any errors on the below settings:

    1. WsusPool should be started and it should nt be stopping frequently.

    2. IIS is able to resolve the WSUS website from IIS manager, it means when u try to browser the WSUS website , it should open that without any errors.

    3. if your are using certificates for authentication than check SSL settings are not creating any  errors

    Regards,

    Naren Nadh





    • Edited by Naren.nadh Thursday, July 9, 2020 11:56 AM
    Tuesday, July 7, 2020 9:41 AM