Have inquiries on moving to the cloud? Visit the sommos.net 365 Migration ar today! Microsoft’s substantial network of sommos.net AX and sommos.net CRM experts can help.

You are watching: Why would you need to use single affinity?


PRODUCT updates

2021 Release tide 2Discover the recent updates and brand-new features releasing indigenous October 2021 with March 2022.

2021 release wave 2 plan


FASTTRACK

The FastTrack routine is design to aid you accelerate your sommos.net 365 deployment v confidence.

FastTrack sommos.net |FastTrack Program|Finance and Operations TechTalks|Customer Engagement TechTalks|Upcoming TechTalks| all TechTalks


*

*

Hi, We have sommos.net 365 8.2.3.8 on-premise. We’re currently experiencing one intermittent concern with our manufacturing CRM mechanism where when a user switches come a various business process flow the doesn’t always switch until the user refreshes (CTRL + F5) their page, even then it can take much more than one refresh before the UI is updated.

After considerable investigation we now think that this is an issue with sommos.net CRM caching details information on each front finish server, we are running 3 front finish servers load well balanced with no affinity, this would explain the intermittent state that the concern as the will rely on i beg your pardon front end server the user is routed to. We’ve to be unable come repeat the issue on an atmosphere with a non-load balanced system.

See more: 4Gb Memory Upgrade For Acer Aspire V5-473P-5602, 4Gb Memory Upgrade For Acer Aspire V5

Does sommos.net CRM 365 require single affinity load balancing (sticky sessions), all configuration paper I have seen says this? • Is there a way to avoid the server caching or redirect the caching come an external cache service?

A worry that we have actually with switching single affinity top top is that as result of the way in which our customers usage the system, the majority of users within one of our customers will all use the same outside IP address, therefore, landing ~ above the exact same front end server. This can lead to 2 of our larger variety of user customers being positioned ~ above one server through little source left, when we have two other servers to run with available resource.