ermcenter.com

Home > Event Id > Event Id 386 Synchronization Failed

Event Id 386 Synchronization Failed

Unapproved: 2609 Approved: 1889 Declined: 1057 Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA SolarWinds Head GeekMicrosoft MVP - Software Distribution (2005-2012) My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.GarvinThe views expressed on this post are mine Reason: Could not load typeMicrosoft.UpdateServices.Internal.UpdateFragments from assemblyMicrosoft.UpdateServices.Common, Version=2.0.0.0, Culture=neutral,PublicKeyToken=31bf3856ad364e35 because the format is invalid.Did anybody encountered the same problem?Thank you for any help and suggestion.Rgds,DWN farhan27 2008-04-25 06:41:30 UTC PermalinkRaw Message So how do you think to solve this problem? My AccountSearchMapsYouTubePlayGmailDriveCalendarGoogle+TranslatePhotosMoreDocsBloggerContactsHangoutsEven more from GoogleSign inHidden fieldsSearch for groups or messages 404 Not Found nginx HOME | SEARCH | REGISTER RSS | MY ACCOUNT | EMBED RSS | SUPER RSS | this contact form

Every time gets the synchronization with 0% the error 'OutOfMemoryException'… Nevertheless the same problem exists with the version 3.2.7600.226 too. Thanks, kailar

0 0 01/28/13--02:40: WSUS 3.2 replica server synchronization failed with error 'OutOfMemoryException' Contact us about this article Hi Lawrence, Thanks for your answer. No: The information was not helpful / Partially helpful. GIG_Cients by upstream: ID: 42F13AF7-A2BB-438F-8F3B-E935D094514A GIG_Cients by dowstream: ID: A1180ED0-8A2A-4A69-8467-6A9548C14415 So when I remove the approvals for that group GIG_Cients (with ID: 42F13AF7-A2BB-438F-8F3B-E935D094514A) on the upstream server and at end delete that https://support.microsoft.com/en-us/kb/909456

The timeout is actually occuring because of the number of update approvals that need to be removed. 2013-01-17 08:58:06.166 UTC Error WsusService.29 CatalogSyncAgentCore.ProcessTargetGroups DeploymentSync: could not delete target group a1180ed0-8a2a-4a69-8467-6a9548c14415:Timeout expired. 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 If you try to remove the approval for too many updates at once, you'll get a timeout error when the database fails to report the task as completed before the console

Thanks, kailar

0 0 01/14/13--07:48: WSUS 3.2 replica server synchronization failed with error 'OutOfMemoryException' Contact us about this article After reducing the approved updates the error with 'OutOfMemoryException‘ is finally All servers are locating in different geographical locations and have this problem. These updates are being approved automatically on the patch day only to some pilot computer groups. I've certainly never had a thousand approved updates on a WSUS server!

Thanks, kailar

0 0 01/17/13--15:18: WSUS 3.2 replica server synchronization failed with error 'OutOfMemoryException' Contact us about this article I am trying to delete the target group on downstream server manually x 8 Private comment: Subscribers only. 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. have a peek at this web-site After that I tried many times to synchronize the downstream server with this but all time got the same error.

Please see ME815155 for a more detailed explanation. And this is a big job. The fix was to create a custom view so that those approved updates could be identified and the approvals removed for that group, thus allowing the group to be deleted from See M909456 to solve this problem.

So how do you think to solve this problem? Why do you have =5459= APPROVED updates? Note These localized versions include the Simplified Chinese and Traditional Chinese versions. Type the following commands to stop the WSUS service and Microsoft Internet Information Services (IIS): net stop wsusservice Iisreset /stop 6.

Claim or contact us about this channel Embed this content in your HTML Search confirm cancel Report adult content: click to rate: Account: (login) More Channels Showcase RSS Channel Showcase 3223522 weblink After each cycle of update approval removals, synchronize ALL downstream servers so they get the update approval removals. WSUS synchronization error (too old to reply) DWN 2006-01-11 01:58:02 UTC PermalinkRaw Message Hi,I have the synchronization error as below:(first occurrence)Event Type: ErrorEvent Source: Windows Server Update ServicesEvent Category: SynchronizationEvent ID: Reporting service: stats.update.microsoft.com, SyncFromMU: False 2012-12-30 16:18:43.671 UTCInfoWsusService.28CatalogSyncAgentCore.ExecuteSyncProtocolServer ID is da9aa6fb-ea7f-4929-862a-7d6e9eae1212 2012-12-30 16:18:44.530 UTCInfow3wp.25SusEventDispatcher.TriggerEventTriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange 2012-12-30 16:18:44.546 UTCInfow3wp.36ThreadEntryThreadHelper.ThreadStart 2012-12-30 16:18:44.546 UTCInfow3wp.36SusEventDispatcher.DispatchManagerWorkerThreadProcDispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange

