If you are familiar with Revit Server at all, by now you know that you can no longer do a 'Save As' of a detached copy of your Central File and write over the existing Central File. Not a really big deal upon first glance, just make sure everyone SWC, gets out, you delete the CF from the Revit Central Server and then Save As a new CF with the same name. NOT SO.
Any Local Server (other than the one that the new CF was posted through) that has a 'memory' of that CF does not get updated with the new model! The first person in any other office that tries to make a new Local Copy will get a 'Revit Server Not Accessible' error. The only way to fix it seems to be to delete the folder that is named the same as the CF on the Revit Local Server(s): \\ServerName\RevitLocalServer\Cache\ProjectFolder\Proj\CFName.rvt
(in bold are the folder names that RS automagically creates)
But what if you have 4,5,10 local servers that are accessing this CF???:crazy:
Sure you can say 'just dont ever replace your Central File'. We are hoping that the promise of CF corruption is all but gone to be true but what about when someone screws up something big in the model. We have all heard horror stories of someone deleting a Level in an Elevation because they 'didn't want to see it'. Events like that neccessitate rolling back the CF or promoting a Local to be a new CF. Things you can't do anymore with RS.
If anyone else is running into this :banghead: and has some insight, please share!
Thanks!

Any Local Server (other than the one that the new CF was posted through) that has a 'memory' of that CF does not get updated with the new model! The first person in any other office that tries to make a new Local Copy will get a 'Revit Server Not Accessible' error. The only way to fix it seems to be to delete the folder that is named the same as the CF on the Revit Local Server(s): \\ServerName\RevitLocalServer\Cache\ProjectFolder\Proj\CFName.rvt
(in bold are the folder names that RS automagically creates)
But what if you have 4,5,10 local servers that are accessing this CF???:crazy:
Sure you can say 'just dont ever replace your Central File'. We are hoping that the promise of CF corruption is all but gone to be true but what about when someone screws up something big in the model. We have all heard horror stories of someone deleting a Level in an Elevation because they 'didn't want to see it'. Events like that neccessitate rolling back the CF or promoting a Local to be a new CF. Things you can't do anymore with RS.
If anyone else is running into this :banghead: and has some insight, please share!
Thanks!
Comment