Need help moving Vault - urgently :(

Dino · Post by **Dino** » Thu Mar 10, 2005 4:56 pm

Everything was just down - I wrote a program to modify the MSSCCPRJ.SCC files, and have since rebooted etc...

Dino · Post by **Dino** » Thu Mar 10, 2005 4:57 pm

Everything was shut down - I wrote a program to modify all of those files, and then have since rebooted...

Post by **jclausius** » Thu Mar 10, 2005 5:01 pm

Can you shut down the old server ( iisreset.exe /stop )?

Also, profiles may be an issue. Do you have a profile configured to point to the old server? Can you change this to point to the new one?

Dino · Post by **Dino** » Thu Mar 10, 2005 5:10 pm

No - I can't shut down the server as other systems are running on it.

I've deleted the old profile already, and created the new one - Vaule Client logs straight in automatically without problem.

It's asking me to log in - I give it my name, my password and the *correct* server name, and it *FAILS* to log in to the old server!

Dino · Post by **Dino** » Thu Mar 10, 2005 5:11 pm

When I eventually get in, if I look at change source control, *everything* is pointing to the old server still - any ideas?

Post by **jclausius** » Thu Mar 10, 2005 5:14 pm

Dino wrote:It's asking me to log in - I give it my name, my password and the *correct* server name, and it *FAILS* to log in to the old server!

You have to act as our eyes/ears. What makes you think the VS.Net client is going to the old server? Can you verify there are login attempts on the OLD Vault server's log file for login attempts from VS.Net? What about login attempts on the NEW Vault server? Anything in that log?

Dino · Post by **Dino** » Thu Mar 10, 2005 5:17 pm

The project has opened up - and it's thrown a huge error message box stating "Unable to connect to http://oldservername" complete with the HTML that was returned. It's failing because I have removed the "Application Name" from the vaultservice (as I couldn't shut down the server).

dan · Post by **dan** » Thu Mar 10, 2005 5:23 pm

Dino,

Let's backup: You are able to get into the new server via the Vault standalone client, but the IDE projects still want to connect to the old server, correct?

Editing the MSSCPRJ.SCC files should work, but if it doesn't, bring up the solution/projects and then invoke Change Source Control, and unbind the solution from the old server, and then rebind it to the new one.

Or, an even safer way to go is to invoke Open From Source Control from the new Server and open the project that way (but to a new working folder, so VS doesn't get confused about the state of the files). Either way, you'll want to carefully check the state of your files after the conversion.

Guest · Post by **Guest** » Thu Mar 10, 2005 6:35 pm

dan wrote:Dino,

Let's backup: You are able to get into the new server via the Vault standalone client, but the IDE projects still want to connect to the old server, correct?

Editing the MSSCPRJ.SCC files should work, but if it doesn't, bring up the solution/projects and then invoke Change Source Control, and unbind the solution from the old server, and then rebind it to the new one.

Or, an even safer way to go is to invoke Open From Source Control from the new Server and open the project that way (but to a new working folder, so VS doesn't get confused about the state of the files). Either way, you'll want to carefully check the state of your files after the conversion.

Dan,

Yes - correct.

Editing the .SCC file clearly hasn't worked. However, "Change Source Control" has some serious issues:

I created a project called "Vault Test" in my Samples folder under Visual Studio Projects. I added this to the new Vault, and then checked it's SCC file to make sure I got it exactly correct for the new server. Now, I open another project (not under samples) and it wants to add the project with a root of "VaultTest" where VaultTest is 100% of nothing to do with this solution at all... so even changing source code control doesn't look like it will help.

And I would rather not have to change working folders if I can help it...

Dino

Guest · Post by **Guest** » Thu Mar 10, 2005 6:52 pm

Ok - new development - I was only trying it with one project, getting the same result every time. This time, I tried a few other projects - they all seem to work perfectly, so it's just one project that is remembering the old server somehow.

Maybe I can delete it's working folder, and then open it from Vault... see if that works.

Guest · Post by **Guest** » Thu Mar 10, 2005 7:02 pm

And now... after doing nothing... it works fine.

Sorry to have been a hassle - I can't explain why - but as soon as I opened a different solution, everything seems to have cleared... looks like I am back in business.

Thanx for the assistance.

Post by **jclausius** » Thu Mar 10, 2005 9:21 pm

Glad you're operational.

Stinking Laptop Thieves! Next time you can strap a Kensington lock to your collegue's leg.

Dino · Post by **Dino** » Fri Mar 11, 2005 1:11 pm

Sad to say I spoke too soon

Ok - here's what I've now got. Vault *seems* to be working fine to the new server, however:

When I open a solution, it will come up with that "server does not support the protocol of the client". I select my new server from the profiles, but the "Automatically connect" option is permanently greyed out. The solution continues to open, maybe asking me 5 or 6 times to select my Vault server.

I can then check out the entire project, check it all back in no worries... but next time I open it, same thing again.

Oh - something I forgot to mention - I renamed the repository (one of the first things after the move - not in the middle of all my problems).

Any suggestions for my next move? And any ideas at all where it's getting the old server address from? I've searched, and it's not in plain text in any file on my drive, nor in registry - but Vault must be getting it from somewhere...

dan · Post by **dan** » Fri Mar 11, 2005 1:16 pm

Vault gets its connection info from the MSSCCPRJ.SCC file (actually, VS reads it and sends it to Vault). However, when you change it via the login, it should overwrite the .scc file. Can you verify that it gets changed after the login? Also, note that there is one of these files per project and solution (it is located in the working folder of each project/solution), so it has to update each one as you login.

However, once you successfully login and then shutdown VS, it should have the right contents.

Dino · Post by **Dino** » Fri Mar 11, 2005 1:26 pm

Hmmmm - every MSSCCPRJ.SCC file in this solution has this in it:

SCC_Aux_Path = http://www.xceptionsoftware.com/VaultService|Xception:1

Which would appear to be correct. I also note that none of these files have changed since I wrote the app to switch them from the old to the new server yesterday - so it seems VS.Net is either not updating it, or is happy with what's there in the first place?