Creation of local file and synchronization error

[wongkuanwei570223]

We are currently working on a huge project (200k sqm), single building and we have segregated our model into multiple files (basement, upper levels, documentation, site) for better management of file size. However, as we are moving deeper into the job, we seem to have some issues with creation of local files (greyed out at times) and synchronizing (often fails). Anyone out there facing similar issues or have any valuable advice?

[Brian Myers]

We used to have the issue with grayed out local files. It had something to do with not all the users pathed the same way to the file.
http://revitclinic.typepad.com/my_weblog/2010/10/why-is-create-new-local-grayed-out.html

In a few of our 2012 projects it also seemed to occur if one user was using Revit MEP, saved the file, and another user tried to open it in Revit Structure. My guess, it's related to the user path mentioned above.

[david_peterson]

We've run into this a few times on my current project. We've noticed it more when we get more than 6-7 people actively working on it. We also have a bunch of people that were using RDP machines that we were thinking caused the central file to "stall" for a moment. If the user waited a few mins and tried again, it seemed to fix itself.

[MikeJarosz]

According to Autodesk tech help, R13 and R14 handle linking differently internally. We were having nasty sync problems in R13. Links were being constantly unloaded when remote locations saved, then the sync would fail, leaving us with a crippled CF.

The solution was:

1) Use UNC filenames for all links. A pain - but it solved the problem
2) Insert the link to the central file directly, not from a local.


The users will all have to get out while you work with Central, and all will have to make new locals, but these two steps solved the problem. Apparently, if the link filename is not exactly the same at all locations, Revit gives up and unloads the locals.