Using RVT 2017, workshared RVT file, not on RevitServer, file shared on Win2012 server in domain login.
I'm getting this sort of issue again an again. And no I don't mean the "file is being accessed by someone else". Here's a screen capture of the actual error message:

This happens during any edit. Draw a line, move a wall, create a dimension ... error shows for a few seconds to minutes, then disappears and the edit completes.
Under the "How to resolve" link I get the usual suggestions of turning WorkSharing to manual, and uninstalling SMB V2 & V3. Though after trying the various fixes this is still occurring.
The file IS available, I can actually browse to it at the very time this error dialog shows. And it's not only happening to me, several others are experiencing this. And also not just on one single RVT file, but several.
There are various windows versions in this office. I'm on W8 at the moment, but there may be others on W10. But I thought that was the reason for disabling the incompatible versions of Windows's file sharing (i.e. SMB V2 & V3). Anyone have any sort of further suggestions on what could be causing this issue?
I'm getting this sort of issue again an again. And no I don't mean the "file is being accessed by someone else". Here's a screen capture of the actual error message:
This happens during any edit. Draw a line, move a wall, create a dimension ... error shows for a few seconds to minutes, then disappears and the edit completes.
Under the "How to resolve" link I get the usual suggestions of turning WorkSharing to manual, and uninstalling SMB V2 & V3. Though after trying the various fixes this is still occurring.
The file IS available, I can actually browse to it at the very time this error dialog shows. And it's not only happening to me, several others are experiencing this. And also not just on one single RVT file, but several.
There are various windows versions in this office. I'm on W8 at the moment, but there may be others on W10. But I thought that was the reason for disabling the incompatible versions of Windows's file sharing (i.e. SMB V2 & V3). Anyone have any sort of further suggestions on what could be causing this issue?
Comment