Forums >> Workflow & Implementation >> Worksets >> Syncronization Issue

SwiftImage

active

Joined: Sun, May 30, 2010
9 Posts
No Rating

I have a strange syncing issue that I have run out of ideas on how to fix.  We have your typical central file with linked in consulatant models each on their own workset.  This morning I received an update to our structural model that I knew ahead of time was going to break a few things right off the bat.  After setting up the new model,  I opened the project and a few warnings and a few errors popped up as expected.  I did what I needed to ignore/fix the errors (thus gaiing control over those elements until I sync/relingquish).  I continued to update my model to suit the changes that structural had.

Before I had finished fixing everything and before I had a chance to sync and fix the warnings/errors, someone else in the office who hasn't been in the project for a long time (no owned elements at this point) tried to create a new local file.  When they tried to create the new local file, they got the same warnings and errors that I did.  Rather than ask me about it they starting to ignore and do what I had already done earlier.  They did something different on the warnings however and somehow became a borrower of the structural link.  When they got to the errors, their load failed because they could not get control of those until I performed a sync with the fixes completed.

Problem is when I try to sync, I get an error and sync fails because they own the structural link.  They cannot sync because I own everything else.  Any ideas?

-----------------------------------

~SwiftImage

This user is offline

WWHub

site moderator|||

Joined: Tue, May 16, 2006
13079 Posts

First thing - because you didn't say, we have to make sure that nobody is working in the central.  All of you are in local files, correct?

Do you control the linked model?  That is, do you save it in your directory then do a "reload from"?  We always add a date to the consultant file then use the "reload from" and pick the correct date. (Archive the old one).  In this manner, updates happen when we want them.

I suggest you have the other user quit and relinquish all, then you sync.

This user is offline

SwiftImage

active

Joined: Sun, May 30, 2010
9 Posts
No Rating

Everyone is using local files.  I keep close tabs on this project with the worksharing monitor just to be safe.

I also control the all the linked models.  I am the only one who manages the links, loads them (actually do it the same way you mentioned already), performs coordination reviews, etc.

The problem is that the other user cannot physically get local file created in order to perform a sync or relinquish.  After testing a little further right now,  I cannot even perform a reload latest because of this issue.  I have gotten everyone in the office to close it down to be safe right now at least.

One idea I have is to delete the link altogether from the directory it is in and reload from scratch (I would lose my copy/monitored elements, but I should be able to get everything back to now with a little time).  By doing this I would effectively be making it so the element that is causing the problem simply doesnt exist...

-----------------------------------

~SwiftImage

This user is offline

WWHub

site moderator|||

Joined: Tue, May 16, 2006
13079 Posts

The other user does not have to sync to relinquish.  Just quit and Revit will ask if he wants to relinquish.

Lets say he doesn't get that done but has quit.  You should be able to save local and close the project.  Or.... I suggest you use your model to create a brand new central and have you and everyone else create a local from that. 

This user is offline

SwiftImage

active

Joined: Sun, May 30, 2010
9 Posts
No Rating

Thanks for the adivce WWHub.  I ended up having to create a new central file based off my local file.  We "lost" about a days work a work on some users local files that had not been synced back (and could not due to the error).  We were able to open their local files and detach just as you would a central in order to make a backup copy of those files as well.  We then had everyone create a new local based off the new central file.  Everyone could then open their backed up old local and copy as much of the changes they could to the new one (took them about an hour to make sure nothing was missed.

I think the lesson learned on this was anytime you open the local file and get a warning or error message, go through the dialog to remove contraints or whever you have to, then sycn right away.  After the sync, go through the process of fixing or changing whatever you were going to.  This way, you can avoid getting locked out from things.

-----------------------------------

~SwiftImage

This user is offline

syncronization process

5

Syncronizing Issue

2

syncronization working

1

Issue date vs Revisions

4

Drawing Issue Record

3