An Unexpected Error Occurred On A Send. Wsus
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered
Wsus An Unexpected Error Occurred Reset Server Node
by: WSUS synchronization problem Windows Server > WSUS Question wsus error unexpected error click reset server node 0 Sign in to vote The WSUS server is not using a proxy server
Wsus An Error Occurred Trying To Connect
or any type of SSL setting.. I cannot sycn to Microsoft update, I have been trying to resolve this error all weekend: TypeInitializationException: The an unexpected error occurred on a send vmware type initializer for 'Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy' threw an exception. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. 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 an error occurred trying to connect the wsus server 2012 help would be greatly appreciated.. could the WSUS application or the actual database file be corrupted? Thanks -BW Monday, August 05, 2013 1:35 PM Reply | Quote Answers 0 Sign in to vote 3.2.7600.226 is WSUS before KB2720211 (that brings you the 3.2.7600.251), maybe patching it will arrange your problem. Did you already try to add/remove the IIS role ? Are you using SSL protocol to secure the WSUS, as it seems that something might have been changed here too. Indeed, from Secure WSUS 3.0 SP2 Deployment in the WSUS Deployment Guide: To keep the WSUS Web site as secure as possible, require SSL only for the following virtual roots: SimpleAuthWebService DSSAuthWebService ServerSyncWebService APIRemoting30 ClientWebService Maybe have a look to your Authentication Methods and configure the *correct* permissions for the C:\Windows\Temp folder, as documented in Step #1 of the Step-By-Step Installat
Content Page 1 of 1 You cannot start a
Wsus System.io.ioexception -- The Handshake Failed Due To An Unexpected Packet Format.
new topic You cannot reply to this topic Cannot the handshake failed due to an unexpected packet format ssl connect to sever through MMC #1 GFPSAdmin Newbie Group: Regular Members Posts: 3 Joined:
Wsus The Handshake Failed Due To An Unexpected Packet Format 2012
11-Aug-09 Posted 11 Aug 2009, 13:17 I opened my WSUS server to check on new computers and updates, but was unable to connect. https://social.technet.microsoft.com/Forums/office/en-US/14d8972a-0baf-46ed-a970-5167250b8f57/wsus-synchronization-problem?forum=winserverwsus I am running version 3.0 sp1 with mmc 3 on Server 2003 R2 sp2. I get the following error report. QuoteThe 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 http://www.wsus.info/index.php?showtopic=13966 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.
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create https://www.experts-exchange.com/questions/27982642/Wsus-no-longer-synchronising.html a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website http://www.myitforum.com/forums/WSUS-Issues-m237001.aspx Testing Store Headlines Experts Exchange > Questions > Wsus no longer synchronising Want to Advertise Here? Solved Wsus no longer synchronising Posted on 2013-01-02 Windows Server 2008 1 Verified an unexpected Solution 7 Comments 3,543 Views Last Modified: 2013-01-02 My server has stopped updating the wsus catalogs. The unhelpful error i am getting is as follows: TypeInitializationException: The type initializer for 'Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy' threw an exception. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. at Microsoft.UpdateServices.Internal.ClassFactory.CreateInstance(Type type, Object[] args) at Microsoft.UpdateServices.ServerSync.ServerSyncLib.GetWebServiceProxyInternal(UpdateServerConfiguration serverConfig, WebServiceCommunicationHelper an unexpected error 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) I really dont want to have to uninstall the whole thing. Any ideas? thanks 0 Question by:timb551 Facebook Twitter LinkedIn Google LVL 23 Active today Best Solution byThomas Grassi what port is wsus on event 12052 is related to a bad port setting http://technet.microsoft.com/en-us/library/bb632477 see this http://social.technet.microsoft.com/Forums/en-CA/winserverwsus/thread/63605d63-26f6-4397-a2b1-4dce0a9e9d1b Go to Solution 7 Comments LVL 23 Overall: Level 23 Windows Server 2008 8 Message Active today Expert Comment by:Thomas Grassi2013-01-02 what happens when you run this wsusutil /checkhealth 0 Message Active 3 days ago Author Comment by:timb5512013-01-02 c:\Program Files\Update Services\Tools>wsusutil /checkhealth Unknown command. The following commands are known: help checkhealth configuressl configuresslproxy deletefrontendserver listinactiveapprovals removeinactiveapprovals export healthmonitoring import listfrontendservers mov
Reading Mode WSUS Issues Author Message jkabaseball Total Posts : 153 Scores: 9 Reward points : 64490 Joined: 5/5/2011 Status: offline WSUS Issues Wednesday, July 18, 2012 4:16 PM (permalink) 0 I"m having issues simply opening up the WSUS console. WSUS and SCCM are on the same server. I can open it fine if I reinstall for a bit, but after that I get this error. I have tried everything listed in the message. 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.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at System.Threading.ExecutionContext.runTryCode(Object userData) at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) 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 unex