Local Changes Not Synchronized with Central window when closing Revit

Local Changes Not Synchronized with Central window when closing Revit

Anonymous
Not applicable
2,916 Views
9 Replies
Message 1 of 10

Local Changes Not Synchronized with Central window when closing Revit

Anonymous
Not applicable

Hi all, 

 

My team is working on Revit 2017.1. They sync regularly to the central file but every time they need to close revit (after synching), the "Local changes not synchronized with Central" keeps showing.

 

I checked the History and files are correctly saved and synched at the first synch and at the last synch (the one after trying to close)

 

Is this happening to many others? I believe it's a glitch, but I want to make sure I am not missing something....

 

Thanks!

 

0 Likes
2,917 Views
9 Replies
Replies (9)
Message 2 of 10

Alfredo_Medina
Mentor
Mentor

Check the current settings in "Synchronize and Modify Settings", and try again.

 

2016-11-10_18-41-35.jpg


Alfredo Medina _________________________________________________________________ ______
Licensed Architect (Florida) | Freelance Instructor | Profile on Linkedin
0 Likes
Message 3 of 10

John.Frank
Explorer
Explorer

We're having the same issue on one of our projects, but not all.  We've saved over the central, audited, purged and held our breath but have yet to understand what's going on.

0 Likes
Message 4 of 10

ddriver
Enthusiast
Enthusiast

Same here

Started on Revit 17.1 just last week (3rd week in Jan)

Continues on Revit 17.2

 

now for me personally is happening on 2016 on workset enabled project that has no other users. 

 

In both cases

  1. Synchronize and modify settings, check all that can be checked except compact file.
  2. Close file action throws up "Local Changes Not Synchronized with Central" etc.

If I ignore the close file dbox as noted in 2, it does appear that my changes are saved...(simple tests)

 

Just curious if others are using BIMLink or not. (the only add-in I have been consistently using across projects where this is happening, though today I have not been using just to see, and it does not appear to make a difference.

 

0 Likes
Message 5 of 10

ddriver
Enthusiast
Enthusiast
0 Likes
Message 6 of 10

thomasarnoldsson5732
Enthusiast
Enthusiast

I have the same issue with old projects that has been upgraded to 2017. Not i projects started in 2017.

 

Any solutions to this yet?

0 Likes
Message 7 of 10

ddriver
Enthusiast
Enthusiast

I had one file that was doing this,

the whole open/detach/audit/saveas/compact routine did not work 2x

then along with some (minor) clearing out of warnings the file was working again.

then two weeks later is went back to the synchronize on close even through it was just synchronized - even if I was the only one that had a local file open.

 

questions:

1) does your office use any third party (non-autodesk) plugins?

if so - any anomalies with their licensing?

2) how many warnings are in the file

2b) in particular do you have

     A) the "over 20 miles" warning typical of a background civil dwg?

    B) multiple "line is slightly off axis" - particularly in topo surface subregion sketches?

3) what version license manager are you using?

4) Did this start happening in 17.1 or 17.2? - and which are you using now?

 

thanks

0 Likes
Message 8 of 10

SerhanB
Advocate
Advocate

We are having the same issue with one of our central files among eight of them. Others close just fine. I'd very much like to hear about a solution as well. Thanks.

Serhan BAKIR
http://www.stand.com.tr/
0 Likes
Message 9 of 10

ddriver
Enthusiast
Enthusiast

I have received no better help than "clean up your warnings"

 

Please look at the questions I posted.

if you can answer these it may help track where this is originating

thanks

0 Likes
Message 10 of 10

SerhanB
Advocate
Advocate

Recently I had an error stating "too many elements are missing..." so I reverted back to a previous version of the model with "restore backup" tool and afterwards started having this "local changes..." dialog box problem. Model restored fine but database somehow corrupted causing this error I guess.

Serhan BAKIR
http://www.stand.com.tr/
0 Likes