For the past year, Vault has failed to log in to my server automatically. I have just one profile, just one repository (I'll get to this in a minute too) yet it simply refuses to auto login.
I have rebuilt my dev machine and thus re-installed probably 5 times. I have 2 laptops, which also flatly refuse to auto login.
Is it a server problem, or is it a code problem in Vault client? I asked about this a year ago, and got the feeling it was "my fault" in the way I configured my client - however I won't accept this asnwer now.
And on the repository - if I only have one, is it necessary to ask me which one I want to use? Seems to me that the answer is going to be one of one, so a bit pointless asking me...
Auto-login - will it ever work?
Moderator: SourceGear
The first place to start with issues like this is to turn on client logging. The knowledge base index has links to KB articles on how to get that set up (depending on whether you are using the IDE client or the GUI client). Post the results when you are done.
Also, if this is the IDE client, these kinds of problems are often resolved by doing a fresh Open From Source Control to a separate working folder (or renaming the existing one). You might try that as well and see if it makes a difference.
Also, if this is the IDE client, these kinds of problems are often resolved by doing a fresh Open From Source Control to a separate working folder (or renaming the existing one). You might try that as well and see if it makes a difference.
Dan, it's both the IDE and the GUI client - basically, once the IDE fails to log in automatically, the GUI client will fail as well.
And what I just said was "I have rebuilt my dev machine and thus re-installed probably 5 times. I have 2 laptops, which also flatly refuse to auto login"
What this means is, I have wiped clean and "Open From Source Control" all my source at least 10 times, and it still happens every single time - so doing yet another "Open From Source Control" is a total waste of time right?
And what I just said was "I have rebuilt my dev machine and thus re-installed probably 5 times. I have 2 laptops, which also flatly refuse to auto login"
What this means is, I have wiped clean and "Open From Source Control" all my source at least 10 times, and it still happens every single time - so doing yet another "Open From Source Control" is a total waste of time right?
Yep it would be (sorry for not paying attention).Dino wrote: What this means is, I have wiped clean and "Open From Source Control" all my source at least 10 times, and it still happens every single time - so doing yet another "Open From Source Control" is a total waste of time right?
Let's start with the log files and see where that leads.
Also, does this happen for just you or everyone on your team?
And, which version of Vault are you using?
Oh I do not believe this!
I just read the thing on client logging, added the registry entry, opened VS.Net and... it logged in Automatically.
To test it wasn't a fluke, I tried on my laptop - straight in. I do not believe this.
Only thing I have done recently (as in within the last 12 hours) is a dump trans and a dbcc shrinkdatabase on the vault database as the log was about 600+MB - could it have been that causing a slowdown on the db, which caused the web serivce to time out on the first attempt to log in?
To test it wasn't a fluke, I tried on my laptop - straight in. I do not believe this.
Only thing I have done recently (as in within the last 12 hours) is a dump trans and a dbcc shrinkdatabase on the vault database as the log was about 600+MB - could it have been that causing a slowdown on the db, which caused the web serivce to time out on the first attempt to log in?