We have our PI Data Archive on a collective with two member servers, a primary and a secondary.
We have a user whose PI Datalink keeps switching to the secondary server. He sees funny questionable data (there is a known gap in some data on our secondary server in 2017), goes to the settings in the Pi Datalink tab, then connection manager, then sees the connection (host) is the secondary server (not primary). He can switch it to the primary, however goes back at some future time and its back on secondary. Has anyone else ever heard of Datalink behaving in this manner? I checked his SDKUtility, the user looks to be set up ok with the correct collective members and priority (priority 1 is on the primary server).