Windows Update sync error: writing update to DB, cannot commit

Question

Checking the Software Update Point Sync status, I saw my main SUP has trouble to synchronize with MS-Update. However synchronization is successful in the WSUS console.

I see this in wsyncmgr.log:

Synchronizing update 58b95dca-41aa-44e3-8293-eccd607481d5 - 2019-08 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4512509)  SMS_WSUS_SYNC_MANAGER   2021-10-18 13:08:04 60152 (0xEAF8)
*** declare @rc int, @errxml xml, @errmsg nvarchar(max); EXEC @rc=sp_SetupCI 18227874, 0, @errxml out, @errmsg out; select @rc, @errxml, @errmsg    SMS_WSUS_SYNC_MANAGER   2021-10-18 13:08:06 60152 (0xEAF8)
*** [25000][266][Microsoft][SQL Server Native Client 11.0][SQL Server]Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count = 0. : sp_SetupCI    SMS_WSUS_SYNC_MANAGER   2021-10-18 13:08:06 60152 (0xEAF8)
*** declare @rc int, @errxml xml, @errmsg nvarchar(max); EXEC @rc=sp_SetupCI 18227874, 0, @errxml out, @errmsg out; select @rc, @errxml, @errmsg    SMS_WSUS_SYNC_MANAGER   2021-10-18 13:08:06 60152 (0xEAF8)
*** [42000][50000][Microsoft][SQL Server Native Client 11.0][SQL Server]ERROR 3930, Level 16, State 1, Procedure dbo.spLogEntry, Line 13, Message: The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction. : spRethrowError    SMS_WSUS_SYNC_MANAGER   2021-10-18 13:08:06 60152 (0xEAF8)
Failed to sync update 58b95dca-41aa-44e3-8293-eccd607481d5. Error: Failed to save update 58b95dca-41aa-44e3-8293-eccd607481d5. CCISource error: -1. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate SMS_WSUS_SYNC_MANAGER   2021-10-18 13:08:06 60152 (0xEAF8)

I looked back in the logs and only this update has trouble writing its info to the database.

Answer 1

Hi, @Alexandre Blanchette
Thank you for posting in Microsoft Q&A forum.

So only this update failed to write to SCCM DB: 2019-08 Cumulative Update for Windows Server 2016 (1803) for x64-based Systems (KB4512509)?

I found this update has been replaced by other updates:

And the error in your wsyncmgr.log is related to SCCM database, since we can not modify the database by ourself, you may need to open a support case for a dedicated Support.
Here is the link of CSS support:
https://support.microsoft.com/en-us/hub/4343728/support-for-business

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

---

Answer 2

I opened a support case with Microsoft and the solution was to simply decline the update in WSUS so it wouldn't sync up to SCCM.

Answer 3

No point checking for sync in WSUS console. ConfigMgr uses WSUS in the backend. You should just concentrate on sync status status in ConfigMgr. Coming to the issue. Apart from that 1 error in the WSUS sync log, does the sync actually fail? Can you please check on the console for the status under monitoring?