I am using two way mirroring. Some users needed to edit one of their files named "SMU Line List Apparel.xlsx." When they went to do so, they found three copies of this document with these names: "SMU Line List Apparel [dmx].xlsx", "SMU Line List Apparel [src].xlsx" and "SMU Line List Apparel [src] [src].xlsx." They claimed that no one changed the name of this file and did not know which one was the original. When I looked at the versions through DMX, I saw that two were new files and one had seven versions; the first six versions all had the correct file name "SMU Line List Apparel.xlsx" the last version had the odd appended file name. The last version "SMU Line List Apparel [dmx].xlsx" did not have a user's name as the person who checked the new version in. Instead, it had the DNN admin account, which is what it shows whenever a file is dropped onto a share and that file is synced.

1) Is it possible that DMX renamed this file? If not, how did it show up as a new version with a new file name and the admin account was listed as the user who checked it in?

2) Is the DNN admin account the process account that is used for the syncing? People have thought that I have logged in as admin and modified their documents because it says admin in the version log.

Thanks for your time,

Jason

1. Yes. This is DMX's way to deal with a document it believes has changed *both* in DMX and on the source since the last sync (sync both ways).

2. Yes. It is an automatic process that you invoke when you create a sync folder.

So the real question is how DMX believed the source version or DMX version were changed. The DMX version change is pretty straightforward as it is a date stored in the DMX_Entries table. The source edit time is more tricky as it looks at LastModifiedTime on the file. Maybe something wrong there?

Peter