Save to central issues after installing updates

[Andre Baros]

Contrary to best practice, we rolled out a bunch of updates lately by having users individually install them from the Autodesk Application Manager. There was a bunch of new updates so we're not sure exactly which is causing the problem but we suspect Revit 2016 R2 or the latest update to A360 collaboration.

Since install, teams with at least one member who installed the updates are seeing save to central failures where Revit stalls on save reporting that the central file is already being accessed by someone, even if we can confirm that no one else is in the model. We've tested various ways and can reproduce the error but not consistently.

We also had a black out in our building the week before the updates and problems started but don't suspect that because only Revit 2016 is having issues. Revit 2015 and other software are all working fine on the network.

Has anyone else had errors with the latest updates?

Thanks,

[nathan.chapman]

I have seen a lot of issues when there is at least one member running a different service pack than others on the project. Make sure everyone is on the same service pack and once that is complete delete all old local copies and create a new central file. This will typically fix the issue. I have not notice anything with the newest updates on our end.

[Andre Baros]

Since the problem was only effecting Revit (both 2015 and 2016) we thought it must have been tied to the updates or A350 which affects both. Turns out it was a search tool we installed about the same time, Lookeen. We're not sure how it caused the problem but uninstalling it solved the issue.