WSUS ERROR:Connection Error

I just started getting this WSUS ERROR:Connection Error when opening the WSUS console.  It has always worked perfectly before.  I have tried some of the things mentioned on this site but nothing seems to work. I am on WSUS 3.0 SP2. Below is the detailed message from WSUS.

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(Protocol
Token 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.ExecuteCodeWithGuarante
edCleanup(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(Str
ing serverName, Boolean useSecureConnection, Int32 portNumber)
atMicrosoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServ
er(String serverName, Boolean useSecureConnection, Int32 portNumber)
atMicrosoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpd
ateServer(PersistedServerSettings settings)
atMicrosoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.Connec
tToServer()
atMicrosoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_Se
rverTools()
TonygretAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

antony_kibble<!-8D58D5C365651885FB5A77A120C8C8C6-->Commented:
Check to see if the NETWORK service still has rights to the C:\Windows\Temp folder. If not, reset the permissions so that it has.

The root folder of the local content directory must have at least Read
permissions for the Users security group and the NT Authority\Network Service
account. In other words, if the WSUS content directory is C:\Updates\WSUSContent,
the Updates directory must have the correct permissions. The BITS service will fail
if these permissions are not set.

If the APIRemote component of IIS is not working you will not be able to connect. from a command prompt go to the following

C:\Program Files\Update Services\Tools

run the following command, wsusutil.exe checkhealth. When it is done look at your event viewer of the wsus server for errors. If apiremote throws up and error this may be what is causing it.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
TonygretAuthor Commented:
Restored to earlier image
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server Apps

From novice to tech pro — start learning today.