Announcement

Collapse
No announcement yet.

Unable to Access the Model

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Unable to Access the Model

    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?
    Attached Files

    #2
    Just to cover all the bases:

    1) Verify everyone has the same Revit build.
    2) Verify that the permissions are set properly in the project folder.
    3) If this is happening with every model and every Revit version, then it could be an SMB issue. Make sure all of the files servers have the same server OS. We have workstations with multiple OS (W7 and W10), so I am not aware of OS incompatibility issues.
    Otherwise, rebuild all of the models with the Audit box checked?

    4) Verify if there are any new processes: backup/archiving/virus scanning on the file servers, assuming this is a new situation.

    Good luck!
    Last edited by Markus; July 19, 2017, 04:30 PM.

    Comment


      #3
      Verify your network connection too....are you running 1000mb or 100mb?
      Michael "MP" Patrick (Deceased - R.I.P)

      Comment


        #4
        I started a similar discussion last week here:
        https://www.revitforum.org/architect...ess-model.html
        No answers, though.
        Dave Plumb
        BWBR Architects; St Paul, MN

        CADsplaining: When a BIM rookie tells you how you should have done something.

        Comment


          #5
          I've seen this in 2017 if the file is open on a machine that's not being used (like in a conference room after a meeting). If anything had been done that Revit would consider to be an edit and the file sits there without being synced or closed then this message would come up on the other machines. Closing the file would make the message go away.
          Rick Moore, AIA
          Barnes Gromatzky Kosarek Architects

          Comment


            #6
            That should give you a "You cannot edit this element because it is owned by someone else" message, (or whatever it says).
            It should NOT gice you the warning above and prevent you from accessing the model AT ALL.
            Dave Plumb
            BWBR Architects; St Paul, MN

            CADsplaining: When a BIM rookie tells you how you should have done something.

            Comment


              #7
              It gives the exact message from above in 2017, I've been able to repeat it. Each time it was from someone leaving an unsynced file open for a long time.
              Rick Moore, AIA
              Barnes Gromatzky Kosarek Architects

              Comment


                #8
                Thanks all.

                We've tried these already:
                • Set all machines' "Worksharing Update Frequency" to "Manual".
                • Disable SMB V2 & V3, allowing only V1 connections.
                • The server is a Win2012, and only a file server, not doubling as domain server. Checked that there are absolutely no other processes running on it - only sharing folders.


                At first I tried the update frequency only on one machine, that didn't help. Then I got all to set their update frequencies to manual. Still no dice. Then I rand the disable V2 & V3 commands at the bottom of this page (Steps to Enable and Disable SMBv1, SMBv2, and SMBv3 in Windows Servers) on one machine, then all. Still same issue.

                Re the suggestions:
                • I'll make sure the exact same updates are installed on all. Not exactly sure about this, but should all be to latest, we're pretty adamant about keeping all as updated as possible here.
                • Permissions are definitely fine, the problem is intermittent, so the user getting this issue can then later continue without the dialog popping up. All of the users can at some point work without this problem, then just as they carry on working (i.e. NOT synchronising but drawing a line, a wall, anything) this error happens, not every time, just enough to irritate the user (i.e. every hour or so).
                • The Windows incompatibility is actually about that SMB stuff, later Windows' use different versions by default, and file locking between different SMB versions sometimes do not work well. So a W7 machine may default to using V2, while a W8 and W10 may default to V3 instead, while some other (like XP, though we don't have those anymore) may only be able to use V1. It's "supposed" to handshake with the server about what is the least common denominator, but "supposed to" only happens in an ideal world. As stated above we've already disabled V2 and V3 on all the client machines, so all should be using V1.
                • Network throughput on all computers is 1Gb/s, though the network switches vary from 1Gb/s through to 2Gb/s with multiple routes into the server (which itself has 4 off 1Gb/s LAN connections).
                • There's 6 people working on this model concurrently. Made sure there's no other opened sessions anywhere. Checked even on the server to make sure nothing else is even looking at the file itself.


                I'll keep trying and investigating here, even go through the server logs. If I do find something I'll revert, but so far I'm finding this completely baffling.
                Last edited by irneb; July 20, 2017, 11:33 AM.

                Comment


                  #9
                  Originally posted by DaveP View Post
                  I started a similar discussion last week here:
                  https://www.revitforum.org/architect...ess-model.html
                  No answers, though.
                  Sorry, I did try to search for something similar. Really not sure why I didn't spot your thread, especially as their titles are near exact replicas.

                  Perhaps a moderator could merge these two threads?

                  Comment


                    #10
                    Irneb,

                    Just curious if you are able to resolve the issue already?
                    Philip Chan
                    Practice Technology Manager | HKS
                    http://phil-osophyinbim.blogspot.com/

                    Comment

                    Related Topics

                    Collapse

                    Working...
                    X