More WSUS Sync failures

Topic

New Reply

Those of you working on update servers over the weekend have my sympathy. There’s a lot of confusion over last Thursday’s KB 4458469 cumulative update
[See the full post at: More WSUS Sync failures]

Reply | Quote

Replies

As I don’t use WSUS myself, I’d be curious to know whether any part of its “syncronization” process relies on WaaSAssessment values in the system registry.

— Arvy

Reply | Quote

I have two small WSUS sites. One has had no sync failures this week. The other had a couple failures on Sept. 22 but the third (automatic sync) on Sept. 22 was successful. Looking back, both have been able to sync at least once a day since Sept. 10; once in a while, they have to try two or three times on the same day before a successful sync.

Reply | Quote

Last night was fine, kicked a manual sync two seconds ago and it failed.  Support folks don’t go to Ignite so there will still be folks left behind that can work on fixing this.

Susan Bradley Patch Lady/Prudent patcher

2 users thanked author for this post.

Nibbled To Death By Ducks, woody

Reply | Quote

@woody wrote:

“Of course, a big chunk of Microsoft staff is in Orlando, getting ready for Ignite. Are we going to see any sort of resolution on this in the near term! Great way to treat your corporate customers”

Funny thing, in the roster of speakers page, not once do the words “Windows” or “Operating System” appear.

Is it possible that in this Titanic of an “organization” (and I use that noun lightly) there’s no one person in the wheelhouse with a sign on their door that says, “The OS Buck Stops Here”, and that this fact may presage the eventual end of Windows as a client OS?

I’d rather jump in the street in front of a bull at Pamplona than run an OS that only works from The Cloud.

But then, I’m old.

Just idle musings.

—–

BTW, the weather looks great for the Ignite event: 95F and raining! Just bring your DEET and stay indoors as much as you can! (Unless you’re thick skinned and can breathe underwater.)

Win7 Pro SP1 64-bit, Dell Latitude E6330 ("The Tank"), Intel CORE i5 "Ivy Bridge", 12GB RAM, Group "0Patch", Multiple Air-Gapped backup drives in different locations. Linux Mint Newbie
--
"The more kinks you put in the plumbing, the easier it is to stop up the pipes." -Scotty

Reply | Quote

To be more precise on this peculiar issue…

SoapException: Fault occurred InvalidCookie

in System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)

in System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

in Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetUpdateData(Cookie cookie, UpdateIdentity[] updateIds)

in Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetUpdateData(UpdateIdentity[] updateIds, List1 allMetadata, List1 allFileUrls, List`1& updatesWithSecureFileData, Boolean isForConfig)

in Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetUpdateDataInChunksAndImport(List<code>1 neededUpdates, List</code>1 allMetadata, List`1 allFileUrls, Boolean isConfigData)

in Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)

Reply | Quote

We run WSUS 3.2 on Windows 2008R2. We are mostly Win7, but we have started getting some Win10 (against my recommendation). It looks like a pain to configure WSUS for Win10 because of all the different versions. Would a new version of WSUS work better with Win10?

Edit to remove HTML – Please use the “Text” tab in the post entry box when you copy/paste

Reply | Quote

Honestly no.  You have to use a blend of WuforBiz settings and WSUS.  Newer WSUS just handle the feature release better.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Thank you for your reply. I wish there was a better way, but I guess all we can do is play the cards MS dealt us.

Reply | Quote

11 p.m my normal sync failed

11:25 it tried again/failed

11:50 it tried again/worked.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Attached image of our corporate WSUS log.   From 9/21 to 9/23 we have 100% failures for both manual and scheduled syncs.  No successful sync since 9/20.

While testing WSUS  in our lab environment we also see a majority of failures.  Although some manual syncs eventually do get through after 6-8 retries (but who has the time for that?)

 

 

Reply | Quote

Any news here? We need the KB4457127, but its not syncing to WSUS. It IS being offered if i check directly against Microsoft, but i really want WSUS to handle the updates to all the servers..

Reply | Quote

Scheduled sync success on 9/25 12:00 am in production env.   This is our first successful sync since 9/20.   Will continue to track progress..

 

Reply | Quote

We’ve had “Scheduled” sync failures beginning 9/21 and continuing daily until I performed a MANUAL sync today (9/26), which was successful. WSUS 6.3.9600.18694 on Server 2012 R2 STD

Reply | Quote

Mine is still misbehaving, seems to be related to Windows Definitions, I would love if someone could also confirm they are still having issues :/

Reply | Quote