XREF's saved path reverts to file name after reloading updated xref

[Anonymous]

I'm having an issue with my xref saved paths. I work off of a windows 10 pc on a server, along with 4 other computers. Only mine seems to have this issue. Sometimes when I make revisions or work on a file that is xrefed into another, and I save it and reload it on the other file, the Autocad will for some reason change the saved path to the file's name, rather than the file's location path. I've audited, purged, regenerated, you name it to make sure the two files are clean. Still not helping. Also, this only seems to be happening on my computer... and sometimes... so I know I'm missing another clue here. I just can't figure it out. Help please! 🙂

john.vellek has embedded your image(s) for clarity

[RobDraw]

Look closely and you will see that those drawings cannot be found by AutoCAD. That is why the path is changed to the file name. Once the files are located and repathed, all will be good.

[Anonymous]

Right, that's why I highlighted the saved path. Something happens that causes the path to change from the saved file location. It's simplifying it to the file name alone for some reason. I've resaved the correct path and it will revert back to the file name again. It seems to be happening when I go into that file, make changes, save, and reload updated xref. 

[john.vellek]

HI @Anonymous,

Can you try changing the file paths to relative rather than absolute to see if that makes a difference?

Does this problem happen if you copy that project (folder structure and files) to your C: drive? I am wondering if AutoCAD is having trouble finding your network drives.

Please select the Accept as Solution button if my post solves your issue or answers your question.

[john.vellek]

Hi @Anonymous,

Did you have a chance to try this with a local location as opposed to a network one?  I would also like to know if the results are different if you use relative paths.

Please select the Accept as Solution button if my post solves your issue or answers your question.

[Anonymous]

I've saved have of the xrefs on the file to be relative and the other half absolute. So far no broken xref paths. I've tried making changes in both the relative and absolute xref source files, saved and reloaded... and the problem hasn't reoccured yet. I've also copied the files and placed onto my C: drive as you said, to see if that causes it... that isn't recreating the problem either. So basically, I'm not sure what's causing it and having a hard time recreating the problem to test solutions. Is any of this helpful? Thanks for the help by the way. 

[Anonymous]

I should also add, we've always used absolute paths and this issue hadn't happened so I don't think that's the issue. 

[john.vellek]

Hi @Anonymous,

From your post it sounds like the behavior is no longer happening as the Xref paths are being retained. Is this the case or am I not understanding this issue properly?

[Anonymous]

John! New development. The issue popped up again. This time, instead of resaving the saved path location, I changed it from absolute to relative, reloaded, and poof! Does that indicate that there is a problem with my computer's network connection? It still seems strange given that as I mentioned yesterday, we've always used absolute. 

[john.vellek]

HI @Anonymous,

This could be a variety of things. i suggest that you first have your IT person monitor your network connection to see if there is an latency, packet loss, etc.

You could have  a failing network card, port on the switch might be bad, bad cable, too many hops, etc.

Lets see if there is anything three that looks like it is the issue.

[Anonymous]

Hi John, 

We don't have an IT department, so if something is wrong with our network, we'll have to deal with that separately. But is there anything CAD related that can be causing the issue? I know you said it could be a variety of things. The reason I ask is I'd like to determine whether or not CAD is the source of the issue as a first step, then if not, zero in on the network as a possible culprit. So far no other problems related to the network are appearing on other programs on my computer, nor with my other team members. 

[john.vellek]

Hi @Anonymous,

The images you show indicate that the xref can not be found. This is likely because a network drive is not obtained or not obtained quickly enough. If this does not happen locally then I suspect you have a network issue.

You can try logging in as a brand new user with administrator permissions and no Group Policy applied from your network. Then launch AutoCAD with no modifications/customizations to see how it behaves.

Please select the Accept as Solution button if my post solves your issue or answers your question.

[agentornge75]

I am having the same issue: I reload my xref and it changes ALL of my absolute paths to relative paths.  My REFPATHTYPE variable is set to <2> so we should ONLY have absolute paths (because relative paths are garbage).

