Hi there,
I am having an issue where Revit 2017 r2 crashes while attempting to synchronise. We have the latest build installed on all machines, however the crash seems to be occurring from 2 users machines. REvit allows the saving of a local recovery file, however when opened this wont synchronise either.
I have found 2 warnings in the journal file which don't sound right:
0:< DBG_WARN: Pathname of WorksetConfig should not be empty. Something is wrong with Revit.ini!: line 244 of MFC\ARecentFileList.cpp.
and
' 2:< 0 ModelServerState "Destroyed": Current server = "Not Queried", Model server = "", Model server state = "Not Applicable"
' 2:< DBG_INFO: [TKY] Not sure which partition borrowed element -1 (original 4145317) came from. Probably need info from central model rather than using local info. Try Reload Latest Worksets.: line 2266 of d:\r2\2017_px64\source\revit\revitdb\permissions\EditingPermissions.cpp.
' 2:< DBG_WARN: The status of system workset 'Family : Spot Elevation Symbols : Anno_Spot_Elevation_Target_Filled13' should be statusUpdating: line 162 of D:\R2\2017_px64\Source\Revit\RevitDB\Dialog Interface\Worksharing\WorksetMgr.cpp.
Second issue that seems odd, Revit requires users to synchronise a second time when closing a file, even if the user has just synchronised a few moments ago, and the "relinquish the following worsksets and elements boxes are greyed out" as well.
Any advice would be much appreciated.
Thanks for your reply, we do have quite a few apps installed, and we were going to try running with apps disabled as a next step. On the advice of our IT support we tried overwriting the users local ini files which seemed to stop the crashing during synchronising. We had a few more crashes during the day (not while trying to synch as before) , and resorted to reinstalling Revit on the 2 problem machines, and so far today the file seems to be stable. We are now waiting to see if this has resolved the issue. While this hasn't exactly isolated the issue as hoped, it has resolved it for now.
Additionally, get the two problem machines cleaned out. Locals deleted, temp files and recycle bin too. We have had this happen a lot and cleaning out the offending machines has been helpful.
Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.