Problem with patches and synchronizations RRS feed

  • Question

  • Hello --

    I have completed the installation of WSUS 6.3 on a Windows 2012R2 server. The system is a virtual server with 300 gigabytes of disk space, and sixteen, 16, gigabytes of memory. I followed the procedure that is outlined in the Deploy Windows Server Update Services document, and used the default settings. 

    I am at a point where I have done the initial synchronization, and it appears to have completed successfully. However, I am running into various problems.

    When I check the Synchonizations list, or attempt to Approve the downloaded patches, the system hangs and eventually times out with the Error: Connection Error message. The text of the error message is the following:

    The WSUS administration console was unable to connect to the WSUS Server via the remote API. 

    Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

    System.Net.WebException -- The operation has timed out


    Stack Trace:
       at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
       at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
       at Microsoft.UpdateServices.Internal.DatabaseAccess.ApiRemotingCompressionProxy.GetWebResponse(WebRequest webRequest)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at Microsoft.UpdateServices.Internal.ApiRemoting.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, Int32 publicationState)
       at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPSearchUpdates(String updateScopeXml, String preferredCulture, ExtendedPublicationState publicationState)
       at Microsoft.UpdateServices.Internal.BaseApi.Update.SearchUpdates(UpdateScope searchScope, ExtendedPublicationState publicationState, UpdateServer updateServer)
       at Microsoft.UpdateServices.UI.AdminApiAccess.UpdateManager.GetUpdates(ExtendedUpdateScope filter)
       at Microsoft.UpdateServices.UI.AdminApiAccess.WsusSynchronizationInfo.InitializeDerivedProperties()
       at Microsoft.UpdateServices.UI.SnapIn.Pages.SyncResultsListPage.GetSyncInfoRow(WsusSynchronizationInfo syncInfo)
       at Microsoft.UpdateServices.UI.SnapIn.Pages.SyncResultsListPage.GetListRows()


    I confirmed the IIS server is running. When I did the installation of the WSUS, the database that I used was the one that was already selected in the Installation Wizard. There is a SQL Server Windows NT - 64 bit (Windows Internal Database) running on the system. 

    The process is at or near 100% CPU utilization nearly at all times. 

    There are currently 14104 security updates, and 3071 critical updates waiting to be approved.  

    The troubleshooting that I have done so far is to go into the IIS Manager, and modify the Private Memory Limit (KB) setting to 0, in order to have no limit set, and after that reboot the server. So far, nothing has worked. 

    Does anyone have insights into how this can be corrected?


    • Edited by kaplan71 Thursday, January 16, 2020 8:14 PM
    Thursday, January 16, 2020 3:40 PM

All replies

  • I am at a point where I have done the initial synchronization, and it appears to have completed successfully. However, I am running into various problems.


    There are currently 14104 security updates, and 3071 critical updates waiting to be approved.  


    I noticed that this seems to be happening during the initial synchronization. This is likely to happen if you have selected more products and classifications in the initialization wizard. First make sure that the "Drivers" classification is not selected. Second, consider reducing the number of selected products.

    If adjusting the dedicated memory of WSUPool in IIS does not solve this problem, I suggest that you consider completely removing the current WSUS role and adding it again. Please refer to the steps mentioned in this thread for complete removal steps: "How to completely remove old wsus settings - trying for a clean install."

    Reply back with the results would be happy to help.


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

    Friday, January 17, 2020 2:02 AM
  • Check the connectivity for Windows update server list from your WSUS server.

    If WSUS server isn't allowed, please allow from your firewall end,



    Saturday, January 18, 2020 3:03 AM