VS.NET 2003 Can't find vault service (ever)

jdonnici · Post by **jdonnici** » Tue Feb 17, 2004 6:29 pm

I'm a relatively new user to Vault, running version 1.2.3 (for now). Each time I open my main source-controlled solution, I get the window that pops up that says something about starting the Vault integration component. I then get a messagebox that reads:

Unable to connect to http://server/vaultservice/VaultService. No server was found at the specified URL.

The reason it can't find it is that it's at http://server/VaultService and for some reason it keeps sticking the extra "/VaultService" in there. When I click OK, I get the "Connect To Server" window in which I've specified the correct URL and clicked the "Automatically connect to this server" checkbox -- That logs me in and all is well, but the problem persists and I get the same "unable to connect" message each time.

The standard Vault client opens and connects to the service just fine, automatically opening my default repository, etc. I've tried modifying some of the HKCU/ registry settings that specify URLbase, ServerString, etc. No dice, the values get re-written by Vault somewhere. This solution has 5 source-controlled projects in it, but the solution file itself is not source-controlled. I've tried looking in both the .SLN and .CSPROJ files to see if there's a setting in there somewhere, but no dice.

Any tips?

J Donnici

Post by **jeremy_sg** » Tue Feb 17, 2004 9:39 pm

You're right, there's a file that needs to be edited. It's the MSSCCPRJ.SCC file. Check out this thread.

http://support.sourcegear.com/viewtopic ... ultservice

jdonnici · Post by **jdonnici** » Wed Feb 18, 2004 10:46 am

After modifying the MSSCCPRJ.SCC files for each project, I re-opened the solution. This time, I still got the connection dialog. I replaced the "server/vaultservice/vaultservice" portion with just "server". The other thread mentions that it wants the service's SERVER and not an URL to the service.

After getting that prompt for each project, changing the server value, and setting the "always connect checkbox", it seems to have stuck. When I shutdown and re-open that solution, it connects to Vault just fine for each project.

Thanks.