AutoCAD MEP xref mixup in Project Navigator?

[gunnar_larsson]

Hi!

AutoCAD MEP2012, Project Navigator in a multidiscipline environment running on Win7-64 enterpriseN clients, Filestore = Virtual R8 server with a NAS setup for daily backup and "previous versions" of files.

We have a rather mysterious problem. This is the second time it happens.

For some reason, suddenly the xrefs in views (view files) in ONE of our projects are being switched out and all layers turned on.

All the drawings are thereby spoiled and has to be revised again.

There is nothing to indicate that someone had opened and saved the files, accidentally creating errors.

The bak-files are not the same date as the dwg-file in the same folder. ?

The latest file on the NAS restore (previous version) is not of the same date as the bak-file. ??

It seems that it happens for all disciplines, therefore I find it difficult to point at some user fault.

Has anyone seen something like this and could point me in the right direktion?

//G

[gunnar_larsson]

All input will be appreciated :-).

This is probably a question for Autodesk, but someone else may have seen this before, so...

I have gone through the project looking for patterns, but can´t really find anything that makes sense.

I have attached a doc that might explain and also versions of the .dst and .apj files.

For those who might be interested, please take a look at the attached files.

Tha only thing that I can see happened at approximately the same time as the file errors, is that an extra level was added and the height of the underlyoing floor was changed.  Could that be connected somehow?

[Anonymous]

Is is possible the [Project Setting > Basic > Drawing Settings > Match Sheet Layers to View] has been toggled on?

Or, has a construct been deleted, recreated with new neame or an element been altered by deleting from construct, adding a new one with different name? This is seen as a new file and all layers are rset to as inserted.

We get around that by not deleting but just repathing the inserted element (via Xref dialog). The insert name is maintained and view layer setttings are not upset

[awitt]

Is your VUSRETAIN set to 1?

[Anonymous]

Another thought, the addition of level might have prompted a "regenerate all views". Maybe that in combo with visretain setting in the view or construct(s) might have caused the attachments

[gunnar_larsson]

Thank´s all.

It´s still a mystery.

It´s higly unlikely that anyone should have toggled the  [Project Setting > Basic > Drawing Settings > Match Sheet Layers to View] . I am (normally) the only one managing project´s CAD-settings.

At times, people replace the xrefs, but that only affect the layers of that xref, not the others. And it wouldn´t attach several other xrefs, would it?

Visretain is set to 1. It always is (in the templates) . What are the possible impact´s of that, other than the obvious?

One part of The mystery lies in the fact that xref´s have been automatically added to all view files that previously had at least one xref, not for example P&ID-files that are drawn in views and does not have xrefs.

The other part of the mystery is that the added xrefs are not the same in all view files. Not all existing constructs are added, only some of them.

More thoughts?

[barbara.schurig]

Hi,

I would suggest storing the project local on any workstation and saving it to the virtual server as backup daily.
The behavior you describe is very strange and I didn’t see something like that happening with PN, since I use ADT 3.3. So I assume something went wrong with the virtual server.
Is it possible that antivirus software checks the files during the copy process?

Please let me know, if there is any question.

Regards,

Barbara

[gunnar_larsson]

Thanks Barbara.

Storing the project locally is not an option when working 35+ engineers from 4 disciplines on the project simultaneously.

We have a NAS which stores backups of all files and versions twice a day for a month back.

When the problem occurs we can recall filles via previous versions in properties. It´s a neat feature.

The NAS was installed some six months ago and since then the problem has occurred twice, never before.

I can´t help but suspect that the NAS might be the root of the problem somehow. However, I don´t have the knowledge to investigate further, so I´ll leave it here, fingers crossed it won´t happen soon again.

[barbara.schurig]

Dear Gunnar,

Thank you for your update on this.
I’m glad to hear that this issue didn’t occur again in the meantime.
And I would like to add some information. Working local on one project with so many people, for sure that would not work so well. But in general and related to the network conditions, it should work fine if the project is saved local on a workstation and the folder is shared with the team.

I had brood over this issue once more and another idea came into my mind. Is it possible that at one system is a tool or application loaded that need to turns on all layers for special commands?

Best regards,

Barbara

[gunnar_larsson · Accepted solution]

Aha, You mean to basically duplicate the server setup but using an ordinary workstation instead of the V-server, and doing manual backups? I would have to copy the entire uncpath for all projects and map as W:\ by startup script, not to confuse the users or the rest of the system.

It´s a thought. I think I´ll dwell on it a little though.

To my knowledge there is no app, script or command that turn all layers on automatically. And there is no script that would attach new files to others automatically, in fact on this project there is no scripting at all. I have chosen to use the PN especially to avoid scripting as much as possible.

I suggest we leave this, at least until it happens again and the problem becomes more acute.

Thanks for now.

[barbara.schurig]

Dear Gunnar,

Thank you for your fast answer.

If this issue occurs again, please update this thread.

Have a good day.

Barbara