WSUS on Windows Server 2012 R2 appears to be badly broken

Topic

New Reply

Left hand, meet right hand. Thanks to Cliff Hogan, who’s awake while we all sleep. InfoWorld Woody on Windows UPDATE: Following on a tip from Rod Tren
[See the full post at: WSUS on Windows Server 2012 R2 appears to be badly broken]

Reply | Quote

Replies

2008 R2 has multiple “The last catalog synchronization attempt was unsuccessful” errors as well (Event ID 10222)

Reply | Quote

Woody, thanks for posting the information on InfoWorld and adding the few extra details.
Windows 2012 R2 recovered after 12-13 hours and now can synchronise. I tried everything that I knew, including deleting the updates downloaded in the new Upgrades category with PowerShell, disabling Upgrades and uninstalling the previous wonder patch KB3095113. The failed patch KB3148812 was never installed and people having it even only just installed without the extra configuration from the WSUS Blog might have a different experience.
Doktornotor, I didn’t experience those issues on Windows 2008 R2. Maybe this is something that happened after Microsoft fixed syncing for Windows 2012 R2 at their end as side effect. I will see when I will have a chance later in the day here and let everyone know.
There is also a chance that various systems which synchronise less often, 1 day is standard, to not observe the issue by chance.

Reply | Quote

Sometihng similar happened about 1 year ago, likely for a different reason.
https://support.microsoft.com/en-us/kb/3058255

What I find interesting is that Microsoft says in the KB article:
“Although the workaround in this article was published, and Microsoft support professionals quickly investigated the reported problem, the cause of the sync failure has not been determined.”

Reply | Quote

Woody, I read your update.
Doktornotor was right about Windows 2008 R2. I think the source of the issue was one of the Office Updates – potentially the Skype Update which was expired.
I identified the problem on Windows 2008 R2 only where Office was also scheduled for synchronisation. If Office was not synchronised, then there was no error.
The first failure happened on few installations consistently in the middle of Office synchronisation after few patches synchronised successfully.
I don’t know if Microsoft will provide further information about this issue.

Reply | Quote

New disaster on the way: https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/

😛

Reply | Quote

It has arrived in WSUS and we have the documentation available now https://support.microsoft.com/kb/3159706

Reply | Quote

Yep, I’m writing it up right now.

Reply | Quote