Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
While updating my machine platform from 21 to 24 (application version 8). I get following error on step 19:
GlobalUpdate script for service model: AOSService on machine: Dev
Moving forward when I see the log the step 19 log it gives error on three standard tables BIConfiguration, FormRunConfiguration and SysClientPerf. The error is as following:
Table Sync Failed for Table: BIConfiguration. Exception: System.InvalidOperationException: Database execution failed: Violation of PRIMARY KEY constraint 'I_65518FIELD'. Cannot insert duplicate key in object 'dbo.SQLDICTIONARY'. The duplicate key value is (4451, 29, 1, 0).
The same error has logged for FormRunConfiguration and SysClientPerf.
What can be done to clear this issue? Should I delete these table data or table+schema from Sql (after taking backup)? or is there any workaround to get rid of these errors?
Please help with your experience. Thank you.
Have you tried to rerun the step? Sometimes this helps. Is there any reason to go for PU24 instead of the latest available? You can also try the latest available PU.
Thanks for reply. I resumed multiple times but it didn't help. Now I just aborted it and start again. We are refreshing our one environment database to Dev environment to reproduce a scenario there. The source environment is currently on PU24. We want everything on Dev as it is on source environment. That's why before refreshing data we are updating Dev to PU24.
The restart would also be an option. Please update the thread if you did or did not succeed with the update.
It took me a while to check what really the problem was. After spending some time I found the solution to this problem. I wrote a detailed blog on it to help others.
d365fo platform update lcs globalupdate.html
Thanks for your feedback. As moderator, I have verified your answer as you probably were not able to mark your own answer.
Just wanted to add that I also got this error on an update 26, and I just opened Visual Studio and Synchronized the database, and got no errors.
Then I just Retried the upgrade script, and it ran to completion.
Business Applications communities