A new update to the Windows Server Update Services (WSUS) software was released on September 4, 2018. This update is known as Configuration Manager 1811.
The an error occurred trying to connect the wsus server reset server node is an error that can occur when connecting to WSUS.
The fundamentals of WSUS.
I upgraded all of the customer’s servers over the weekend. Everything should have gone well, right? When I arrived at work on Monday morning, I discovered that the WSUS server had not been updated. After that, I signed in to the server and got the following error message:
When attempting to connect to the WSUS server, an error occurred. This mistake may occur due to a variety of factors. Check the server’s connection. If the issue continues, please contact your network administrator.
Strange, since I updated the server the day before yesterday… After some experimenting and Googling, I was able to find the answer.
Let’s get this sorted. “An issue occurred when connecting to the WSUS server.”
I’m assuming you’re a system administrator who knows how to use Command Prompt in the instructions below. You can always write a remark if you don’t.
- As an administrator, open Command Prompt.
- Execute the command below: Update ServicesTools CD (C:Program FilesUpdate ServicesTools)
- wsusutil.exe postinstall /servicing was then used.
- Restart the WSUS Server if necessary.
The issue should be resolved now.
As you can see in the picture, my Command Prompt is elevated.
When attempting to connect to the WSUS server, an error occurred. This mistake may occur due to a variety of factors. Check the server’s connection. If the issue continues, please contact your network administrator.
Does it function on a temporary basis?
It’s also conceivable that your WsusPool has ceased working in IIS. Navigate to Application Pools in IIS. Start the Pool by right-clicking on WsusPool.
When attempting to connect to the WSUS server, an error occurred. This mistake may occur due to a variety of factors. Check the server’s connection. If the issue continues, please contact your network administrator.
Summary
Is config manager also used in your infrastructure? Is my solution just a stopgap measure? Then this Technet may be of additional use to you.
This is the whole error message
When attempting to connect to the WSUS server, an error occurred. This mistake may occur due to a variety of factors. Check the server’s connection. If the issue continues, please contact your network administrator.
The WSUS administrative console was unable to make a remote API connection to the WSUS Server.
Check that the Update Services, IIS, and SQL services are all operating on the server. Restart IIS, SQL, and the Update Services Service if the issue continues.
An unexpected problem has occurred in the WSUS management interface. It’s possible that this is a temporary issue; try restarting the administrative console. If the problem continues,
Delete the wsus file under percent appdata percent MicrosoftMMC to remove the console’s persistent preferences.
System.IO.IOException — The handshake failed because the packet format was unexpected.
System of Origin
Stack Trace: Stack Trace: Stack Trace: Stack Trace: Stack Tra System calls Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest) at Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest. System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at Net.Security.SslState.StartReceiveB At System.Net.Security, checkCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest). SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at System.Net.Security.SslState.ProcessAuthentication(Boolean receiveFirst, Byte[] buffer, As Threading. ExecutionContext. At System, call RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) Threading. ExecutionContext. at System, execute(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) Threading. ExecutionContext. At System.Net.TlsStream, run(ExecutionContext executionContext, ContextCallback callback, Object state). At System, ProcessAuthentication(LazyAsyncResult result). Net.TlsStream. At System, write(Byte[] buffer, Int32 offset, Int32 size). Net. ** This exception was buried inside of the following exception ** ConnectStream.WriteHeaders(Boolean async)
System.Net. The underlying connection was terminated due to an unexpected error on a send, which resulted in a WebException.
Microsoft.UpdateServices.Administration is the source of this information.
Microsoft’s Stack Trace. UpdateServices.Administration.AdminProxy. Microsoft’s CreateUpdateServer(Object[] args) method. At Microsoft, you may use UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings) and UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings). Microsoft’s UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer() UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get ServerTools()
Related
The failed to start and configure the wsus service is a common error that has been occurring for some time. Bas Wijdenes has released a fix to fix this issue.
Related Tags
- the wsus administration console was unable to connect to the wsus server via the remote api.
- wsus an error occurred while generating the report
- wsus connection error
- fatal error: the wsus synchronization service (wsusservice cannot be stopped)
- an error occurred when trying to perform a database operation wsus