File Sharing Error with X-refs

[Tiger]

Hai,

 

I have had troubles with my X-refs lately. Often when I have the file FV.dwg open and I open another file that have FV.dwg as an x-ref, the X-ref is not displayed. In the x-ref list it says File Sharing Error. at the commandline it says Can't open \\one.afconsult.com\projects\24839\Documents\Modell\FV.dwg

 

It's not unique to just these files, it's just an example.

 

If I close FV.dwg, then I can reload in the other file and it looks fine. Sometimes I can just reload the FV.dwg in the x-reflist without closing it, and it works. But sometimes it doesn't.

 

I just installed SP2 and that didn't change anything. I have XLOADCTL set to 2 (and have checked it all the time while replicating the problem, it doesn't change).

 

Anyone have any idea what is wrong?

[nod684]

not sure if it has something to do with XLOADCTL sys var

try setting it to 2

[Tiger]

not sure if it has something to do with XLOADCTL sys var

try setting it to 2

 

.. I have XLOADCTL set to 2 (and have checked it all the time while replicating the problem, it doesn't change). ..?

 

Ahem.

[nod684]

Ahem.

 

sorry, didn't saw that part

[Tiger]

no worries. I was pretty convinced that it must that setting that was messing with me, but it doesn't seem to affect this particular error.

[Dadgad]

Have you tried setting your XLOADCTL to the square root of four?

Sorry, the devil made me do that.

 

Try setting it to 0 first, then reset it to 2.

Certainly sounds screwy, just an anomaly I bet.

Have you checked the ANOMXCTL is set to 0?

[Tiger]

Have you tried setting your XLOADCTL to the square root of four?

Sorry, the devil made me do that.

 

Try setting it to 0 first, then reset it to 2.

Certainly sounds screwy, just an anomaly I bet.

Have you checked the ANOMXCTL is set to 0?

 

I knew we would come to a day when you'd just start inventing variables!

[Dadgad]

So then, it is set to 0, right?

Sorry, having not found anything real to help you I figured

the least I could do was entertain you.

Did you try changing the setting to something else though, and then back to 2, seriously?

[Dadgad]

I think we should put that on the wishlist for 2014 though, the ANOMALY variable.

How many anomalies do you want in the program?

Clearly the great majority of users would vote for 0.

[Tiger]

I think we should put that on the wishlist for 2014 though, the ANOMALY variable.

How many anomalies do you want in the program?

Clearly the great majority of users would vote for 0.

 

Oh I don't know. I know some people that I would set ANOMALY to 64 or something

[Tiger]

Ok. I opened both files. The x-ref didn't load.

 

Closed the layout file. Change XLOADCTL to 0 while the FV.dwg is still open. Opened the layout file and the x-ref showed.

 

Closed everything. Opened both files. The x-ref didn't load.

 

Closed the layout file. Change XLOADCTL to 2 while the FV.dwg is still open. Opened the layout file and the x-ref showed.

 

Closed everything. Opened both files. The x-ref didn't load.

 

 

What's bothering me is that it's a weirdly consistent problem...

[Dadgad]

Perhaps it would be a good idea to close the XREF drawing while you are trying to open the others which contain it? That is what I would do.

 

XNOTIFYTIME does not appear to be a real variable, now they are making stuff up!

[Tiger]

yeah, that is what I have to do. It's just annoying because that is not how I am used to have to do.