Today I'm having trouble syncing changes with a project and this dialog has been stuck on my screen for about a half hour so far.
It's the fourth cycle of trying to Reload Latest... I think after a second failure to sync it should exit more elegantly. At this point I'm wondering how many times will it try before giving up? There is no option to quit or cancel...just stuck with forcefully quitting Revit at this point? That's polite.
4 comments:
Following this post to see if you figure out anything to help. Experienced this pretty heavy the other day on a project with a lot of users in one file. We resorted to scheduling the sync times which helped.
Have a CLOSE look at any applications scanning your resources (anti-virus, mirroring and backup). In this case it appears that Trend Micro is interfering with the cache creation/update for projects when they are being opened and/or sync'd.
We've got all AV and scanning off; both on local machines and on our backbone infrastructure and we're also experiencing massive slowdowns. Sync speeds average at about 30-50kbps yes, that's kilobits.
A support request to Autodesk got the response "your project is too large".
Blaming everyone (including standard Windows operations that every other software platform plays nice with) and in particular blaming your CLIENTS for making project TOO LARGE (we're talking a 350MB RVT file here, that's NOT large!) is not the kind of response I expect from Autodesk, considering how much money B360 costs. If it was free? yeah, sure no problem.
Have to admit that we really "wanted" to put the "blame" on Autodesk for this but it seems that the AV tech deployed (for this client at least) is "responsible". Their scanning processes are interfering with data transfer and access. Trend Micro is the primary tech among others here. Since they've separated the cache locations from scanning actions normal behaviors has returned.
Work to remove everything between your computer(s) and Autodesk servers and slowly add them back in to see if/where the delays occur again. It was necessary to do some "close packet sniffing" to pin things down. Good luck!
Post a Comment