SourceGear Support

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.

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.

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 ...

The default is Access.

We have multiple repositories and multiple groups under Fortress. We wanted granular access control for one of the repositories, and the folders in it. We set up one group with full access to all the folders in that repository, and one group with full access to most of the folders in that repository...

Linda - Thank you for your quick response. I was looking at the Admin functions of Fortress for that feature. I didn't think to look at Client side.

It appears that the default status of all files checked-in to Fortress is Read-Only. I haven't found anywhere to change that. Is there a way to modify the default file properties to not be Read-Only?