Answered by:
WSUS admin console unable to connect with remote API

Question
-
Hi Microsoft team,
I have a problem with my WSUS service, that stops unprovoked.
The Windows (Windows Server 2012 R2) system log gives me this:
- System
- Provider
[ Name] Service Control Manager
[ Guid] {555908d1-a6d7-4695-8e1e-26931d2012f4}
[ EventSourceName] Service Control Manager
- EventID 7031
[ Qualifiers] 49152
Version 0
Level 2
Task 0
Opcode 0
Keywords 0x8080000000000000
- TimeCreated
[ SystemTime] 2016-09-29T06:22:14.165442400Z
EventRecordID 22639
Correlation
- Execution
[ ProcessID] 700
[ ThreadID] 3260
Channel System
Computer AKZ-WSUS.AAGAARD.LOCAL
Security
- EventData
param1 WSUS Service
param2 2
param3 600000
param4 1
param5 Restart the service
570073007500730053006500720076006900630065000000
--------------------------------------------------------------------------------
Binary data:
In Words
0000: 00730057 00730075 00650053 00760072
0010: 00630069 00000065
In Bytes
0000: 57 00 73 00 75 00 73 00 W.s.u.s.
0008: 53 00 65 00 72 00 76 00 S.e.r.v.
0010: 69 00 63 00 65 00 00 00 i.c.e...
When I try to connect to the WSUS console window, it gives me this:
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()I've tried to do the things it tells me to do, but with no luck.
The only thing running on this server is WSUS service and my Kaspersky Security Center (SQL database), and that is not what is blocking the WSUS service (have checked). Im new to this forum and this is my first thread. I apologize if I do not mean the start requirements what I should minimum give you, of information.
Best regards Kim (male) ;)
Friday, September 30, 2016 9:16 AM
Answers
-
Hi Kim,
Please check if you have install KB3159706 on the WSUS server, if yes, then we need to do manual steps list in the following article, otherwise, WSUS console will crash:
https://support.microsoft.com/en-us/kb/3159706
Best Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- Proposed as answer by Anne HeMicrosoft contingent staff Monday, October 10, 2016 7:29 AM
- Marked as answer by Anne HeMicrosoft contingent staff Thursday, October 13, 2016 2:04 AM
Monday, October 3, 2016 2:34 AM
All replies
-
Hi Kim,
Please check if you have install KB3159706 on the WSUS server, if yes, then we need to do manual steps list in the following article, otherwise, WSUS console will crash:
https://support.microsoft.com/en-us/kb/3159706
Best Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- Proposed as answer by Anne HeMicrosoft contingent staff Monday, October 10, 2016 7:29 AM
- Marked as answer by Anne HeMicrosoft contingent staff Thursday, October 13, 2016 2:04 AM
Monday, October 3, 2016 2:34 AM -
Hi Kim,
Could the above replies be of help? If yes, you may mark it as answer, if not, feel free to feed back.
Best Regards,
Anne
Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Monday, October 10, 2016 7:29 AM