Multiple users in multiple BIMs all get Access denied error around same time?

[Anonymous]

Hi guys,

The weirdest thing just happened. Today at around 11:20 am, EST,  all open Revit 2016 local models (about 6 entirely different project BIMs) in our Philadelphia office got the accessed denied .dat, & eperms error at about the same time.

The only way to solve it was to close everyone out of their locals, then rename/delete the central backup folder, then have everyone open their locals and sync.

New models opened soon after the initial occurrence did not see any issue.

Have you ever seen this on such a scale?

What would be the cause? Is this a symptom of something you’ve seen before? There were no Revit updates pushed to staff. And everyone is on build: 16.0.1185.0, 20161004_0715(x64), Update7 for R2

[Sahay_R]

Are you sure that everyone is sync'ing the same way using the Synchronize and Modify Settings button, and not Synchronize Now?

[Anonymous]

Thanks for your reply. It was confirmed to not be user error. Let me clarify:

This was 6 different Central models, with users experiencing the same "Access to <file url>.dat was denied" error to the 6 different .dat/eperms files when trying to sync. All local models that were already opened by that time were unable to sync, receiving this error. Most folks here use Worksharing monitor and don't sync while others are syncing and know enough to recognize that if they can't sync to check WSM. In this case, some projects had only 1 person in their local and experienced the issue, while other models had about 10 folks working. But everyone working on a local copy, with no exception, was unable to sync after about that time.

[Sahay_R]

Sounds like a worse situation than what had happened to my team! Good luck!

[Anonymous]

So we discovered, after the issue proceeded to get worse over a week and begin to effect other software, that a network component was failing. I'll add details on the unit if I get them.

[Anonymous]

I would love to hear more about what network component failed. We are running into similar issues where users are hanging onto permissions to the users.dat file in several central models. I suspect it may also be due to network failures.