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 1 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
Hi, We have Dynamics 365 188.8.131.52 on-premise. We’re currently experiencing an intermittent issue with our production CRM system where when a user switches to a different business process flow it doesn’t always switch until the user refreshes (CTRL + F5) their page, even then it can take more than one refresh before the UI is updated.
After extensive investigation we now believe that this is an issue with Dynamics CRM caching certain information on each front end server, we are running 3 front end servers load balanced with no affinity, this would explain the intermittent state of the issue as it will depend on which front end server the user is routed to. We’ve been unable to repeat the issue on an environment with a non-load balanced system.
Does Dynamics CRM 365 require single affinity load balancing (sticky sessions), all configuration document I have seen suggests this? • Is there a way to stop the server caching or redirect the caching to an external cache service?
A concern that we have with switching single affinity on is that due to the way in which our customers use the system, the majority of users within one of our customers will all use the same external IP address, therefore, landing on the same front end server. This could lead to two of our larger number of user customers being positioned on one server with little resource left, while we have two other servers running with available resource.
I am afraid that CRM requires Affinity: Single - please see blogs.msdn.microsoft.com/.../network-load-balancing-microsoft-dynamics-crm-2013
Business Applications communities