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
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I had restarted one of our server instances which is something that I do often.
After restarting the server instance, users began receiving the below error message (URL and SPN identity removed for confidentiality reasons) when trying to open the Nav 2018 RTC app on their local machines.
The Service Principal Name (Delegation) configuration has been set incorrectly. Server connect URL: " "
A call to SSPI failed, see inner exception.
The ClientUserSettings CONFIG file on users' local machines had the value of "Windows" for the "ClientServicesCredentialType" key.
If I change the "ClientServicesCredentialType" key value to "UserName", the users can sign in.
I am unsure why Windows authentication would suddenly stop working as there have been no recent changes to our active directory, etc.
We are using Nav 2018.
Has anyone had a similar issue with Nav 2018? Although all of our users can sign with a username and password, I would like to get back to using Windows for the authentication credentials.
If nothing changed during normal operation of NST, it could be that the nav service account password expired.
Business Applications communities