For no reason the MMC for WSUS is not connectiing to the server

Question

All,
I rebooted the WSUS server after a windows update and now I cannot connect to the WSUS server.  I get error: connection error.  I've reviewed all posts for this issue, but none of them help.  This is ridiculous as I finally got it working
and once again, right after an update, it screws up!!!  What is going on?
Here's the details of the error when copied to clipboard:
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.CheckCompletionBeforeNextReceive(ProtocolToken message, 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.Net.TlsStream.CallProcessAuthentication(Object state)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   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.PooledStream.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.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
   at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()
It was working perfectly before the update.  Please help!!
Lee Feldman
Feldman Consulting Co.
Lee Feldman SMB Consultant

Answer 1

Thank you for your input.  At least you're not like Lawrence giving poor information.
Hmmmm.. having been working with this product for eight years now, while sometimes I make an erroneous statement, it rarely happens these days.
In this case, it is Yan Li who has given you incomplete information. In addition to the split-server scenario not supporting the
database on a Terminal Services server (which is the information provided by Yan, but not really relevant to this conversation), it is also true that WSUS has
never been supported on a Terminal Services server.
This was posted to the Release Notes, historically, but due to several omissions in the WSUS v3 SP2 Release Notes, does not appear in that document. (That is to say, the SP2 release notes were exclusive to the SP2 feature set, and were not inclusive of the
RTM and SP1 limitations and issues.)
Here is the entry from the
WSUS v3 Service Pack 1 Release Notes:
WSUS 3.0 SP1 is not supported on servers running Terminal Services
Although WSUS 3.0 SP1 may still run on servers running Terminal Services, doing so is not supported or recommended. WSUS 3.0 SP1 will not run on a server running Terminal Services in configurations using remote SQL Server implementations. Because all remote
custom actions (including installation) on a Terminal Services license server will be run as the system account, and the server's system account may not have permissions on the remote SQL Server, the installation may fail.
Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
SolarWinds Head Geek
Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
http://www.solarwinds.com/gotmicrosoft
The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.