HELP! Revit cannot reconcile differences!!!

[gnarkill283]

We have a deadline in our office this week and every single day we've had the following two messages appear: "Revit cannot reconcile the differences between your local file and the central model. You can find more information about the errors in the Worksets dialog" - this happens when we try to reopen our local; "Revit cannot synchronize this file with the central model, because the central model was rolled back to a prior version of the project" - this happens when we try to sync our local.

Today it happened 3 times! We lose hours of work as well as additional time searching for the most up to date local/central model to recreate a central from. We've had this happen previously in the past but much less frequently so we mostly lived with it. We are using 2017 now though and we noticed it creates a conflict copy every time this happens in the central file directory. I've found nothing definitive looking at worksets and searching on the internet.

Our new team member mentions they had a similar problem in his old office where this happened and it turned out to be something with the server. The path would not be a direct drive path and revit wouldn't be able to find the central so this error occurs. He mentioned that making the path a universal naming convention fixed the problem or something like that - I'm not a techguy so I'm not sure if any of that even made sense.

Could this be our problem? Or is it something else. Please help we are losing countless hours of work do to this mess.

[gnarkill283]

I should note we have another project in 360 in our office which hasn't had this problem.

[Kimtaurus]

Don't reopen the local file, always create a new local from your central file.

The problem in your case is the differences between local and central have become too large (from not syncing often enough or closing without syncing).

you best bet is to rename your current local, create a new local from the central.

Open the old local using detach from central and copy the needed elements to the new local.

[Kimtaurus]

"Our new team member mentions they had a similar problem in his old office where this happened and it turned out to be something with the server. The path would not be a direct drive path and revit wouldn't be able to find the central so this error occurs. He mentioned that making the path a universal naming convention fixed the problem or something like that - I'm not a techguy so I'm not sure if any of that even made sense."

If the name of the server is differenct for different users you get a warning saying the central has been moved. So I don't think this is the problem, though you can easily check this by checking the server's name on the different computers.

[gnarkill283]

Thanks but we already know this. We all are opening new locals every morning and its still occurring.

[Kimtaurus]

Have you tried creating a new central?

Open the current central, detach from central while preserving the worksets. Save as a new central (and compact the file while you're at it).

Have everybody make new locals from this central.

[gnarkill283]

Yes we've done this about 6 times in the last 3 days

[treyk]

Hi Daniel--

Can the issue happen immediately after creating a new local from the central file?  i.e. 1) open central, 2) create/save new local, 3) draw a wall in the new local, 4) SWC... then you can get the "Can't reconcile" error?  Or does it happen only after a long worksession in the local file?

You mention opening a local file... and I agree with Kim--you shouldn't ever do this.  Sounds like you're not though.  Your further comments say that you guys always make a new local from the central.

Two other possible problems (both of which you're probably not doing, but it's worth mentioning because they can really piss off Revit and cause issues like you're experiencing):  

A) Make sure that there aren't two computers on which the Revit users have signed in with the same user ID; and

B) Make sure that somebody isn't simply opening the central file and working in it directly (instead of creating a local file and working in that).  Open the central via File > Open > File Open dialog has "Create new local" checked by default, but opening via double-click on the Recent Files page doesn't create a new local automatically, so it's easy to get mixed up. 

If none of this helps, it would be helpful for me to look at your Revit journal files from sessions in which you experience this.  If you need help finding these, I'm happy to give you further details.

Thanks,

Trey

trey.klein@autodesk.com

[gnarkill283]

So it looks like we found the solution to the age-old problem of corrupt revit central files. Revit was mixing up locals opened with a drive path with locals opened with a UNC path. The solution is to find the UNC path by opening your existing local and going to the collaborate panel and clicking on “synchronize with central” drop down menu and clicking sync and modify settings. Then copy the contents of the central model location. Then click the Revit icon in the upper left, click open, and paste the path into the file name box in the new prompt. Hit enter and you should be in the central file directory. Save this path by right clicking on the left panel and adding current folder. Now every morning you should open revit first and click on the Revit icon>open>click on the shortcut and open the central file by always creating a new local. This goes for all server based revit projects. AFAIK 360 doesn’t need to worry about this.

PS - This is what I wrote to my office so it might sound a little strange here

[Anonymous]

So in the case of the lost production, is there a way to reconcile that information? If so, could someone please provide the steps?

Daniel

[gnarkill283 · Accepted solution]

Scratch that - problem was never resolved even 5 months later with trying solutions from the reseller but today we may have finally cracked the case. Apparently our server is Linux based and uses a product called Egynite for replication on the cloud. Instant replication could be causing issues with the central file. Changing this setting will hopefully solve our problem.

[PeterHobbsArchitects]

Gnarkill283 We are having the same issues and are also using an Egnyte Cloud Server. Did you find that changing the settings resolved the issue and if so could you please advise what the settings changed were. 

[Anonymous]

We have been experiencing this on Revit 2020.1

Are you signed in as the same user on multiple computers?

Are you using the same 3d view ie "3D View: {3D - userxx}?

This was our issue. 

We resolved this by making sure all users were signed in on a unique user account

[Hedraki]

This also could be caused but not using same version of Revit updates,  means if one machine it updated to 2020.1 all the other machines need to be using the same version / hotfix.  please update frequently

[gaaraj]

That was exactly the problem I had - Thank you!