Vectorworks 2018 Crack Get MacOS Linux Incl Windows Latest MacOSX

0 views

Skip to first unread message

Message has been deleted

Giselda Sasao

unread,

Jul 11, 2024, 2:49:14 PM7/11/24

to quaitoolmawho

I found a few similar topics on this subject but the solutions they offer don't fix my problem. In the past week or so, using both VW 2018 and VW2019, when opening many Vectorworks I get this error message about 50% of the time.

Vectorworks 2018 Crack Get MacOS Linux Incl Windows Latest MacOSX

DOWNLOAD >>> https://shoxet.com/2yLTCl

I have confirmed that no one else in the office has the file open and that permissions on the server are set properly. Because the problem seems to occur intermittently, I'm having trouble zeroing in on a solution.

Is this over a server? I have a colleague who inadvertently worked on a file on one computer that has Landmark installed, & saved it back to the server. He was then getting this error message when opening the file on another machine that only has Architect installed. His fix was to open consistently on the Landmark enabled machine. Perhaps there is another fix, but I'm not sure what that might be.

It is over a server and I suspect that has something to do with my problem. We only have Architect licenses in our office, so it's not related to a conflict with Landmark. Thanks for the suggestion, though!

I'm in a similar situation and have a windows server 2016 serving my data at the moment.

I get the read only error from Windows Samba shares, windows nfs share, and I'm about to try a Linux nfs share to test these files.

With the former, it opens but only in read only format.
I know that Macs from like 10.10 (I think) have a different version of samba to windows. Is this strictly a samba issue? What makes me skeptical is that it was also a problem via NFS on the windows server. Then again... Windows NFS is terrible as well.

Darn - I wish I could be of more help. On the Mac OS X platform, this would typically be a Permissions issue, but as you may have seen from my earlier posts, the problem wasn't resolved until I upgraded all of our computers to the latest OS.

I have an environment where all other apps do not have a problem though, only vectorworks which is frustrating.

I think that also because POSIX permissions are simpler and I think are more supported on MacOS, I've had to go for a linux server (cos I don't like mac servers) but also why Doug has had a good time.

There must be a way around this but doesn't seem like a common workflow in general with Vectorworks users.

I've created a linux server and to make sure that sharing work is easier in general even if permissions have set, set the umask for all users to 002

Additionally, I think sharing via NFS has given me more customization on the type of mount I can do where I can retain the permissions through the mount rather than with Mac Samba which only allows me to log in as the user.

I think what would work with a Samba set up though is if you have Domain Controller managed user accounts to sort out your permissions (which I haven't done yet).

The linux nfs set up seems to be working well so far and I would recommend it for a storage server to everyone at the moment. (Using CentOS 7.6 server but whatever you prefer would probably be fine.)

Has anyone found a working solution to this problem yet? A couple of years ago we had serious problems and ended up replacing our whole server, lots of machines, new software licenses etc. Eventually the solution that worked was to downgrade all users to non-admin status, which worked until now.

In the last two weeks we have the problem recurring - lots of VW files opening up in a 'read only' state (the pop-up shown in the OP appears on opening). The files are definitely not in use and this has been confirmed by our IT support who have checked server side.

We've the feeling it may be related to referenced files: when working with 2 files (file A, file B), when a user opens file B (containing a reference to file A), file A suddenly becomes (and remains) "read-only" till user B logs out. This also happens when file A is already opened by user A: suddenly the open file becomes read-only, and the user loses the possibility to save it and/or write/overwrite file A.

Just to confirm we are having the problem with all files, whether they include any referencing or not. Most of our files are small projects where we don't need to use referencing, and the issue still occurs.

It happens both with 2022/2023 files, even with files I just created myself and saved on the server as a test. My MacOS is Ventura 13.2.1 and server is a NAS Qnap in the same network, connected with SMB protocol. I guess not all of my colleagues are updated to the exact same operating system, but since it happens with my own files I just created as well this shouldn't be the problem, right?