If it were a network issue, then closing the drawing and reopening it shouldn't be possible.  When I do so, the correct and updated xref shows.  If I reload that XREF in the newly opened drawing, the drawing changes all my XREF paths to relative.

I've tried an audit, and found 10 errors, which it fixed.

I can't figure out what is happening to this *one drawing.  Next I'll be creating a new drawing and re-piecing this together.  sometimes its best to throw away a broken drawing and start anew.

[cadffm]

>"My REFPATHTYPE variable is set to <2> so we should ONLY have absolute paths"

Nothing to do with your situation. This variable is just for the default type for the moment you attaches a file as xref.

>"(because relative paths are garbage)."

Clever sounds different

>"If it were a network issue, then closing the drawing and reopening it shouldn't be possible."

That's a wrong conclusion.

>"I've tried an audit, and found 10 errors, which it fixed."

In all files? (Recoverall, thats makes also sure you are saves all files in the newest file format)

>"I can't figure out what is happening to this *one drawing.  Next I'll be creating a new drawing and re-piecing this together. "

First step should be: detach and rE- Attach ing

>"sometimes its best to throw away a broken drawing and start anew."Yes.

Yes, if there is time, you can continue trying to figure out the problem with the original file.

[cadffm]

>"My REFPATHTYPE variable is set to <2> so we should ONLY have absolute paths"

[cadffm]

Nothing to do with your situation. This variable is just for the default type for the moment you attaches a file as xref.

[cadffm]

>"(because relative paths are garbage)."

[cadffm]

Clever sounds different

>"If it were a network issue, then closing the drawing and reopening it shouldn't be possible."

That's a wrong conclusion.

>"I've tried an audit, and found 10 errors, which it fixed."

In all files? (Recoverall, thats makes also sure you are saves all files in the newest file format)

>"I can't figure out what is happening to this *one drawing.  Next I'll be creating a new drawing and re-piecing this together. "

First step should be: detach and rE- Attach ing

>"sometimes its best to throw away a broken drawing and start anew."Yes.

Yes, if there is time, you can continue trying to figure out the problem with the original file.

[agentornge75]

>"My REFPATHTYPE variable is set to <2> so we should ONLY have absolute paths"

"Nothing to do with your situation. This variable is just for the default type for the moment you attaches a file as xref."

Agreed.  It was mentioned as a pre-empt to someone suggesting that be set.

>"(because relative paths are garbage)."

"Clever sounds different"

personal opinion, just happens to be true.

>"If it were a network issue, then closing the drawing and reopening it shouldn't be possible."

"That's a wrong conclusion."

fair enough.

>"I've tried an audit, and found 10 errors, which it fixed."

"In all files? (Recoverall, thats makes also sure you are saves all files in the newest file format)"

yes.  all xrefs that were in all drawings that were found and not unreferenced were opened, audited, purged, audited, and saved.

>"I can't figure out what is happening to this *one drawing.  Next I'll be creating a new drawing and re-piecing this together. "

"First step should be: detach and rE- Attach ing"

did that, but didn't mention it earlier.  didn't affect my issue. 

>"sometimes its best to throw away a broken drawing and start anew."Yes.

"Yes, if there is time, you can continue trying to figure out the problem with the original file."

Agreed.  Generally speaking.  I've found that all things being equal, the fastest solution usually works best.  Many situations are one-offs or you encounter every few years in odd very situational times.  I can either spend my time finding an elusive solution or creating a work around.  The ROI for fixing the problem is diminishing when you have a deadline and budgets.

So here is what I found out.  the XREF I was bringing in as an Overlay was from an outside firm (XREFa).  That firm used our survey reference, and had brought it into XREFa as an Attach XREF.  It was not transmitted to my company, and was showing in their drawing as unreferenced attached XREF with a relative path.

