Need help moving Vault - urgently :(

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

Have the working folders been switched somehow, so that you are actually loading the files from somewhere else? You could try to put in some junk chars that you know are incorrect and see if it tries to load them.

You may have mentioned this already, but for solutions/projects doing this, you might check the .sln and .proj files in notepad, and search for "scc", and see if there are any old references there too.

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

No - in fact, I have ensured that all working folders have been reset.

I edited the SCC file, changed the URL to something else, and VS.Net did nothing... I opened the project, closed it and the SCC file remains as I changed it.

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

What I am very confused about is there are STILL logs on the old web server indicating it's trying to log into that server - is there anywhere else that this URL could be being cached???

I am currently searching every file on my dsk (150GB sadly!) trying to find any reference to the old server, but one thing is for certain - that is where Vault is looking.

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

Ok - little more information - it's corrected most of the older "core" projects (almost all Libraries) but has not corrected any of the EXE projects, however one Library has been left unchanged as well.

I've checked out the entire solution (from VS.Net) and checked via VaultCLient - everything is showing as checked out correctly... but still no joy???

dan · Post by **dan** » Fri Mar 11, 2005 2:25 pm

Try this: Do an Open From Source Control on this solution to an entirely separate folder, verify it checks out to the new server, and then compare this folder against your existing working folder, and see what the differences are.

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

Dan - it gets worse - I deleted the MSSCCPRJ.SCC file, and well - it makes no difference! The project loads, I get the same errors, but I can still check the project in and out of the new server, and the MSSCCPRJ.SCC file never reappears! SO it seems to me that VS is not getting it's path from there at all...

I think I am going to blow away this machine and start again - this is just too messy. Clearly things are not even remotely working the way they should - VS.Net is *NOT* using those files, I can't for the life of me figure out how it even know about the old server as it is not referenced in any file on my machine at all... it's just getting beyond a joke.

Also - can you explain why the "automatically log in" option never enables when I select a profile? It always used to - what is causing that not to work now?

dan · Post by **dan** » Fri Mar 11, 2005 2:53 pm

In 3.0, choosing a profile to connect with will automatically choose that profile next time, so there isn't a choice to be made by the user. We should probably just remove it from the IDE login dialog.

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

I hope that's not the case - if my colleague had not chosen that option on her notebook, then we wouldn't have had a problem with possible unauthorised access.

dan · Post by **dan** » Fri Mar 11, 2005 3:12 pm

You can't automatically login without having entered the password in a profile, so the capability to login is there when a user creates a profile with a password, not when a profile is used to connect by the IDE.

Dino · Post by **Dino** » Sat Mar 12, 2005 1:13 pm

Ok - I have just rebuilt my entire machine... and it's STILL looking for the old server@!?!?!

What else can I do - this is getting rediculous!

Dino · Post by **Dino** » Sat Mar 12, 2005 1:18 pm

Oh - and you know how VS.Net uses the MSSCCPRJ.SCC file to locate the source code control server?

I deleted every one of them from my drive, and it STILL looks to my old server - where is it getting that from!?

Dino · Post by **Dino** » Sat Mar 12, 2005 1:49 pm

Here's a tip - VS.Net stores the path to the Source Control Server in the suo file as well. Deleting those gave me a bit of grief in re-creating web projects, but otherwise has finally fixed this problem.