Work is not being saved in project sharing file

[Hassan Raza]

Hi Everyone,

 

We are having difficulties with sometimes work is not being saved even after saving and committing in a project sharing file since we updated to 2018. 

We tried making a new project file after making previous project file into normal Vectorworks file.

I am wondering if someone is having the same issue or know anything about it.

 

Thank you!

[Christiaan]

We've experienced this sort of thing too. Have you updated to SP1?

[mthompson]

We are able to check out and release sheets/layers, but changes cease to be pushed to the Project File after approx. 2 hours. Running VW2018 without SP1.

[Asemblance]

+1

 

Also suffering from problems with the project sharing in our office, and its a major headache!

 

We've had a few minor issues with speed and such, but I am assuming this is just part and parcel of using the project sharing files and the network choking. The more serious ones we've had today include:

 

1. Three of us in the office working on a set of plans. One working on the basement floor plan (checking out the entire layer and working on it) made a series of changes throughout the day, 'save and committing' regularly. However these changes did not show up on the other machines in the office. I am 100% confident this wasn't due to some noobie error on our part, we spent a good long while looking at it and trying to find a workaround. Ultimately we had to copy the basement plan to a new file, and replace it manually in my working file. I should clarify as well that the file had not disassociated, as we could still see in the project file sharing history a bunch of two way information, suggesting the files were all still linked properly (screenshot attached).

2. Often random pieces of geometry are 'left behind' when items are committed/released. We have kind of taken this to be just one of those things, frustrating as it is. This happened earlier today, and I went in as administrator to release the layer, but couldn't. A few screenshots attached ('release' button greyed out in project sharing menu).

3. Frequently we will get an error saying 'The commit operation failed because your permissions were changed or the exclusive locks on items you had checked out were released by an Administrator'. I know for a fact this isn't the case because several times it occurred whilst I was the only administrator, and we all seem to get this message occasionally with no correlation to any admin activity. To get around it, we have to blanket 'checkout' everything we can remember working on, and then try again, which appears to resolve the problem. It can usually be traced to one or two pieces of geometry that the working file seems to have 'forgotten' it has checked out, for want of a better word.

 

Apologies thats quite a chunk of text! Screenshots attached.

 

We're all working on vwx2018 (SP1)

Edited October 23, 2017 by Asemblance

[Christiaan]

On 20/10/2017 at 7:48 AM, mthompson said:

Running VW2018 without SP1.

 

You should update to SP1.

[Christiaan]

10 minutes ago, Asemblance said:

Screenshots attached.

 

I've found the "exclusive locks" message can often be solved by subsequently checking out all the layers you've worked on and then trying another save and commit.

[Asemblance]

Christian - Yes we've also worked that out through trial and error. The biggest issue we have is then having to kick out everyone else who may be working in any element of those layers, so that we can checkout all the entire layers we have completed any work on. This is further complicated when the file sometimes thinks rogue geometry is checked out by someone else (who it isn't), and you get into a spiral of chaos trying to sort it out!

[JMR]

For 2017, we noticed that using "close and release" instead of save and commit helped to remedy the situation with mysterious soft locks. Perhaps worth trying here as well?

 

In other words, we started to use "close and release" in the middle of the working day, several times.

[Christiaan]

Ugh, yes, all nasty stuff. And made worse the more people you have working on a project.

[Hassan Raza]

For me checking out each layers from project sharing through drop down menu works rather then checking out objects while making changes. Sp1 definitely resolve few issues specially graphics glitches but still it is far from being perfect.

[anton5]

we still have these issues with Project sharing in 2019 SP6... which is time-consuming and frustrating frankly, any solutions?

[matteoluigi]

On 1/22/2021 at 2:31 PM, anton5 said:

we still have these issues with Project sharing in 2019 SP6

Which operating system are you working with? Mac? Windows? Both Mac and Windows? What kind of server do you use? Ever thought about switching to 2020 or 2021? (In 2021 finally there exists a projectsharing server-app)

when you’re working on Mac, check wether you access your network shares via afp, smb or both afp and smb protocol. Generally it’s dangerous using both smb and afp parallely...

[chaz]

Using VW2021 and having this issue, 3 days before I fly and this project starts becoming reality. None of the work arounds suggested work. I am the lead designer and admin on the project and running out of time on a project that cannot be delayed. I spent a long time yesterday and traced the error to resizing a rectangle. But now I'm in  completely different layers and none of them will commit.

 

Very disappointing that no one from VW has commented here. VW doesn't really seem to be ready for Project Sharing, always have big issues. I'll probably move us to using referencing more in the future and rely a lot less on Project Sharing, just don't need the headaches when facing deadlines.

Edited March 2, 2022 by chaz