When I brought XREFa into my drawing  as an overlay it worked fine.  When i reload XREFa: it changed the path for the survey in my drawing to relative.  

When I reopened XREFa and detached the unreferenced Attach XREF and saved it, I was then able to reload XREFa in my drawing and it no longer changed the path of my survey XREF to an relative path.

can't exactly figure out why, when I was Overlaying XREFa and not attaching XREFa (and therefore it should not have been bringing in any of the XREFs it had with it)...but that did fix it.

cheers mate. thanks for the quick response.

Greg

---

[agentornge75]

>"My REFPATHTYPE variable is set to <2> so we should ONLY have absolute paths"

[agentornge75]

"Nothing to do with your situation. This variable is just for the default type for the moment you attaches a file as xref."

[agentornge75]

Agreed.  It was mentioned as a pre-empt to someone suggesting that be set.

[agentornge75]

>"(because relative paths are garbage)."

[agentornge75]

"Clever sounds different"

[agentornge75]

personal opinion, just happens to be true.

>"If it were a network issue, then closing the drawing and reopening it shouldn't be possible."

"That's a wrong conclusion."

fair enough.

>"I've tried an audit, and found 10 errors, which it fixed."

"In all files? (Recoverall, thats makes also sure you are saves all files in the newest file format)"

yes.  all xrefs that were in all drawings that were found and not unreferenced were opened, audited, purged, audited, and saved.

>"I can't figure out what is happening to this *one drawing.  Next I'll be creating a new drawing and re-piecing this together. "

"First step should be: detach and rE- Attach ing"

did that, but didn't mention it earlier.  didn't affect my issue. 

>"sometimes its best to throw away a broken drawing and start anew."Yes.

"Yes, if there is time, you can continue trying to figure out the problem with the original file."

Agreed.  Generally speaking.  I've found that all things being equal, the fastest solution usually works best.  Many situations are one-offs or you encounter every few years in odd very situational times.  I can either spend my time finding an elusive solution or creating a work around.  The ROI for fixing the problem is diminishing when you have a deadline and budgets.

So here is what I found out.  the XREF I was bringing in as an Overlay was from an outside firm (XREFa).  That firm used our survey reference, and had brought it into XREFa as an Attach XREF.  It was not transmitted to my company, and was showing in their drawing as unreferenced attached XREF with a relative path.

When I brought XREFa into my drawing  as an overlay it worked fine.  When i reload XREFa: it changed the path for the survey in my drawing to relative.  

When I reopened XREFa and detached the unreferenced Attach XREF and saved it, I was then able to reload XREFa in my drawing and it no longer changed the path of my survey XREF to an relative path.

can't exactly figure out why, when I was Overlaying XREFa and not attaching XREFa (and therefore it should not have been bringing in any of the XREFs it had with it)...but that did fix it.

cheers mate. thanks for the quick response.

Greg

[cadffm]

>"(because relative paths are garbage)."
"Clever sounds different"
>"personal opinion, just happens to be true."
No it isn't in 2 of 3,5 cases and in the third case it is no matter.

1- Requirements where Absolutet paths do not work (without having to change them separately during the data exchange).
Relative pathes are a good solution

2- Requirements where relative paths do not work (without having to change them separately during the data exchange).
Absolute paths are a good solution

3- If both work well with the requirements, then it does not matter (One may like to convince me otherwise).
But in terms of possible changes in the timing of a project (which is more than a handful of files), I would always prefer the relative path.

Each variant makes sense and provides options for the file and folder structure which the other does not offer.

3,5 = With absolute, relative or without path information: PROJECTNAME is also often the hero in these XRef games.

By the way: The ignorance of users I do not allow as an excuse, in the case is not the program but the level of knowledge of the user.

Unfortunately, I have no other idea without checking the files.
I would be very interested in it since I recently also one
Very much worthy case had to play a role in the XRefs.
(can you share it with etransmit along with any external file?)

>"So here is what I found out. "
Wow, thanks for sharing!