Skip to main content

Notifications

Announcements

No record found.

Finance | Project Operations, Human Resources, ...
Suggested answer

Error upgrading to version 17

(0) ShareShare
ReportReport
Posted on by 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

  • Luke Sha Profile Picture
    Luke Sha on at
    RE: Error upgrading to version 17

    Here it is.

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

  • AstridMalanka Profile Picture
    AstridMalanka 8 on at
    RE: Error upgrading to version 17

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

  • Luke Sha Profile Picture
    Luke Sha on at
    RE: Error upgrading to version 17

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

  • Suggested answer
    Luke Sha Profile Picture
    Luke Sha on at
    RE: Error upgrading to version 17

    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.

  • AstridMalanka Profile Picture
    AstridMalanka 8 on at
    RE: Error upgrading to version 17

    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
    André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 291,642 Super User 2024 Season 2 on at
    RE: Error upgrading to version 17

    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.

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

Congratulations 2024 Spotlight Honorees!

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December!

Congratulations to our December super stars! 🥳

Get Started Blogging in the Community

Hosted or syndicated blogging is available! ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,642 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,371 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans