Personalized Community is here!
Quickly customize your community to find the content you seek.
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
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 2 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 | Upcoming TechTalks
We have had an issue for many months now.
We are using NAV 2017 and the Single Sign On client to connect to an Azure VM with NAV on it.
The client frequently hangs - you get a spinning wheel and have to wait up to a minute to get it back although it rarely actually ever crashes.
We have upgraded SQL server express, moved to a NAV2018 platform (objects still at NAV 2017), looked at sql, created dedicated drives for sql files, done lots of traces and tests but have not been able to identify the issues.If we run the Windows client directly on the server via RDP we do not get the issue but for various reasons do not want to use this as the way we access NAV.
Has anyone else had this issue or any ideas?
1. authentication does work fine with no errors
2. after authentication, users are able to work and then get the spinning wheel
1. authentication does not work fine and users get the spinning wheel before they are able to logon?
We have already talked to you about these issues and you have been on the correspondence for this.
I was really trying to find out if anyone else had these issues.
But in answer to the question log on is fine and you can work normally but then you will get a spinning wheel especially If NAV is not the active window and you are switching back to it from say Excel.
Hope you are well. Yes, I remember. I do not think we were able to reproduce this scenario in standard. Are you running latest CU and were you able to test in standard?
We upgraded NAV2018 client/platform to CU27 a few months ago. I notice CU33 has a platform fix for "The client crashes or the ribbon hangs". Not exactly sure what that means we have a hang but necessarily tied to the ribbon. I have tested connectivity using just the web client and don't think we get any hangs then - all the processing on the server. So the issue seems to be using SSO with the Windows client/server client - maybe that was only ever really properly designed for use on the NAV server using RDP and cannot handle much latency between client and server?
Lars has now recommended we move the platform to latest BC14 platform but everything else at NAV2017.
I wonder if these issues are why MS has moved away from the Windows client.
Yes, it is a difficult support request and quite complicated to find root cause, I believe this is now with Azure support. I got side tracked of this one, but Lars is on it. Hopefully we are able to resolve it for you.
If you eventually get a solution, please do post it here. It is highly appreciated by others.
Business Applications communities