Cannot check out because file is already checked out

[Tri]

Can you find out of the users who've reported this, does this only happen when they kill VS.Net during a commit operation? Or has it happened through a normal VS.Net session.

It happens most of time through normal session. (can check out, edit, but can no longer check in. Or see file as checked out, cannot edit and cannot undo check out).

Also, it would help if you know this ALWAYS happens with VS.Net / Vault integrated client, the Vault GUI client, or both.

It seems like VS is involved. All these issues are reported by developers of the team using VS integration. We have another team who has decided not to use VS integration. They didn't experience this kind of error during the last 4 months.

More clue: would that influence anything if the user switch from wired network (set Vault client to use proxy) to wireless (no proxy) during the day?

[jclausius]

If their domain / machine name is changing, then yes, that would explain things. When they switch from wired to wireless, is there some sort of domain shift?

Also, I was going to ask can you look at the folder where checkouts disappear? Is it always in a shared folder? Or does it occur in any folder (shared or otherwise)?

[Tri]

If their domain / machine name is changing, then yes, that would explain things. When they switch from wired to wireless, is there some sort of domain shift?

No machine name change for sure. A few of us sometimes use the wireless network to get past the customer proxy server and VPN in our head office network. None of them don't have the vault issue described above, except UserX who didn't use wireless yesterday.

Also, I was going to ask can you look at the folder where checkouts disappear? Is it always in a shared folder? Or does it occur in any folder (shared or otherwise)?

None of the folders involved in the issue are shared.