Vectorworks cannot open or save files through NFS on Windows 10 desktop (standard Microsoft NFS v3 client install). This is a single user license running Vectorworks 2025 Update 3.1 (Build 796361) on an up-to-date Windows 10 Professional desktop. I'm the only user accessing these particular files through network shares on a Linux server (Ubuntu Server 24.04.1 LTS), which supports access to the same files through both SMB and NFS. SMB support will eventually be removed from that server, and thus I need to migrate to NFS.
1. If I open any Vectorworks file via SMB, Vectorworks opens and saves with no problems. If I try to open the exact same file through NFS, Vectorworks thinks for while and eventually reports "Unexpected end of file encountered during file read operation. (Failure on attempt to read file)". If I next try to open the exact same file through SMB, it opens fine. So there is nothing wrong with the file. If I then use Windows Explorer to copy the exact same file through NFS to my local Windows Desktop, the copied file opens fine in Vectorworks. Thus reading files through NFS works properly, but not with Vectorworks.
2. If I try a 'Save As' with any open Vectorworks file to write a new file through NFS to the server, I can see Vectorworks trying to write the file three times ("Writing file" at the bottom right). After that it gives up and reports: "An error occurred while saving this file. This file is now corrupt on disk. Try saving this file to a different location. If you close this file before you successfully save it, it will be completely lost." I then close the original file without saving it. The interesting part is the new file has actually been saved correctly through NFS, in spite of Vectorworks' complaint. In fact I can immediately then open the same new file via SMB with Vectorworks, and there is no problem. So Vectorworks was wrong - the 'Save As' worked through NFS. But I still can't open that new file through NFS with Vectorworks. Thus writing files through NFS with Vectorworks functions properly, but Vectorworks doesn't realize it.
There isn't anything peculiar about the Vectorworks file. The same thing appears to happen no matter what file I try. Restarting Windows and/or Vectorworks makes no difference. All other applications I've tried on Windows can access files with no problems through NFS. The server provides LDAP domain service for both SMB and NFS access. The user/group IDs are identical for both, and I've also tried setting these as entries in the files 'passwd' and 'group' on the desktop in C:\Windows\System32\drivers\etc. This is not a permissions problem, because I can copy files in both directions through NFS.
I have rummaged through the Internet and community boards. I see others have encountered similar or related problems over the years, but I can't find any fix, workaround, or any evidence that these problems were ever solved or resolved.
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
pendragon
Vectorworks cannot open or save files through NFS on Windows 10 desktop (standard Microsoft NFS v3 client install). This is a single user license running Vectorworks 2025 Update 3.1 (Build 796361) on an up-to-date Windows 10 Professional desktop. I'm the only user accessing these particular files through network shares on a Linux server (Ubuntu Server 24.04.1 LTS), which supports access to the same files through both SMB and NFS. SMB support will eventually be removed from that server, and thus I need to migrate to NFS.
1. If I open any Vectorworks file via SMB, Vectorworks opens and saves with no problems. If I try to open the exact same file through NFS, Vectorworks thinks for while and eventually reports "Unexpected end of file encountered during file read operation. (Failure on attempt to read file)". If I next try to open the exact same file through SMB, it opens fine. So there is nothing wrong with the file. If I then use Windows Explorer to copy the exact same file through NFS to my local Windows Desktop, the copied file opens fine in Vectorworks. Thus reading files through NFS works properly, but not with Vectorworks.
2. If I try a 'Save As' with any open Vectorworks file to write a new file through NFS to the server, I can see Vectorworks trying to write the file three times ("Writing file" at the bottom right). After that it gives up and reports: "An error occurred while saving this file. This file is now corrupt on disk. Try saving this file to a different location. If you close this file before you successfully save it, it will be completely lost." I then close the original file without saving it. The interesting part is the new file has actually been saved correctly through NFS, in spite of Vectorworks' complaint. In fact I can immediately then open the same new file via SMB with Vectorworks, and there is no problem. So Vectorworks was wrong - the 'Save As' worked through NFS. But I still can't open that new file through NFS with Vectorworks. Thus writing files through NFS with Vectorworks functions properly, but Vectorworks doesn't realize it.
There isn't anything peculiar about the Vectorworks file. The same thing appears to happen no matter what file I try. Restarting Windows and/or Vectorworks makes no difference. All other applications I've tried on Windows can access files with no problems through NFS. The server provides LDAP domain service for both SMB and NFS access. The user/group IDs are identical for both, and I've also tried setting these as entries in the files 'passwd' and 'group' on the desktop in C:\Windows\System32\drivers\etc. This is not a permissions problem, because I can copy files in both directions through NFS.
I have rummaged through the Internet and community boards. I see others have encountered similar or related problems over the years, but I can't find any fix, workaround, or any evidence that these problems were ever solved or resolved.
Link to comment
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.