We have an issue with our keynotes. We have a very eloborate building so we decided to put the stone skin in a separate model. We assigned keynotes to the stone families. The master model that contains all the linked models (skin plus consultant models) and interior architectural elements allows us to keynote the stone families in wall sections. It works better than in previous Revit releases where we were forced to use user keynotes. However, there is a problem when worksharing and keynoting at the same time. For some reason errors pop up when someone keynotes a linked element and we're forced to all save in a specific order (employee 5 needs to save, then employee 3 needs to save, then 1, then 4 etc etc.) It consumes large amounts of time. I've attached the error report also. The error report suggests that the keynote files are not the same, however, after checking both models both file paths are the exact same. Let me know if you think I'm doing something wrong.
To better understand why this issue is happening, please refer to the link below:
Hope that helps!
Has anyone had success fixing this problem? I checked the link, but didn't see where it's addressed.
We are currently having the same issue as bderrick.
We have a Model (Model A) that has another model linked in (Model B). Both models share a keynote file. When we're in Model A, and use an element keynote to call out something in Model B we eventually get errors saying the User 1 can't sync becuause User 2 owns a sheet. User 2 can't sync becuase User 3 owns a sheet, and so-forth. We end up having to sync in order, and it takes a lot of time.
We're also finding that Model A keeps unloading the keynote file.
We're to the point where we're going to start user keynoting Model B, because it's just not worth the hassle unless we can get this fixed.
We are encountering the same issue as the original poster if we tag the link with anything other than User keynotes. The link http://revitclinic.typepad.com/my_weblog/2012/03/w
Multiple users who have not been keynoting and who have NOT touched the sheet or any view on the sheet referenced in the Synch error message are getting the same error in a strange daisy-chain order.