Revit MEP

Reply
Contributor
xxjwilson
Posts: 14
Registered: ‎07-20-2012
Message 1 of 7 (1,281 Views)
Accepted Solution

Worksharing error: Can't create local copy without overwriting central first

1281 Views, 6 Replies
10-04-2012 09:20 AM

ISSUE: Worksharing does not work. I have followed the worksharing workflow to the letter.

 

SYMPTOMS: I created a model, turned on worksharing and saved as central model to our (local) networked server, that all users have access to. Once I close and re-open the model I am able to create a local copy, work on it and synchronize with central as normal. The problem comes when another user tries to open that model, a warning pops up that says the user must do a save-as back to the network and over-write the central, making the new one the central after save. Now when I try to open that same model, I get the same error message and have to perform the same steps. Thus the entire idea behind worksharing is null if we have to over-writing each others work.

 

Its as if only one local copy can be made at a time!

 

PLEASE HELP!!!

Are both of you mapped the same to the location of the central model?  Ex: both of you are using the same drive letter designation and/or the same UNC path?

 

If this is different it can cause the issue that you describe in your follow-up post (local copy box not being available).

*Expert Elite*
abulla
Posts: 358
Registered: ‎10-14-2008
Message 2 of 7 (1,269 Views)

Re: Worksharing error: Can't create local copy without overwriting central first

10-04-2012 10:19 AM in reply to: xxjwilson

It sounds like the new user is opening the central file, and not creating their own local. Have them click on the central file from the Open dialogue in Revit, and make sure the "Create New Local File" box is checked.

 

A good way to see if a user is working in the central file or their local file is by using the Worksharing Monitor add-in. Also, check the file name at the top of the screen when the file is open. If the file is appended with the user's name, then it is their local file.

Contributor
xxjwilson
Posts: 14
Registered: ‎07-20-2012
Message 3 of 7 (1,260 Views)

Re: Worksharing error: Can't create local copy without overwriting central first

10-04-2012 11:30 AM in reply to: abulla

Thanks for the response.

I thought this might be the case so I tried to walk them through it. The "create new local" checkbox is un-checked and greyed out, and cannot be changed,as if the file was not a "central" model.....but it is. 

 

 

Active Contributor
brettgatti
Posts: 49
Registered: ‎07-08-2001
Message 4 of 7 (1,256 Views)

Re: Worksharing error: Can't create local copy without overwriting central first

10-04-2012 11:38 AM in reply to: xxjwilson

Are both of you mapped the same to the location of the central model?  Ex: both of you are using the same drive letter designation and/or the same UNC path?

 

If this is different it can cause the issue that you describe in your follow-up post (local copy box not being available).

Contributor
xxjwilson
Posts: 14
Registered: ‎07-20-2012
Message 5 of 7 (1,247 Views)

Re: Worksharing error: Can't create local copy without overwriting central first

10-04-2012 11:50 AM in reply to: brettgatti

Everyone is mapped to the e drive on our server. However when mapping the drive, the letter e is not available, so we're all using the letter P for our project directory.

P:smileysad:\\server\e\)

The error message (attached) does coincide with this thought however.

Valued Contributor
TonyVav
Posts: 65
Registered: ‎11-13-2006
Message 6 of 7 (1,220 Views)

Re: Worksharing error: Can't create local copy without overwriting central first

10-07-2012 03:17 PM in reply to: xxjwilson

After opening the central file you can "save as" to the local user drive. Thus creating a local copy to the central file.

Contributor
xxjwilson
Posts: 14
Registered: ‎07-20-2012
Message 7 of 7 (1,209 Views)

Re: Worksharing error: Can't create local copy without overwriting central first

10-08-2012 05:36 AM in reply to: xxjwilson

I believe this was the answer. Some of our mapped network drives were named using the IP of the drive and others were mapped using a directory path, even though the destination was the same place, having conflicting naming cuased the problem. It all appears to be working as expected now.

Thank you for the assistance,

Post to the Community

Have questions about Autodesk products? Ask the community.

New Post
Need installation help?

Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.