Answered by:
WSUS stopped working

Question
-
WSUS was working and then one day it stopped working. I have no clue as to why as there were no changes to my environment other than installing Microsoft updates, which are all up-to-date.
In a Hyper-V instance I’m running Windows Server 2012 R2 Standard. The workstations that I support are either Windows 10 or Windows 7 and I have about 200 machines. When I try to start the Management Console (3.0) this is the error message that is in the 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.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.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()
In the Server Management Console, I get the following error message
SERENITY 7053 Error Windows Server Update Services Application 6/24/2016 12:40:48 PM
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.NullReferenceException -- Object reference not set to an instance of an object.
So far I’ve rebooted, restarted Update Services service, IIS and SQL are running on the server and I’ve deleted %appdata%\Microsoft\MMC\wsus
Does anyone have any ideas how I can get this restarted?
Thanks, Sam
Friday, June 24, 2016 6:42 PM
Answers
-
....there were no changes to my environment other than installing Microsoft updates, which are all up-to-date.
https://support.microsoft.com/en-au/kb/3159706
https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/
Did you perform the manual steps described in these articles?
Don [doesn't work for MSFT, and they're probably glad about that ;]
- Marked as answer by Sam-coderedsafety Saturday, June 25, 2016 12:14 PM
Saturday, June 25, 2016 12:50 AM
All replies
-
....there were no changes to my environment other than installing Microsoft updates, which are all up-to-date.
https://support.microsoft.com/en-au/kb/3159706
https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/
Did you perform the manual steps described in these articles?
Don [doesn't work for MSFT, and they're probably glad about that ;]
- Marked as answer by Sam-coderedsafety Saturday, June 25, 2016 12:14 PM
Saturday, June 25, 2016 12:50 AM -
That worked, thank you. I would have expected the normal update process to have taken care of all of the details, obviously it didn't.
Thank you very much
Sam
Saturday, June 25, 2016 12:14 PM