The behavior that you were observing is actually correct!!When Joe resourced the MXD, he must have used his connection (connected as user 'Joe')....the MXD stores this user information along with other connection parameters...The correct way would be for each user to create their own connections with their username/password and then resource their individual MXDs to point to these new connections (which I guess you already figured out).Regards,
How about having each user create his own mxd using their own version of the layer you want to use Editor Tracking on? This should at least solve the problem of only joe being tracked. Make sure that the layer with joe's version is not copied into any of these new mxds because it would be carrying his credentials along.
But did you create your own version to edit the data and replace that version in the mxd and save the mxd after making the version change. Unless you actually change the version in the mxd to your own, it will always use joe's SDE credentials.
Unless the 2 other users changed the version in the mxd from joe's to their own, they will be making changes as joe. This is 1 reason why sharing an mxd that can edit SDE is dangerous as you are providing other user's to someone's SDE version.
My organization tested Editor Tracking in Oracle 11g and it worked as expected. Maybe it is an issue with SQL Server 2012. I would log an incident with ESRI if no one using SQL Server 2012 responds to your post.
Might you be using operating system authentication for tracking and even though you have 3 users with different versions in SDE, they are all logged into the same computer with the same credentials which is what Editor Tracking is using?
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.