File is already checked out by the current user... but not

[patrickc3000]

I'd really appreciate any help anyone could throw my way as I've been struggling with this issue for days now.

I created a new solution, converted my website in vs2008 from 1.0 - 3.5 framework.

I committed the solution to the repository. Everything was well and I could check in/out files successfully.

I renamed the working solution's root folder and got latest on vault to see if I could just get latest and have the project work for someone else.

That's where everything went wrong. I couldn't get the original solution fixed either, so I just deleted everything and started from scratch.
Since then, every time I either create a new solution and check it all into vault -or- permanently remove bindings, create a new solution and then rebind the projects to vault, I get the error message when I try to check something out:

File is already checked out by the current user in a different location. It will let me check the file out, but it isn't able to be checked in from the solution in VS2008 nor in vault at the location I check it out at.

Please help. This is truly miserable hacking away at this for hours and hours.

Thanks,

Patrick

[patrickc3000]

Just read some guidelines in another thread. Here is my version info:

Client Information
Vault Client Version: 4.1.4.18402
.Net Framework Version: 2.0.50727.1433
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 3 GB
Time Zone: (GMT-06:00) Central Time (US & Canada)

Server Information
Vault Server Version: 4.1.4.18402
.Net Framework Version: 2.0.50727.3082
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Timezone: (GMT-06:00) Central Time (US & Canada)
SQL Version: Microsoft SQL Server 2005 - 9.00.3042.00 (X64)
Feb 10 2007 00:59:02
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)

[Beth]

Go into your admin web page, then the repository where this is happening, then click Undo Check Out. You will receive a list of all the things currently checked out. Pick out the ones that you need to work on and force an undo check-out. Watch to see if the same file or files are listed twice. If you force an undo check-out on something you wanted, you can easily check it out again with no harm to your files.

[patrickc3000]

I'm not sure what you mean by my admin web page. I'm using the vault client and VS2008 IDE. The issue I'm having appears to be with the binding of a VS2008 project. I go to the root of the directory structure in vault and filter in the search tab by files checked out to me and the files are indeed checked out, but only once. I deleted all my files and started from scratch and I'm still getting the same error message. That makes me think it's a vault dat/ini file or something that is still pointing to the wrong place.

I am unable to checkout through the VS2008 IDE or Vault Client without getting this message and the end result is neither will allow me to check in a changed file.

[patrickc3000]

This is a time sensitive situation for my company. I'd appreciate any help anyone could throw my way.

[Beth]

Do you have someone performing admin duties on Vault? Who set it up? That person should have access to the admin web page where an undo check out can be forced. The error you posted is resolved by doing that. If it's really a case where it can't find some previous checkout, then that's the route to go.

Once the admin forces the undo check out, then try a fresh Open From Source Control (also called Open From Vault if using the Enhanced Client).

[patrickc3000]

Problem solved by deleting my client cache. Thanks for the help. I didn't know who my Vault admin was until you brought that up!

[Beth]

Thanks for the update. It sounds like in this case, your admin, when going to the Undo CheckOut would have probably reported a check out not being listed there. At that point it points to the cache.

If you want to get an idea of what other users would do, you can delete your entire solution from disk and perform a fresh Open From Source Control or Open From Vault. If you are using the Enhanced Client, it should give you a warning if you are about to upload something that others might not be able to open and use.