codeDom posted Oct 13, 2016 SBS 2003 Sharepoint Database... It had no issues sync with MU and downloading updates. Help Desk » Inventory » Monitor » Community » microsoft.public.softwareupdatesvcs Discussion: WSUS Error 386 - No Trust Relationship (too old to reply) Scot 2006-09-12 22:20:02 UTC PermalinkRaw Message I just went There is a > diffrence > in how the problematic site is conneted to the primary site location > verses > the site location that is syncing properly. http://devstude.net/wsus-error/wsus-error-403.php
Thanks, kailar0 0 01/17/13--02:06: WSUS 3.2 replica server synchronization failed with error 'OutOfMemoryException' Contact us about this article Once the upstream server is healthy, the downstream servers will be at Microsoft.UpdateServices.ServerSync.ServerSyncCompressionProxy.GetWebResponse(WebRequest webRequest) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object parameters) at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetDeployments(Cookie cookie, String deploymentAnchor, String syncAnchor) at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetDeployments(String anchorMin, String anchorMax) at Microsoft.UpdateServices.Internal.WebServiceCommunicationHelper.ProcessWebServiceProxyException(SoapHttpClientProtocol& webServiceObject, Exception exceptionInfo) at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetDeployments(String anchorMin, String anchorMax) at Once all of the update approvals have been removed for the GIG_Clients group, and those approval change events synchronized to the replica servers, THEN you can remove the group from the The only allowed classification updates of my upstream sever are the „critical“ and the „security updates“.
Okay. I created a Windows 2008 Server box, patched it, and then installed the WSUS roles. I wouldn't think this is relavent, when syncing one WSUS server to another upstream internal WSUS server? I have three WSUS servers.
The downstream server tries further to delete it's GIG_Clients group with ID: A1180ED0-8A2A-4A69-8467-6A9548C14415 which is not known by the upstream server. Art Bunch posted Jul 9, 2016 Microsoft.net framework install... Monday, April 18, 2011 1:38 AM Reply | Quote 0 Sign in to vote Keep us in the loop on your results. Due to solve my problem I had reduced the declined updates last days, which did not help that.
The only problem is, it isunable to synch with upstream server.Error Event ID 386WebException: The underlying connection was closed: Could not establishtrust relationship with remote server.Do you have a proxy configuration Change:Deleted deployment(Install) of 814033: Critical Update by NT AUTHORITY\NETWORK SERVICE UpdateID:359D3F60-B1AD-4CA7-BCDF-2EFE91227462 Revision Number:100 TargetGroup:GIG_Clients Change:Deleted deployment(Instal at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ProcessTargetGroups(ServerSyncTargetGroup groups) at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ReplicaSync() at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect) at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.CatalogSyncThreadProcess() at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.runTryCode(Object I did decline 1008 updates. Unfortunately it didnt solve the problem.
at System.Xml.XmlTextReaderImpl.Throw(Exception e) at System.Xml.XmlTextReaderImpl.ThrowTagMismatch(NodeData startTag) at System.Xml.XmlTextReaderImpl.ParseEndElement() at System.Xml.XmlTextReaderImpl.ParseElementContent() at System.Xml.XmlReader.ReadElementString() at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderServerSyncCompressionProxy.Read13_UpdateIdentity(Boolean isNullable, Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderServerSyncCompressionProxy.Read14_RevisionIdList(Boolean isNullable, Boolean checkType) at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderServerSyncCompressionProxy.Read23_GetRevisionIdListResponse() Both WSUS >> > installations and configuration are setup the same in the other 2 >> > sites. >> > However one location is unable to synchronize. >> > >> > If so > what > is that point of failure? The previous SUS servers worked fine before migrating it to WSUS.
Remeber this is a problem syncing with an upstream internal WSUS, not the Microsoft server. > One other reason it's not a timeout problem. The only problem is, it isunable to synch with upstream server.Error Event ID 386WebException: The underlying connection was closed: Could not establishtrust relationship with remote server.at System.Net.HttpWebRequest.CheckFinalStatus()at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult)at System.Net.HttpWebRequest.GetRequestStream()at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(StringmethodName, Line 1, position 31747. Regards, , Dec 22, 2006 #20 Advertisements Show Ignored Content Page 1 of 2 1 2 Next > Want to reply to this thread or ask your own question?
Strictly speaking, it is not required, but presumably, at some point, you do want to retire the SUS server. More about the author If you want more detail specifics, I can most certianly post them. Why would the internet have anything to do with this WSUS server connecting to an upstream internal WSUS server. > > > > Please share this information ... > > Really.. It's the most bizarre thing I've seen with WSUS and I've implemented it many times.
However, now I am getting a diffrent Event ID and error message when syncing. Any help is welcomed. HTH Robert Aldwinckle --- >I am having sync issues with WSUS 2.0. check my blog For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Reason: Exception of type 'System.OutOfMemoryException' was thrown.. 2012-12-30 16:22:33.249 UTCInfoWsusService.17CatalogSyncAgent.WaitUntilSyncFinishedOrCancelledAgent signalled done. 2012-12-30 16:22:33.249 UTCInfoWsusService.17CatalogSyncAgent.SetSubscriptionStateWithRetryFiring event SyncFailToStart... 2012-12-30 16:22:33.249 UTCInfoWsusService.17CatalogSyncAgent.WakeUpWorkerThreadProcFound no more jobs. I guess I will need to break out the NNTP Client.. "Robert Aldwinckle" wrote: > (cross-post added to WSUS NG) > "Justin" <> wrote in message > news:... > > > One location is getting the updates from Microsoft, > > and the other two locations are setup in replica mode to point to the > > location that is getting the
Well..... Why would you open INBOUND ports to a resource that is not providing web services to the Internet? >> /Ports/ are not the only thing that can impact data communications, and But, part of the difference here is that I do it on a monthly basis, so the effort of removing approvals is [a] trivial, and [b] doesn't send the Server Sync I assume this might not work.
I cannot reduce the approved updates anymore. And this is a big job. OK, I understand this and am still asking you to please provide details as to what else would becausing this issue? news I previously stated that I have 3 > > sites and 1 WSUS server in each site. > > You also previously posted errors from the /SUS/ server which certainly >
When trying to access the group listed from the web portal it isn't listed. I also stated that there is no proxy system anywhere. I doubt it was ever tested. I'm still a loss.
I moved the HD's and the Memory from the server we were using to another server. Is to uninstall and reinstall WSUS at this location and direct it > >> > to > >> > Microsoft. I am able to access it via DNS with a PING, and TRACERT. So I still stand by the fact that the firewall doesn't seem to be an issue.
Tell me about the VPN connection. Stilll looking for answer to my question? "Robert Aldwinckle" wrote: > (cross-post added to WSUS NG) > "Justin" <> wrote in message > news:... > > > Justin, > > You In the cited thread, the issue was that the group could not be deleted from the upstream server because there were still existing approvals for that group.