Of course..... I had to rebuild the replica WSUS by some of them too. x 6 EventID.Net This problem may occur in a large-scale, non-English-language deployment in which the WSUS database grows to more than 2 gigabytes (GB), because the DisableThrottle setting is not included navigate here There are four computer groups which are causing probably this problem.

The 'OutOfMemoryException‘ error is gone. Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA SolarWinds Head GeekMicrosoft MVP - Software Distribution (2005-2012) My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.GarvinThe views expressed on this post are mine and do not necessarily reflect the 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.ServerSync.CatalogSyncAgentCore.ReplicaSync() at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect) at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect) at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.CatalogSyncThreadProcess() at

The eventlog reports this: Source: Windows Update Category: Synchronization EventID: 386 Synchronization failed.

http://social.technet.microsoft.com/Forums/en/winserverwsus/thread/4e57e3ad-a8f8-4da4-8bec-410b0180bc4c No, you don't need to do anything on the downstream servers. Action: No Retry, Fail. The only allowed classification updates of my upstream sever are the „critical“ and the „security updates“. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSy \ ncAction.WSyncAction.SyncWSUS SMS_WSUS_SYNC_MANAGER 4/05/2016 6:00:28 \ AM 5968 (0x1750)

STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" \ COMP="SMS_WSUS_SYNC_MANAGER" SYS=SERVER.DOM1.DOM2.COM SITE=XXX PID=4208 TID=5968 \ GMTDATE=Tue May 03 20:00:28.780 2016 \ ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyn \ cAction.SyncWSUS" ISTR1="UssInternalError: SoapException:

Type the following command to restore the database: Execute %programfiles%\update services\Tools\osql\osql.exe S machinename\WSUS E -b n Q "RESTORE DATABASE SUSDB FROM DISK=backup location" 7. Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA SolarWinds Head GeekMicrosoft MVP - Software Distribution (2005-2012) My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.GarvinThe views expressed on this post are mine and do not necessarily reflect the x 8 Anonymous WSUS must have port 80 (HTTP) and port 443 (HTTPS) free to access the Internet in order to synchronise. http://ermcenter.com/event-id/dns-event-recv-call-failed.html Note: Depending on the number of updates actually approved for that group, it may take more than one cycle.

wsusutil reset Dbcc checkdb Reindexed DB Reduced declined updates Restarted IIS, BIT, SQL server, wsus service Upstream or master server 2008 sp2 x64: RAM 8GB Wsus version: 3.2.7600.251 All Updates: 5459 Approved: 5459 Unapproved: 0 Reason: Exception of type 'System.OutOfMemoryException' was thrown.. 2012-12-30 16:22:33.249 UTC Info WsusService.17 CatalogSyncAgent.WaitUntilSyncFinishedOrCancelled Agent signalled done. 2012-12-30 16:22:33.249 UTC Info WsusService.17 CatalogSyncAgent.SetSubscriptionStateWithRetry Firing event SyncFailToStart... 2012-12-30 16:22:33.249 UTC Info WsusService.17 CatalogSyncAgent.WakeUpWorkerThreadProc Found no more jobs. Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA SolarWinds Head GeekMicrosoft MVP - Software Distribution (2005-2012) My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.GarvinThe views expressed on this post are mine and do not necessarily reflect the We have one upstream w2k8 server and 22 downstream w2k3 server as replica.

These steps I have already done without any effect. Reason: . 4 Comments for event id 386 from source Windows Server Update Services Subscribe Subscribe to EventID.Net now!Already a subscriber? I did decline 1008 updates. Ican see the installation option when visitting Microsoft update.DWNPost by DWNLooks like you installed .NET Framework v2.0 on top of your WSUSinstallation -- or have tried to install WSUS on top

English: Request a translation of the event description in plain English. Hier one of that groups GIG_Clients. Several time synch. My guess would be there's at least another 4000 that can also be changed.

CatalogSyncAgent quits but will run rollup before terminating ... 2012-12-30 16:22:33.264 UTC Info WsusService.17 CatalogSyncAgent.UpdateServerHealthStatusBasedOnError ServerHealth: Updating Server Health for Component: CatalogSyncAgent, Marking as Not Running 2012-12-30 16:22:34.577 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: RollupAgent, EventInfo: 2012-12-30 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 Also, the Certificate Revocation List (CRL) is now examined to make sure that the certificate has not been revoked.cause:These problems may occur in a large-scale, non-English-language deployment in which the WSUS