Link to home
Start Free TrialLog in
Avatar of GrieverNSS
GrieverNSS

asked on

WSUS Connection Error

See Code.

I've been fighting with this WSUS server for the better part of 2 weeks and still can't manage to get it up and running for more than 30 minutes at a time.  I've set permissions for the 'Network Service' on the various folders it's errored out on, reset services, even uninstalled and reinstalled.  I can't figure out what's going on.  Anyone have some insight?
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()

Open in new window

error.jpg
Avatar of leakim971
leakim971
Flag of Guadeloupe image

Hello GrieverNSS,

Which version ? Have you applied the latest service pack for this version ?

Regards.

Avatar of GrieverNSS
GrieverNSS

ASKER

This is SP1, 3.2.7600.226
Apparently it's already been updated, so I am already on SP2
ASKER CERTIFIED SOLUTION
Avatar of Don
Don
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
This should help you as well:
 
Issues with the WSUS 3.0 Administration Console
Any luck here?
I just wanted to comment that I ran into the same problem with WSUS 3.0 SP2 installed on Windows Server 2003 SP2.
It turned out the problem was due to an applied hotfix KB938759.
After uninstalling this hotfix - WSUS came back up just as it did before.
Hope that helps someone.  Cheers!