Repository option "Request exclusive lock"

[marct]

Hi,

I'm trying to have this setting apply across all my clients on a given repository, and while Vault GUI client seem to detect that server parameter and force exclusive lock on each checkout, I can still check out without lock from Visual Studio. I have restarted Visual Studio several times since changing the server setting.

Is this normal or am I missing something?

Note: I know there is a setting in Vault client options, but I wish to propagate/enforce this from the server as much as possible to iron out any renegade workstation there might be.

Thanks
Marc-Andre

[Beth]

In the Vault admin web page there is a setting for each repository where you can require exclusive locks. Try setting it at the Vault admin level and have users restart their clients.

[marct]

In the Vault admin web page there is a setting for each repository where you can require exclusive locks. Try setting it at the Vault admin level and have users restart their clients.

That is exactly what I have done. However, from Visual Studio it doesn't work. If I right-click a file and select "Check Out", the "Request exclusive lock" checkbox is still open and unchecked by default. I have restarted Visual Studio already several times since the setting was changed on the server.

I have a screenshot that I can provide to illustrate this. Let me know where I can email it to you if needed.

Furthermore, with automatic check outs enabled, if I start typing in a CS file the file is checked out but not locked.

Note: We are using the Enhanced client.

EDIT: I forgot to mention it is Visual Studio 2010.

Regards
Marc-Andre

[Beth]

What are your settings in the Vault Tools - Options - Network Settings? Can you post a screenshot of those settings?

[marct]

What are your settings in the Vault Tools - Options - Network Settings? Can you post a screenshot of those settings?

I have uploaded my network settings screen as an attachment with this post. Proxy settings are left to default, which is "none specified". The three checkboxes at the top are all checked.

Marc-Andre

[Beth]

Can we also check your Concurrent Development Style settings? Can you post a screenshot of those?

[marct]

Sure, attached in a screenshot of this.

[Beth]

The Always Request Exclusive Locks should be checked in your client.

What version of Vault are you using? So that I can try to recreate the issue, can you go to Help - Technical Support and copy the Client and Server information into a post?

[marct]

Hi Beth,
While it could be checked on all installed clients to enforce the locking behavior, I am seeking to enforce this from a server side perspective as much as possible, and avoid maintaining/enforcing the config on installed clients. A setting is easily changed and could then lead to potential problems if one workstation is not following the same policy as the others.

I am currently experimenting with the server setting (as mentioned in previous posts) on an isolated test repository. We have another repository with our production source codes. I don't know if that can interfere somehow and explain the behavior that I am getting. Just thought I'd give you this piece of the puzzle as well.
As far as I know the client settings are not varied by repository? If they do vary I may have to take those screenshots again as I am unsure in which repository I was logged in at that time.

Server and client version is 6.0.0.477

Thanks
Marc-Andre

[marct]

Here's the text requested:

Client Information
Vault Standard Client Version: 6.0.0.477
.NET Framework Version: 2.0.50727.5456
Operating System: Microsoft Windows 7 Enterprise
Service Pack: 1.0
OS Version: 6.1.7601
Total Physical Memory: 3.99 GB
Time Zone: (UTC-05:00) Eastern Time (US & Canada)

Server Information
Server Version: 6.0.0.477
.NET Framework Version: 4.0.30319.269
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Timezone: (GMT-05:00) Eastern Time (US & Canada)
SQL Version: Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86)




License Information
1 serial number(s):
1 of 1: 5 full users, permanent

[marct]

Hi Beth,

I noticed this morning that there is a new version 6.0.1.598 available for the server. I was thinking of applying that update to see if the issue is hopefully resolved in that new version.

I will post back once I have updated and tested the scenario again.

Thanks
Marc-Andre

[Beth]

I ran a test and even though you can check off the box in the client to not request exclusive locking, the server will still enforce it, and during the check out, the check out window that pops up should have the exclusive lock checked and grayed out as I am showing in my attachment.

I'll be trying a VS project next.

[Beth]

I've reproduced the issue in VS 2010 and will be logging a bug.

Thank you for reporting this.

F: 16537

[marct]

Thanks for confirming Beth.

[Beth]

You're welcome.