Community
Hi Paul,
We have been experiencing this issue for over a year on and off so you are not alone. We got Both Autodesk and Microsoft involved who actually passed the blame on to each other which didn't help matters.
The first issue we had was when users were using AutoCAD. A user would open a series of 5 files from the file server, work on them, and save with no issues. Then we got reports that the user couldn't save their drawings because they were being accessed by someone else. We quickly worked out that if a second user was browsing to the server location of the files whilst they were in use, it would lock the file up. If the second user closed Windows Explorer, after a minute or so, the user could then save as normal.
We then found a post that hinted at file locks associated with SMB2 so we turned it off on the client machines and the issue went away, however speaking to IT,we get a lot of benefits from SMB2 so this is not an option to us.
Unfortunately it then came back but this time with Revit 2014 and 2015 in a different office. I too have just found the same link as you on the Autodesk Knowledgebase which we will try the suggestions on their and see how we get on. We did coincidently move the model from a Windows 2008 server to another location with windows 2008 server and we couldn't replicate the issue in the other site. The only way we could replicate was a user from the problematic site with a user from the none affected site.
I'm curious to find out if you are still in the same situation as you were or have you now fixed this as its one of those annoying issues that I want to erradicate...
Look forward to hearing from you!
P.S - We are using Windows 7, no XP. Our Revit installs are all x64 Bit. We have mostly Windows 2008 Servers, some are 2012. I'm trying my best to find a pattern to this but trying to get the users time and resource is proving difficult to say the least which is fair enough, but to fix it you also need their help.
We have been experiencing this issue for over a year on and off so you are not alone. We got Both Autodesk and Microsoft involved who actually passed the blame on to each other which didn't help matters.
The first issue we had was when users were using AutoCAD. A user would open a series of 5 files from the file server, work on them, and save with no issues. Then we got reports that the user couldn't save their drawings because they were being accessed by someone else. We quickly worked out that if a second user was browsing to the server location of the files whilst they were in use, it would lock the file up. If the second user closed Windows Explorer, after a minute or so, the user could then save as normal.
We then found a post that hinted at file locks associated with SMB2 so we turned it off on the client machines and the issue went away, however speaking to IT,we get a lot of benefits from SMB2 so this is not an option to us.
Unfortunately it then came back but this time with Revit 2014 and 2015 in a different office. I too have just found the same link as you on the Autodesk Knowledgebase which we will try the suggestions on their and see how we get on. We did coincidently move the model from a Windows 2008 server to another location with windows 2008 server and we couldn't replicate the issue in the other site. The only way we could replicate was a user from the problematic site with a user from the none affected site.
I'm curious to find out if you are still in the same situation as you were or have you now fixed this as its one of those annoying issues that I want to erradicate...
Look forward to hearing from you!
P.S - We are using Windows 7, no XP. Our Revit installs are all x64 Bit. We have mostly Windows 2008 Servers, some are 2012. I'm trying my best to find a pattern to this but trying to get the users time and resource is proving difficult to say the least which is fair enough, but to fix it you also need their help.
Hi Paul,
In a way, i'm glad we are not the only ones troubled by this and i do know that other regions are essentially having difficulties as well.
FYI, we also noticed a while back the issue with PDF's and Excel documents but these issues seem to have disappeared all of a sudden. The only issue we are left with is Revit.
Our way forward in my eyes is this...
A year ago we were supporting XP and Windows 7 on our workstations, to fix this, we turned of SMB 2 on client machines with Windows 7 so that everyone was talking to the Server via SMB 1 with Windows Server 2008 R2. Now that we have removed all instances of SMB 1 (removal of XP and upgraded to Windows 7 for all machines) we are going to force via Group Policy SMB 2 on all local Workstations in the problem site. Hopefully by doing this, the issue will be removed (Fingers Crossed).
If the above isnt resolved, at least this way we have a blank canvas to start from to troubleshoot.
I have asked our local team to look into the Worksharing Update Frequency in all versions of Revit and to confirm that all versions are affected with the file locking issue.
I believe to force the issue, if you were to pick another site, turn off SMB 2 on one of the client machines, get this person to work on the same model as someone else who has SMB 2 enabled, you should be able to recreate the issue.
From your post, you mention Windows Server 2012, can you confirm that the site with this server is all using Windows 7 or do you have some Windows 8 installs? If this is the case, this means you are supporting users running SMB2 and SMB3. Try to get them all on to the same SMB to remove the problem.
Its a shot in the dark but this is what i would do.
Hi Paul,
Ok, we have just done some testing in the problematic site experiencing this issue.
The server currently is Windows Server 2008 R2. Our Revit Users are all on Windows 7 x64
A year ago, our server was Windows Server 2003 and was changed to 2008 R2. Thats when the issues started and SMB 2 was turned of on the client machines. By doing this we created a mixed environment of SMB 1 and 2.
We got 3 people together working on a project, all three reported the locking issue. We checked the Protocols the machines were using... 2 were SMB 1 and 1 was SMB 2.
We updated the three to SMB 2 and restarted their machines. The testers opened Revit 2013 and 2015 and tested working with each other again, however this time there was no issue!
We then identified all other users working on SMB 1 protocols and added a forth user to the mix. So we had 3 users working fine on SMB 2 and added a user on SMB 1, issue cam back! Changed the forth user to SMB 2, restarted and all was working fine again for all 4.
As a suggestion for you, seeing as you are using Windows Server 2012 and have a mixed set of users on Windows 7 and 8. If i understand correctly, your Windows 7 users are using SMB 2 and Windows 8 are using SMB 3. Based on what we found above, all it would therefore take is one user with an install of Revit collaborating with others in the local site to cause the issue if they are using different protocols to the other Revit Users.
If you could possibly turn off SMB 3 so all Win 7 and 8 users use SMB 2, i would hope, fingers crossed that the issue disappears for you.
I beleive thats why when you put windows Server 2008 R2 in place, everyone whether Win 7 or 8 are forced to all use SMB 2 protocols.
Hope all that makes sense.
Can't find what you're looking for? Ask the community or share your knowledge.
Post to forums
