A couple of computers are not finding Xrefs when opening drawing files

[fdebolt]

In our office we have a problem with a couple machines that when they open a drawing it can never find the attached xrefs. I have checked the xref settings and preferences and have found nothing that seems to be causing this since the machines that work have the same settings. This has become a very annoying issue for the two people having the problem. They have to repath the XREFs each time they enter a file. Has anybody else experienced this or have a clue what we can do to solve this issue.

I had thought they had a different path or server name, but that also all checked out fine. The goofy part is it is only happening on 2 of the 20 workstations we have and I have tested the same files on most of them and it is consistantly only these two.

[emodderman]

I have 2007 at home and i get this all the time. Drive me nuts! a fix for this would be fantastic!

[Mike.Perry]

Hi

Have you determined if the problem is computer based or user based?

Have a good one, Mike

[rkmcswain]

As related to the parent drawing, where do the xref drawings reside?
In the same directory?
In a relative directory?
On a different drive?

How are the paths saved?
None, relative, full?

[fdebolt]

Xrefs are on the network - paths saved as full paths.

[rkmcswain]

Xrefs are on the network - paths saved as full paths.

UNC paths or drive letters?
Does the person who is logged on have access to these locations?
Are the locations physically accessible from this machine?

[Try copying the saved path to the clipboard and then use it in the (findfile) lisp function]
(findfile "\\\\server\\share\\projects\\123456\\myXref.dwg")

Download FILEMON to watch file activity while the parent drawing loads. See what happens when AutoCAD gets to the point of loading these reference files.

[fdebolt]

They are pathed and when in the drawing you can repath it, save it and it you get out and come back in the xrefs are missing again.

[Avatart]

You haven't said whether the drives are all mapped out to the same drive letter on all machines, that will have that effect. Try using relative paths, they usually fix these problems.

[fdebolt]

Everything is mapped the same - I had the IT guy confirm it this morning. I will try relative path - but in past we had no luck with that - I belive that to be user error.

[Avatart]

Everything is mapped the same - I had the IT guy confirm it this morning. I will try relative path - but in past we had no luck with that - I belive that to be user error.

Good old fashioned "Carbon Unit Failure", eh? Please do let us know when you find the cause of the problem, I'm intrigued.