problems changing servers for vault

cdubose · Post by **cdubose** » Mon Dec 27, 2004 1:55 pm

We are moving our entire web site to another server, and are having a big problem getting the new projects set up on Vault.

The Vault client points to the new server. The project has been unbound from the old Vault. What I want to do is add the solution to Vault in the new location. However, it never seems to get completely unbound.

When I bring up "Change Source Control" it shows the following Server Name for the Solution and Project:

http://ded401dter.maximumasp.com/VaultService|:5

with red squiggly lines under it. Server Binding is "Unable to Display" and Status is "Invalid".

This IS the correct address for the server. But I think the VaultService|:5 is left over from the old one. I changed it in the MSSCCPRJ.SCC to VaultService|admin:2 because this is what a co-worker has and it works for him. However, even so it continues to show |:5 in the Change Source Control window.

Help .. what are we doing wrong?

lbauer · Post by **lbauer** » Mon Dec 27, 2004 2:03 pm

If the project is already in Vault, you might try backing up your working directories and then trying to get the project afresh from File->Source Control->Open From Source Control. This would recreate all the bindings.

cdubose · Post by **cdubose** » Mon Dec 27, 2004 2:25 pm

If I try to do this, I get an error: The project MandateMaker1 is under source control. An error occurred registering this project with source control. It is recommended that you do not make any changes to this project.

And this is when it is storing it in a DIFFERENT directory from the one that I moved the files into Vault from .. so it is not overwriting it.

I am totally lost. why is this so difficult? How can I just start over?

dan · Post by **dan** » Mon Dec 27, 2004 3:24 pm

Is the new error happening during the Open From Source Control, or does it happen when you later try to unbind?

You may need to hand edit the solution and project files to remove any scc related entries. Do a search for "scc" and see what comes up (make a copy of these files before modifying them!).

One thing that looks strange is that your co-worker seems to have a different Vault repositoy ID than you do, which could be the source of the problem as well. The line:

http://ded401dter.maximumasp.com/VaultService|:5

is broken down as follows: The first part (up to the |) is the Vault server to connect to. The part between the | and the : is the profile to use or the user to connect as. The part after the : is the Vault repository ID, which should be the same for any user using that project.

So, another thing to try is to change the 5 to a 2 in that file (if 2 is the right rep id), and see if that works. If there are muliple projects in the solution, you may need to update every MSSCCPRJ.SCC file (there is one per folder in your solution).

cdubose · Post by **cdubose** » Mon Dec 27, 2004 4:59 pm

Well, I just started over with a new Visual Studio project, moving all my files in and recompiling, and then doing an "add project to source control" (or whatever that menu item is). It seems to be working now.

My co-worker is working on a different repository, and he is using (or was using) the admin account, so that makes sense. Mine is still "|:5" so I guess that means I was not logging in with a profile.

Thanks for your attempts to help. I hope never to have to do this thing again. Truly, this should be easier.