Xref Conflict Error

[Anonymous]

We are having an issue with our xrefs.  We will open an xref to edit.  We make some changes, save, and close the xref.  For some reason, the xref has some sort of error and saves as:

filename_ADMIN_Nov-03-073551-2019_Conflict

It often deletes the original file and sometimes it doesn't.  We can open up this new xref file and save as back to the original name.  We often need to update the file path in the drawings referencing this xref.  This is not an error that we have been able to reproduce, but it has been happening a lot in our office in the last few weeks.  We have users on AutoCAD LT 2015, 2018, and 2019.  

Any help would be appreciated.

[pendean]

What does "open an xref to edit" please? Use command names.

is everyone saving down to 2013dwg file format to accommodate that LT2015 user(s)? That's probably a contributing factor.

And by chance did you fix all of your XREFs and top files with RECOVER or RECOVERALL command? Looks like you might need to do so.

[Anonymous]

"Open an xref" means that if you are in a file with xrefs, you right click it to get the shortcut menu.  From that menu, we pick the option to "open the xref".  It is the same as opening the file that is xrefed in.

Yes everyone does have their files set to save down to AutoCAD 2013.  This is done for our office and for other offices we work with such as surveyors, contractors, etc.

We did not use Recover or Recoverall as we did not get an error message.  It just renames the xref file with the ADMIN_date_Conflict.  If it kept happening, I could see recover fixing an error, however, this is randomly happening to different users in the office on old and new project files.  I will try the Recover command next time it happens.

[pendean]

"ADMIN_date_Conflict." sounds like a server/Windows log-in problem: did you all change things recently? is your I.T. involved here? they should be.

In the mean time...
As a test, for a small group of you usign 2018-2019 only, work for a few hours in files with XREFs that ALL where fixed with RECOVER command and with the 2018dwg file format set.
See if you can replicate the problem.

Report back your findings.

No, there is no miracle fix, your problem is unique and you need to help yourself and help us find the problem. Hope your findings from the test are fruitful.