Issue:
When attempting to bring up the synchronization history, the window would freeze at Loading synchronization history: 0% complete. and eventually prompted Reset Server Node.
Solution:
1. During the initial synchronization, make sure that your server has sufficient memory. I set my VM to 64GB RAM just in case, and eventually found that the RAM usage climbed up all the way to over 13GB to finish. After the initial synchronization is finished, the subsequent synchronizations wouldn’t use that much RAM anymore, so it’s safe to tune down the VM’s RAM.
2. You’ll also need to set the following values in IIS Manager for the initial synchronization to finish without errors.
Go to IIS Manager - Application Pools - WsusPool - Advanced Settings and modify the following fields:
Queue Length: 25000
Limit Interval (minutes): 15
"Service Unavailable" Response: TcpLevel
Failure Interval (minutes): 30
Maximum Failures: 60
Private Memory Limit (KB): 03. I also needed to delete the synchronization history from the SUSDB to be able to sync again, I think it was because my initial sync failed due to insufficient RAM. To delete the sync history from SUSDB, you will need Microsoft SSMS (Run As Administrator) and connect to
\\.\pipe\MICROSOFT##WID\tsql\query
and run the following commands:
USE SUSDB
GO
DELETE FROM tbEventInstance WHERE EventNamespaceID= '2' AND EVENTID IN ('381','382','384','386','387','389')4. The Microsoft ReportViewer and Microsoft System CLR Types for SQL Server 2012 will need to be installed to view update error logs.