We have a reoccurring problem in Revit Server 2012 and it involves linked Revit files.
We have 1 central as 4 local servers with 4 models on the server. These servers are only serving this single project, the central is a dedicated box and serves nothing else.
We have been getting errors involving the workset that one or more of the linked files are loaded on. Revit displays a warning that the workset is out of date and cannot be reloaded. There appears no way around this except to recreate a new local. After this has occurred a few times we have gotten the error
Element XXXXX is corrupt you need to save a recovery file. When you go to save the recovery file you get another corruption warning with a different ID number and Revit crashes badly, no recovery no error reporting, just goes away with a dialog “serious error has occurred and Revit must exit.”
No matter what we do we cannot open these files. Yesterday we finally got a detached one to open after multiple attempts and audits. Not sure what happened but Revit unloaded the bad link and we were good.
Couple of questions
- How does this happen? We don’t have a good understanding of what happened to avoid it in the future
- If it happens again how do we get Revit to drop the link?
- On non-server files renaming the linked file or moving it somewhere else corrects any issues with linked files. When we deleted files from the server we got “Server Error “and the file again refused to open.
Has anybody else seen this? Solutions? avoidance?
How does this happen? We don’t have a good understanding of what happened to avoid it in the future
Like any Revit file workset can get out of date. Depending on how the files are linked together and when a link or local copy was last opened. I would make sure that all user are cutting new locals when they open a file. Opening a local that was synced in a few days or even hours (on a busy project) can cause issues.
If it happens again how do we get Revit to drop the link?
See this link for details.
Hope this helps and thanks for posting.
The problem is we were creating new locals. The creation process was where the crash was occuring.
I looked at your link, but that realy was not the problem. It appears there was a problem with one of the links in the file, the linked file itself was fine and opened normally. We could not get Revit to ignore the link in the file. We tried locking, moveing and finally deleting, All we got was "Server error" and the main file never opened.
After detaching the file and trying numerous times to open it detached, someone double clicked it and it opened fine but missing the corrupted link.
So my follow up question is how do we open a Revit server file with links also on the server and have Revit ignore the linked file?
I passed this one by one of our Revit Server developers and here's what he said.
If you can open the host successfully, you can unload the link in the host. However this may not work if Revit has issues resolving the link. In that case, try temporarily archiving the model folder for the link and removing it from the host entirely. If you do this, Revit will find that the link is not present when it tries to resolve it, and it will simply move on. At that point you could unload the link in the host (Sync with Central to save the state.) Then you could restore the model folder back to the host to continue the investigation into the state of that linked model, with the host now completely decoupled from it.
Let me know your results.
We finally got that to work but we are not sure how.
Mostly we just got "Server Error" when trying to open the files after archiving and deleting or moving the files on the server. Only after double clicking a local did we finally get a missing links dialog and the file opened.
Is there a trick to working with linked files on the server? should be even try to use linked files on the sever? This seems to be where we have issues frequently.
Our current hypothsis is that one team member detached his local files from the server but did not repath the links and after that all the server files fell apart and had numerous lock errors. Prior to detaching we have had almost no issues with the server files. Can you give us some best practices (besides recreating locals) for managing linked files and or not using links on the server?
Is this any different on the 2013 server?