WSUS failing

[laserblazer]

Since the holidays, when I try to run WSUS it tries to add a snap-in and then errors. Can anyone offer any suggestions please?

 

I've tried all of the suggestions in the first paragraph.

 

 

 

he 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.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.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.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.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)

at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()

at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_Ser

[sparkeh]

The error matches the one in this article: Issues with the WSUS 3.0 Administration Console

 

This error is probably due to the WWW Publishing service being configured to allow interaction with the desktop. To solve this problem, take the following steps:

• Open the Services snap-in (click Start, click Run, and then type services.msc).
  
• Right-click the World Wide Web Publishing service and select Properties.
  
• On the LogOn tab, clear the Allow service to interact with desktop check box.
  
• Click OK, and then dismiss the Services snap-in.
  
• From a command shell, type iisreset.
  
• At this point you should be able to access the WSUS server from the console again.
  

This error is caused by the issue described in KB919085 (Error message when you browse an .aspx page and the World Wide Web Publishing Service is configured to interact with the desktop: "The compiler failed with error code 128").

[laserblazer]

The box wasn't checked. I tried the iisreset anyway but the problem's still there.

[Chuckster]

I experienced this a few times on a Windows 2003 box and the only way I resolved it was to reinstall WSUS.