locked
Error: Connection Error RRS feed

  • Question

  • Hi all,

    This is the scenario... after a failed in-place update at the WSUS server, I've had to install a new brand VM with Windows 2012R2 with WSUS role.

    The DB instancy is in another server (SQL2008R2) so, I've change the value "SQLServerName" at the registry to the SQLServer.

    At the IIS, I've change the Wsus Pool the memory to 0 (it is the only service that will be running at the server), and the Queue Length from 1000, to 30000...

    After installing KB3159706, run "C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing

    but... nothing worked for me... when I open the WSUS the red error connection appears...

    Any idea if the problem could be for a certificate needed? or an API, or something else?

    Thank you in advance!

    Pablo.



    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.

    The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,

    Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.


    System.IO.IOException -- The handshake failed due to an unexpected packet format.

    Source
    System

    Stack Trace:
       at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
       at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
       at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
       at System.Net.ConnectStream.WriteHeaders(Boolean async)
    ** this exception was nested inside of the following exception **


    System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.

    Source
    Microsoft.UpdateServices.Administration

    Stack Trace:
       at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)
       at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
       at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
       at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()

    Tuesday, September 24, 2019 1:44 PM

All replies

  • Please increase memory for WSUS apppool from IIS manager as below guidance

    https://www.404techsupport.com/2016/03/21/iis-wsus-private-memory/

    https://gal.vin/2016/10/27/wsus-errors/

    For further WSUS troubleshooting, Please keep this guidance also.

    https://gallery.technet.microsoft.com/office/Troubleshooting-WSUS-d63da113

    Wednesday, September 25, 2019 12:54 AM
  • 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.

    The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,

    Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.
       
    System.IO.IOException -- The handshake failed due to an unexpected packet format.

    Hi Pablo,
      

    I recommend starting with the following checks:
      

    1. Since you mentioned that the SQL server currently used by WSUS is on a different server, make sure the following services on the SQL server are up and running:
        
      -  SQL Server (MSSQLSERVER)
        
      At the same time, if this service is logged on as a Local System, it is recommended to change to a domain user with the relevant permissions to log on.
         

         
    2. As suggested in the prompt, try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.
         
    3. In addition, the "The handshake failed due to an unexpected packet format" error usually occurs during the communication process in which SSL is applied. Is your WSUS configured to use SSL encryption?
        

    Reply back with the results would be happy to help.
       

    Regards,
    Yic

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

    Wednesday, September 25, 2019 2:38 AM
  • Hi,
     

    Any update is welcome here.
    If the issue is resolved, share your solution or find the helpful response "Mark as Answer" to help other community members find the answer.
     

    Thank you for your cooperation, as always.
     

    Regards,
    Yic

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

    Wednesday, October 2, 2019 2:34 AM