invalid working folder

[gregch]

This problem happened overnight. I have used new _sgvault files on my profile, restored cachemember files from a previous state. Even if I get a prodject bound correctly and open in another Visual Studio solution, it will complain again

Using VS2012 or VS2010
Using Vault Standard ver 6.0.1

I have checked and dbl-checked working folder assignments in Vault Client and they are correct

Where is this incorrect information coming from, cache files on the web server?

All of my solutions and projects are acting the same way

[Beth]

It might be a case of where your Vault Client and your Visual Studio client have conflicting working folders.

Here's some steps I'd like you to try:
1) Close Visual Studio.
2) Open the Vault GUI client.
3) Unset a working folder for a project you want to work with.
4) Open the .sln for that same project in Visual Studio.
5) An error will be given, but it should give you the option to select the working folder to use. Set the working folder.

Then let me know your results.

Please note that if you have another copy of the project, such as a branch, set to that same location, then you will receive a conflict error. There can be only one Vault location per working folder. You can have many working folders, but each one only corresponds to one Vault location.

[gregch]

I reset the working folder for one of the offending projects. I then loaded the orginal solution ( 10 projects) and removed all but the one in question and a dll library it need and then saved as a new solution.

Then I went to the Visual Studio menu and changed the bindings for the offending project.
That worked

So, why could I not bind the project when I was part of a different solution, or was it resetting the working folder in vault client that did it.

Also, my machine was not changed, the database is in good shape, how can this happen overnight and what can I do so I don't have to change every project that is doing this.

Also, after doing this, I opened the original solution with all projects, and the offending project was bound correctly!

[Beth]

Changing around a working folder in the Vault client won't change the working folder for Visual Studio, because VS places the location in its project files.

I had you take this route instead of trying a rebinding as an easier route to take care of a conflicting working folder, and to confirm in a way that was the issue. If you'd like to work on rebinding, then start with the article I have posted here: support.sourcegear.com/viewtopic.php?f=13&t=18956. If it's still not working for you, then you can send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread and I can take a closer look.

Things don't happen overnight, but it would be hard for me to tell you what exact action got you to this state. Usually it's a case of a user changing a working folder in the Vault GUI client to try and move some code around.