Need help moving Vault - urgently :(

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

Hi, I've just had my colleagues laptop stolen and they have Vault set to auto-login, so I am fearful for the data. I want to move the vault to a new server ASAP - but with extras:

1. I'd like to upgrade to 3.0.5.
2. Move it to an entirely new server (different domain - the works).
3. I'll need to upgrade our licences as well - assume this is instant via credit card purchases?

I'm searching now for the relavent articles on the above, but if anyone can save me time by pointing them out, that would be great...

TIA
Dino

Post by **jclausius** » Thu Mar 10, 2005 2:52 pm

Sorry to hear that. You may want to change passwords immediately.

In the meantime, take a look at the KB index - http://support.sourcegear.com/viewtopic.php?t=792.

There are a number of articles related to moving Vault and/or the Vault database ( if SQL Server is located on a different machine ).

As for the purchase for Vault 3.0.5, what version of Vault are you currently using?

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

Thanx.

If I change passwords, will it still record a login attempt? One thought I had was to leave the current one intact once I have backed up the db, and then if they do log in, it records their IP address - could give that to the police to track it. I've seen our successful ones in the log - what about unsuccessful?

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

Oh - and just to clarify - do I need to move the Vault to a new install of 2.0.5 and then upgrade it to 3.0.5? Is that the correct order?

Post by **jclausius** » Thu Mar 10, 2005 3:00 pm

Dino wrote:If I change passwords, will it still record a login attempt?

The log file should contain something like:

user--hostname(ip.address)--SSL state Login failed: FailInvalidPassword

on any login failure regardless of Vault's log level.

Note, some people are smart enough to spoof IP addresses, so that information may or may not be beneficial.

Post by **jclausius** » Thu Mar 10, 2005 3:02 pm

Dino wrote:Oh - and just to clarify - do I need to move the Vault to a new install of 2.0.5 and then upgrade it to 3.0.5? Is that the correct order?

I think that would be the most prudent. Get Vault 2.0.x running correctly, and then do the upgrade.

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

Much appreciated.

On the spoofing of addresses, I'm expecting that these opportunists who stole the laptop from her boot won't be smart enough to do that - then again, they may not be smart enough to crack her password either.

But any little bit helps.

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

Have moved the db and followed the instructions for the user changes, but this is happening:

----3/11/2005 10:25:33 AM Dino--WXSLAKL001(192.168.69.10)--SSL Disabled
Object reference not set to an instance of an object.
----3/11/2005 10:25:33 AM Dino--WXSLAKL001(192.168.69.10)--SSL Disabled
Login failed: FailEncryption

Any ideas what I've got wrong?

Post by **jclausius** » Thu Mar 10, 2005 4:22 pm

Is this a good description of what has been done so far?

1) Detached / re-attached the database.
2) Modified the connectionstring in web.config to point to the new server

Are you using Windows Authentication or SQL Server authentication?

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

Ok - have resolved that - might have been due to the upgrade not yet having valid keys - not sure - but now I can log in via the web.

Next problem - have client 3.0.5 on my machine - I can log in via Vault Client to my server, however VS.Net gives an error "Vault Server uses a protocol not supported by this client"?

Dino

Post by **jclausius** » Thu Mar 10, 2005 4:51 pm

Have you uninstalled the Vault 2.0.x client? Or did you run this as an upgrade?

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

Ok - that's because of it still pointing to the old server.

Given I have about 300 projects, is there any "fast" way of redirecting them to the new server?

Post by **jclausius** » Thu Mar 10, 2005 4:53 pm

Unfortunately no, as this is defined by Visual Studio.Net, not Vault.

If this is for bound VS.Net projects, you should be able to do a search for MSSCCPRJ.SCC files. Upon finding all of them, you will need to :
1) Make a backup in case anything goes wrong.
2) Modify them in a text editor - being very careful not to change anything except the server connection info ( URL for the vault server )

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

Already done that - it seems it's being ignored...

Post by **jclausius** » Thu Mar 10, 2005 4:55 pm

After modifying the file, did you shut down / restart VS.Net?