Hello. We are having some trouble since we updated to Autocad 2017 at work.
Sometimes we open a file with full rights for edition and if a workmate opens the same file later, the "DWG file is currently in use or is read-only" doesn't show up. The 2nd user will work normally and save the file without any problem. However, the first user, after trying to save the file, receives an error message which doesn't allow saving it.
This leads to a process of merging the work of the two of them, which causes a lot of problems. We have to be very careful if we don't want to lose any information.
I'd really appreciate some help with this issue.
Thank you!
Joaquin
Solved! Go to Solution.
File locking is handled exclusively by the server operating system these days. Acad not longer has any internal file locking mechanism. Are you using a NAS for you shared drawings? A Linux or BSD server, or what?
As @jggerth says, you've got some server based issues. Get with your IT people on this.
If you are not running a pure Windows based file system, then you are on your own.
https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Autode...
https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/Suppor...
Source: I've been there, done that, and got the T-shirt. I've seen all sorts of strange issues when using non-compliant file systems. And I've seen non-compliant file systems work just fine too.
The file system is pure Windows. Nevertheless, this is a big issue for me if it transcends to the server.
I will check with the IT guy and post any solution if we find one.
Thank you very much!
Yes, on the server, which runs Windows Server 2012 R2.
The IT guy told me that it is SAN and BSD. And the problem might be solved after installing the last updates on the server.
I'll keep you updated.
SAN is Storage Area Network, and BSD is a unix-derivative operating system. At least that's what I familiar with the acronym meaning. If that is the case, and your Windows server is talking toi a SAN running a 'nix OS, that's likely the problem.
Hi again! It looks like the problem disappeared after installing the last update of windows server.
Thank you for your help anyway.
I've had users also run into locked files because they had the "Preview Pane" open in Windows Explorer and THAT had a lock on the file. Just something to keep in mind in case you use preview pane.
Can't find what you're looking for? Ask the community or share your knowledge.