linked models unloading

[eric.piotrowicz]

We have a workset project with three users. If a new link is added while multiple users are working then we get some strange behavior as follows. We are using 2010 with all updates.

User 1 links a consultant model and it loads without any issues and then does STC
User 2 does STC and the new link is not displayed, in Manage Links it shows as not found
User 1 does STC and now the link in shown as unloaded in Manage Links, Reload and STC
User 2 does STC and the new link is not displayed, in Manage Links it shows as not found
User 2 does Reload From and STC
User 1 does STC and the link stays loaded
User 3 does STC and the whole stinking game starts over :banghead: :banghead:

The only way I've found to load a link is to wait until after hours so I am the only one working on the model, add the link and STC. Then go to each user's computer and create new local files.

Has this happened to anyone else? Am I doing something wrong?

[twiceroadsfool]

They work fine over here when we add them, except for some completely unrelated issues surround the Links being set to By Linked View. But its certainly not this problem.

1. Are all of the users pathed to the networked drives in EXACTLY the same way? Ive seen this issue creep up when user 1 is pathed by "...\\xdc2\Job105\Model" and user 2 is pathed "Z:\Job105\Model" and so on.

[eric.piotrowicz]

There have been some odd network pathing issues around the office on some of the newest machines. I though the three on this team were all matched but I might have to look into that possibility again.

[mholzer]

I had some issues with links unloading and I did this:

In Revit go to File - Open and browse for the consultant Revit model you are wanting to link. Check "detach from central" and open the consultant model. Now save and close the consultant model and try to link it into your model again. This kept my consultant model links from being unloaded.

[twiceroadsfool]

There have been some odd network pathing issues around the office on some of the newest machines. I though the three on this team were all matched but I might have to look into that possibility again.

If theyre not identical, this issue will keep rearing itself, in my experience...

[eric.piotrowicz]

Thanks Aaron,
It turns out that one machine had the file server location in the path and the others were pointing to the mapped drive letter. Even though both paths are recognized in Explorer on all machines and take you to the correction location, it appears that Revit is a bit more picky about the path.

[twiceroadsfool]

Revit is picky, LOL. We learned the hard way when a critical Server rebuild occured and Eye Tee (stolen from Mr Stafford) didnt name the Drive on the Server the exact same way it was before the rebuild.

Holy nightmare. Every worksetted project thought it was a local copy, LOL.

[patricks]

Revit is picky, LOL. We learned the hard way when a critical Server rebuild occured and Eye Tee (stolen from Mr Stafford) didnt name the Drive on the Server the exact same way it was before the rebuild.

Holy nightmare. Every worksetted project thought it was a local copy, LOL.

whoa nelly!!! :shock: :p

This is where network domains and login scripts come in handy. Everyone always gets the same mapped drives when ever (and where ever) they log in, and everyone's Revit is set with all default network paths (default user path, libraries, etc) pointing to the locations on the mapped network drives. Much more stable between users than the \\server\share file location.

Even my VPN connection at home is set to map the same Z: folder as the one at the office, so everything plays nice when working on a workshared project at home with the local file at home and SWC thru the VPN connection.

[twiceroadsfool]

Yeah, its been a fun few months since that happened. LOL. :)

[Steve_Stafford]

whoa nelly!!! :shock: :p...
This is where network domains and login scripts come in handy. Everyone always gets the same mapped drives...Revit doesn't pay any attention to drive letters, it is focused on the UNC naming of the server and its shared resources. You can use any letter you want. If the server name is different or the folders change...Revit thinks the central file is "changed" and now a local file.

[psteel]

We have been having this problem as well and still cannot fix it.

There are couple of issues here:-

1. When the structures guys send us the file they detach a copy, purge
etc and then send us the file. If the guys doing the detach save the file to
their server, we see there link in our Linked Revit Files dialog box. Therefore
on STC over eight machines the file unloads etc

2. Over the eight machines local alias's are being generated for the linked file??????

3. The suggestion of detaching and resaving once recieved is ok if its
an Architectural model but not if its Structuraland if you do not own a copy of Revit Structures

4. Even tried locking the Structures import file but to no avail.

Surely the factory is aware of this ?????????

Greetings from London

[eric.piotrowicz]

Not sure why you couldn't "Open and Dettach from Central" with your engineer's models. I can open them and dettach and save using Revit Architectural 2010 and we do not have any copies or licenses for Revit Structure or MEP. Although I can't really work on any of our engineer's models when I open them with RAC I can't think of any reason I would want to be able to edit them, seems like a recipe for disaster.

[violet78]

3. The suggestion of detaching and resaving once recieved is ok if its
an Architectural model but not if its Structuraland if you do not own a copy of Revit Structures

Greetings from London

As I understand it, Revit is all one program, only the tools available vary from one type to another (Arch vs. Struct vs. MEP). The file format is still the same. I have opened structural files in Revit Arch with no problems.

[ppaige]

I'm not really certain that this problem falls into the same category, but all of my Revit links keep unloading every time I load in / reload a family. Needless to say, but it's driving me crazy.