While upgrading from CRM 2011 to 2016 we are facing following issue in the first stage itself while doing up gradation from 2011 to 2013. previously we have done rehearsal at that we didn't face this issue we successfully upgraded at that time now it is returning following issue. Can any one help me on this what was the problem with following
*This post is locked for comments
Hi Bipin Kumar,
There is the problem with CRM 2013 version we are using to build the environment on up gradation. Later on we used different version of CRM 2013 which solved our issue. You can refer following link to get more idea about this
https://community.dynamics.com/crm/f/117/t/126709
Hi ,
We're running into the same error and I'm working to get past it, thank you for your article because it's the only reference to the issue I've found so far. I'll note that CRM 2013 SP1 did get me past the issue without any changes, but I ran into another known issue for SP1 that I've used RTM to get past before. So now I'm trying to locate a RU pre-SP1 to see if that will work for this issue, if I do I'll post my findings.
Like Ankit, I'm wondering how did you go about identifying the column(s) causing the issue? I've captured the SQL statement for the table merge but I've yet to fully debug to identify the tables. The LOE to restore the data back after with your approach has me concerned because the table in question for us is quite large.
Thanks,
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156