Home > An Unexpected > An Unexpected Error Occurred On A Send. Wsus

An Unexpected Error Occurred On A Send. Wsus

Contents

at Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(Type type, Object[] args) at Microsoft.UpdateServices.ServerSync.ServerSyncLib.GetWebServiceProxyInternal(UpdateServerConfiguration serverConfig, WebServiceCommunicationHelper webServiceHelper, Boolean useCompressionProxy) at Microsoft.UpdateServices.ServerSync.ServerSyncLib.GetWebServiceCompressionProxy(UpdateServerConfiguration serverConfig, WebServiceCommunicationHelper webServiceHelper) at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.RetrieveSubscriptionData() at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect) Any help would be greatly I went into the %appdata%\MMC and deleted the WSUS file but that was just the server connection data for WSUS app. Microsoft Customer Support Microsoft Community Forums {{offlineMessage}} Store Store home Devices Microsoft Surface PCs & tablets Xbox Virtual reality Accessories Windows phone Microsoft Band Software Office Windows Additional software Apps All Ostensibly this would indicate a catastrophic failure of IIS, or the WSUS website, but in reality that's rarely the actual cause. http://lanprolab.net/an-unexpected/an-unexpected-error-occurred-on-a-send.php

For some reason the NETWORK SERVICE account keeps losing permission to the C:\Windows\Temp folder. The server access Internet regularly and there is no proxy on that LAN. Are the client systems having any issues communicating with the WSUS server? (Are the majority of Last Reported Date values within the past 24 hours?)Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA SolarWinds It can also manifest asa result of a failed installation of KB2720211.

Wsus An Unexpected Error Occurred Reset Server Node

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, Edited by Lawrence GarvinModerator Sunday, August 11, 2013 8:11 PM Marked as answer by Yan Li_Moderator Saturday, August 17, 2013 6:33 AM Sunday, August 11, 2013 8:09 PM Reply | Quote This may be a transient error; try restarting the administration console. In the instance case, though, I believe the first step should be to resolve the Health Monitoring Service issues, which may actually account for the 'unexpected error' issue as well.

Solution was found on Microsoft Answers. { 3 comments… read them below or add one } Laurie April 1, 2013 at 7:10 am I had the exact same issue These errors are recorded because the WSUS Health Management Service cannot communicate with those webservices. Last week WSUS patched itself and all of a sudden the WSUS Admin console was inaccessible: Clicking the copy error to clipboard gave this: The WSUS administration console was unable to An Error Occurred Trying To Connect The Wsus Server 2012 If this error persists, Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.

Register now! It was a hit or miss if it would synch and I restarted the server several different times but no luck. Get 1:1 Help Now Advertise Here Enjoyed your answer? 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()

I get the following error report. Wsus System.io.ioexception -- The Handshake Failed Due To An Unexpected Packet Format. If this error persists, Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\. This may be a transient error; try restarting the administration console. Reply Diego July 9, 2014 at 1:02 pm Thanks for this post is a solution help to fix the sync!

Wsus Error Unexpected Error Click Reset Server Node

What virtual root and port is WSUS actually installed to? try here Links About Me Adam Brigham IT Blog Home Map Tag Cloud2010 Active Directory Sites and Services Apple AutoDiscover Backup Exec backups batch CAS Citrix DNS esx ESXi Exchange Exchange 2010 exchange Wsus An Unexpected Error Occurred Reset Server Node Monday, August 05, 2013 2:19 PM Reply | Quote 0 Sign in to vote btw, im usingVersion: 3.2.7600.226 Monday, August 05, 2013 2:20 PM Reply | Quote 0 Sign in to Wsus An Error Occurred Trying To Connect If the problem persists, try restarting IIS, SQL, and the Update Services Service.

Once I reset the permissions everything worked like a charm GFPSAdmin, on 11 Aug 2009, 13:17, said: I opened my WSUS server to check on new computers and updates, but was More about the author If you like to migrate an older 2003 Server (and the installed client CALs) to a 2008 R2 server for example, you … Windows Server 2008 How to Deleting a SSL This may be a transient error; try restarting the administration console. 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) An Unexpected Error Occurred On A Send Vmware

It seems to exist in concert with SSL issues performing synchronizations (and, apparently outdated root certificates). Microsoft Windows Server comes with so… Windows Server 2008 Multiple websites on single instance of IIS Article by: Neeraj Prologue It is often required to host multiple websites on a single Again, thanks very much! check my blog System.IO.IOException -- The handshake failed due to an unexpected packet format.

The WSUS administration console has encountered an unexpected error. The Handshake Failed Due To An Unexpected Packet Format Ssl Brian Mason MCTS\MS MVP - Enterprise Mobility (CM) http://mmsmoa.com Attend MMS in May! #2 jkabaseball Total Posts : 153 Scores: 9 Reward points : 64490 Joined: 5/5/2011 Status: Icon Legend and Permission New Messages No New Messages Hot Topic w/ New Messages Hot Topic w/o New Messages Locked w/ New Messages Locked w/o New Messages Read Message Post New

Solved The WSUS administration console has encountered an unexpected error, Server 2008R2 Posted on 2010-12-01 Windows Server 2008 Microsoft IIS Web Server ASP 1 Verified Solution 6 Comments 5,447 Views Last

Once your back you may find that client scans against WSUS no longer succeed. In other words, if the WSUS content directory is C:\Updates\WSUSContent, the Updates directory must have the correct permissions. This may be a transient error; try restarting the administration console. Wsus The Handshake Failed Due To An Unexpected Packet Format 2012 If the problem persists, try restarting IIS, SQL, and the Update Services Service.The WSUS administration console has encountered an unexpected error.

net stop wuauserv net start wuauserv wuauclt /resetauthorization /detectnow   DETECTNOW.BAT - To only have client check the WSUS server now. Back to top #2 pascalvis pascalvis Newbie New Members 2 posts Posted 22 April 2016 - 12:48 PM Did you perhaps installed update : KB3148812 Solution Microsoft WSUS Product Team Please get the version number from the Main Page of the WSUS Administration Console. news Verify that the Update Services service, IIS and SQL are running on the server.

Connect with top rated Experts 25 Experts available now in Live! I get the following error report. If this error persists, Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\. QuoteThe WSUS administration console was unable to connect to the WSUS Server via the remote API.

The WSUS administration console has encountered an unexpected error. The WSUS administration console has encountered an unexpected error. Click reset server node to try to connect to the server again.   Please help me someone.>

>

0 Pimiento OP johntasker Dec 13, 2014 at 8:09 UTC 1st Post Check your WSUS service is running. 0 Sunday, August 11, 2013 3:12 AM Reply | Quote Moderator 0 Sign in to vote I may be blabbing nonsense here, but Lawrence- do you think re-running postinstall could fix this

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_ServerTools() So after much Googling I found KB3148812 is the update that broke The API Remoting Web Service is not working The Reporting Web Service is not working This is a core issue. Event 12002 The Reporting Web Service is not working. Join our community for more solutions or to ask questions.

Licensed to: Scott Korman Home WSUS stopped working by jcvbass on Jul 25, 2012 at 11:14 UTC | WSUS 0Spice Down Next: WSUS Stuck on "Reset Server Node" Error IN THIS Thanks !!!! Had the exact same issue.