Endless "Enging Transaction" then Vault hangs

[rdtuengel]

We've seen this error reported on the Support Forum, but not with later Vault releases. The user has this version:
[11/17/2011 12:43:12 PM] Version Check: This Vault Professional client is version 5.1.1.19216
[11/17/2011 12:43:13 PM] Version Check: Your server is version 5.1.1.19216
The user clicks ‘check in’ and the progress bar on the bottom right progresses up to 100%. Then on the bottom left it says ‘Ending Transaction.’ This message never clears. The user can then only use the Task Manager to force Vault to close. When they restart Vault, it reports that the remote version is a newer version than the local version they were just trying to upload. The status of this file is ‘Needs Merge.’ They can then ‘resolve merge status,’ but this then downloads the file in Vault back to the local working directory. So they don’t have any idea which, if any, is the correct version of the file. The file in this case is 13 MB.

We saw one solution, which was, under Tools > Options, under Network Settings, uncheck the box “Use chunked encoding to reduce . . . . “ . But it was already unchecked. Any ideas as to how we can resolve this issue?

[lbauer]

Is this happening just to this user and this specific file, or to other users/other files?

You could try enabling Chunked Encoding, to see if that helps the file upload.

Let me know if this does not resolve the problem.

[rdtuengel]

Just this one user has mentioned the problem. It happens with more than one file, but not with every file. We'll have him change the Chunked Encoding setting, and see if that makes a difference.

[rdtuengel]

The user has indicated that the files they've tried so far with the Chunk Encoding setting "checked" has worked fine. Hopefully that's a long term solution. Thank you for your suggestion.

[lbauer]

Glad that worked!

Chunked transfer encoding is an Http data transfer mechanism in which data is transmitted in a series of chunks. This helps to reduce memory consumption and makes it easier to upload large files.

However, chunked encoding is incompatible with some proxies, and doesn't work on all networks. That's why you might see some postings on our forum suggesting a user enable it, and other postings which recommend disabling it.