Hello,
in Vault Client, I have one profile stored with login and password, "automatically login using this profile" is checked, and when I open Client, it works OK.
But when I open a VB6 project integrated with Vault, there's error message "the username or password supplied is invalid". Then it opens up the dialog "connect to server" with filled username and server, but empty password and empty profile. I select the profile (the only one in dropdown box), which fills in the password; then I click OK, and it successfully connects. But next time it's the same over again.
And when that happens, next time I open Vault Client, it again shows me the dialog "connect to server"; the checkbox "automatically connect using this profile" has become unchecked; everything else is selected, so it's no big deal to click OK, but still, it seems that when VB is connecting to the server, something gets broken.
Is it possible to get rid of this error, and is it possible to automatically login with the selected profile in VB6?
In VB6, first logon always fails
Moderator: SourceGear
In VB6, first logon always fails
Vadim Rapp
It sounds like VB6 is accessing old information instead of your current profile. Check out this article for a fix suggestion: http://support.sourcegear.com/viewtopic.php?t=2474.
The way that vault ties an individual project to a profile is through the mssccprj.scc file with the SCC_Aux_Path setting. For this setting the vault server address and the profile to use is set. If the profile in this setting is not correct or is missing then when visual basic tries to open this project it will prompt you for a user name and password. Often when opening a group, if one of the projects does not have the correct setting in the mssccprj.scc file then it will prompt you for the user name and password. If all of the projects have the correct setting then it will not ask you for a user name and password.
Much thanks, that fixed it.Beth wrote:It sounds like VB6 is accessing old information instead of your current profile. Check out this article for a fix suggestion: http://support.sourcegear.com/viewtopic.php?t=2474.
Vadim Rapp