Failed to sync update Error: Failed to save update

Boopathi S 3,601 Reputation points
2025-01-18T23:12:24.69+00:00

Hello,

Below error message received when WSUS Sync.

Synchronizing update b968cec5-ec74-4939-9291-1bcce5505b15 - Microsoft Edge-WebView2 Runtime Version 132 Update for ARM64 based Editions (Build 132.0.2957.115)

Synchronizing leaf update 5b11a91f-c9d9-41c6-90b5-e46d0f92e8df

Writing update 5b11a91f-c9d9-41c6-90b5-e46d0f92e8df

*** insert into CI_DocumentStore (DocumentIdentifier, Body, IsVersionLatest, DocumentType) values ('5b11a91f-c9d9-41c6-90b5-e46d0f92e8df', '', 0, 0)~;select SCOPE_IDENTITY()

*** [23000][2627][Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Violation of PRIMARY KEY constraint 'CI_DocumentStore_PK'. Cannot insert duplicate key in object 'dbo.CI_DocumentStore'. The duplicate key value is (16777216).

Failed to sync update b968cec5-ec74-4939-9291-1bcce5505b15. Error: Failed to save update 5b11a91f-c9d9-41c6-90b5-e46d0f92e8df. CCISource error: -1. Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.UpdatesManager.UpdatesManagerClass.DefineUpdate

is there a key already exits in SQL database? Please help how to fix the issue.

There are other 3 updates with same kind of message.

Microsoft Configuration Manager
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. AllenLiu-MSFT 47,631 Reputation points Microsoft Vendor
    2025-01-20T02:37:42.8166667+00:00

    Hi, @Boopathi S

    Thank you for posting in Microsoft Q&A forum.

    The error message you are encountering indicates a violation of a primary key constraint in the SQL database, specifically for the CI_DocumentStore table. This typically occurs when there is an attempt to insert a record with a key that already exists in the database.

    To resolve this issue, you may consider the following steps:

    1. Check for Existing Records: Verify if the key (in this case, 16777216) already exists in the CI_DocumentStore table. You can do this by running a SQL query to search for that specific key.
    2. Decline Updates: If the updates causing the issue are not required in your environment, you can decline them in WSUS to prevent them from synchronizing to Configuration Manager.
    3. Manual Distribution: If you need the updates and cannot wait for a fix, consider manually downloading and distributing them.

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Add comment".


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.