Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
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 | Preview 2020 Release Wave 1 Timeline
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 | Upcoming TechTalks
We are upgrading from 2013r2 to 2018 CU2 and we're in the data upgrade step. We're following the official documentation (https://docs.microsoft.com/en-us/dynamics-nav/upgrading-the-data#ImportAppObj) but whenever we start the data upgrade we'regetting a message saying "The server stopped the session (ID: xxxx) because of a stop session request"
any ideas of what could be wrong here?
Thanks in advance!
Full error message :
It looks strange and I have no idea what causes this problem. You would better read a research paper and here link for you to get proper help. Maybe you should spend more time on research and write here what was a problem. I'm very interested in this and hope you'll find the answer.
had the same problem with upgrade... when running the data upgrade process use Serial instead of Parallel and check Continue on error. If it gets on certain completion percent even after running it multiple times, restart SQL server service and NAV service in administration, then run the data upgrade again. Worked for me, spent many hours figuring this out, hope it helps you as well.
Managed to solve this by running the upgrade from the dev env. with serial but did not tick the continue on error checkbox. Not sure exactly what was the problem from the admin shell :/
Business Applications communities