an offsite co-worker is trying to open a central model but was not able to create a local file. BUT, when they created a detached file and preserving worksets and saved the file, they were able to create a local from the detached. Both the original central file and the detached file are in the same folder.
any clue why?
also, is there another way for them to work on a local? maybe copy local folder local file and backup folder from office pc to home pc and once done, copy all back to the office pc and then sync with central?
Gelöst! Gehe zur Lösung
Gelöst von SteveKStafford. Gehe zur Lösung
Are you opening it from 'recent files' start screen or open -> find file -> etc...?
there could be lots of reasons why your coworker was not able to create a local file. Could be anything from VPN access of the model, general internet connectivity, etc.
What version of Revit is your team using?
Was there any error messages?
While there is a way to work on a local copy that is not connected to the central mode, this workflow presents several problems. The obvious is if someone makes a change your remote co-worker will not see those changes.
Best option would be to have a cloud based model if possible. We have had trouble with models accessed on a server via a VPN connection.
@martijn_pater open - file
@Tom_Kunsman Revit 2019 - no error message, the 'create local' button was grayed out and it is a shared file. but when they created a detached, they are able to create a local from said file.
@Anonymous never had a problem using VPN. they are connected via direct connect.
Revit over VPN is not recommended. Just because it has worked until now, doesn't mean it is not the problem.
Remote desktop is a much better option.
When Create New Local is disabled it means that the network path is no longer compatible with other versions of the project. The person who creates the central file defines the path to the central based on how their computer is connected to the shared drive. If another person encounters a disabled Create New Local then their path is not the same as the other person's computer. When we are at the same office (inside the LAN) it means one is mapped via IP address and the other is probably mapped via \\server\folder\subfolder which Revit regards as different.
Working through a VPN complicates the situation and is inherently perilous because network latency can allow more than one user to borrow the same elements. The connection is too slow to notice that someone else has borrowed an element already. I routinely hear people saying but it's been working fine...unfortunately it just means their luck just ran out. VPN connections are fine (but really slow) for single user but fragile and perilous for more than one using worksharing.
Steve Stafford
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
@SteveKStafford that sounds about right the way the file is mapped. i just compared the 2 files. original is server mapped while the detached is IP.
thank you.
Howard
It sounds like they might be copying the central model to a different location. That might be why the option to create a local is grayed out.
Just to clarify exactly what is happening can you describe the workflow being used to work at home?
@RobDraw what @SteveKStafford said about the different connections IP vs server based is the difference. I looked at each of the 'revit properties' for each file and the mapping is different.
so basically, my coworker still working from home is connected via VPN (IP based map) and working on a project. so basically, the project is now considered non-workshared workshare model.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.