small problem with Client after upgrading to 2.0.6

ggaudet · Post by **ggaudet** » Mon Sep 13, 2004 4:32 am

Hi,

We recently upgraded our client and server to versions 2.0.6. So far, there have been 3 complaints that after checking in a file, the client insists that it is still exclusivly checked out.

Shuting down the client and then restarted it seems to work, and then on future check out/ins, everything is fine.

Is there a reason for this? Is it OK that people use their same working directory, that was used in a 2.0.3 environment?

Gavin.

Post by **jclausius** » Mon Sep 13, 2004 8:39 am

I'd like to gather some more info here:

1) Is this reported in the Windows GUI client or within an IDE client? If this is the IDE client, what is the IDE ( VS.Net, VS.Net 2003 )?

2) To your knowledge, did this behavior exist, but go unreported in previous versions of Vault?

3) Are the users checking out the file specifically or are they checking out folders?

4) Is folder security enabled on the repository?

5) Are the files shared? If so, how many times? Do the files exist in shared folders? If so, how many shared folders?

Post by **jclausius** » Mon Sep 13, 2004 8:42 am

6) Do other clients see the file as locked, or when they refresh do they also see the file as locked?

sterwill · Post by **sterwill** » Mon Sep 13, 2004 4:08 pm

If you can reproduce this problem with client-side logging enabled (see this KB article for details) and send me the log file, we can diagnose your problem quicker. In the VaultGUIClient.exe.config file, set the "classesToLog" value to "checkoutlist", then start the client. When you've duplicated the problem, you can close Vault and send the log file. Be sure to mention which file was checked in.

ggaudet · Post by **ggaudet** » Tue Sep 14, 2004 12:37 am

To answer some of the questions:

1) This is the Windows GUI.

2) Not sure if this existed before, but in the Win Client, I can't recall anyone having this issue.

3) The users were checking out the file, not the folder

4) No, folder security is not enabled.

5) No, the files are not shared.

6) Only the one client would see the file as locked.

On the next occurence of this, I will confirm the above, and try to replicate it along with the client side logging.

Gavin.