web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Error upgrading to ver...
Finance | Project Operations, Human Resources, ...
Suggested Answer

Error upgrading to version 17

(0) ShareShare
ReportReport
Posted on by AstridMalanka 8

Hi,

We were trying to upgrade dynamics from 16 to 17 and we got the following error:

Managed Sync Table Worker encountered an exception, but is continuing because ContinueOnError is true. Table Sync Failed for Table: InventItemPendingPriceV2Staging. Exception: System.InvalidOperationException: Database execution failed: The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.INVENTITEMPENDINGPRICEV2STAGING' and the index name 'I_22964STAGINGIDX'. The duplicate key value is

Since we cannot log into UAT db, what can we do? or does this error means something else?

Thanks

Astrid

  • Suggested answer
    André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 307,361 Super User 2026 Season 2 on at

    Hi Astrid,

    Do you have changes on this data entity? If not, you can consider cleaning the staging details for this entity. If you need to keep the history and you don't have customizations on this entity, you can create a ticket for Microsoft Support.

  • AstridMalanka Profile Picture
    AstridMalanka 8 on at

    Thanks, how do you clean the staging details of the entity? As far as I know there was not change to the entity, which from what we found, this staging table belongs to Pending item prices V2

  • Suggested answer
    Luke Sha Profile Picture
    Luke Sha Microsoft Employee on at

    you may log into database to check the duplicated records first.  then you can remove them in the dB directly as this is staging table in the UAT, then resume package deployment to complete upgrade.

    Then refresh PROD DB to UAT, if DB sync is still failed with same error, you have to run 'clean up' job in the UI or request Microsoft to remove duplicated records in the PROD DB before upgrade PROD.

  • Luke Sha Profile Picture
    Luke Sha Microsoft Employee on at

    why you cannot login DB? you should have access in UAT environment.

  • AstridMalanka Profile Picture
    AstridMalanka 8 on at

    How can I access the environment? There is not access to it.

  • Luke Sha Profile Picture
    Luke Sha Microsoft Employee on at

    Here it is.

    docs.microsoft.com/.../database-just-in-time-jit-access

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the August Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 528 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 424 Super User 2026 Season 2

#3
CU10121822-0 Profile Picture

CU10121822-0 374

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP
License usage reporting (in-app and PPAC) with Entra dynamic groups

Product updates

Dynamics 365 release plans