Path to Vault.exe incorrect in FinalBuilder Options

FinalBuilder Discussion
1

I just installed the trial version of FinalBuilder and am trying to configure our Vault repository (from FinalBuilder Options) and I'm getting the following error when I click on the find button in the Repository textbox:

 

Error occured when trying to retrieve repository list : 

Path to Vault.exe incorrect in FinalBuilder Options

I have Vault 5.0.4 installed on my local machine (where I'm trying to configure FinalBuilder) and I selected the path from Explorer so I know the path is correct (C:\Program Files\SourceGear\Vault Client\vault.exe). I've tried both options for "Connection and Authentication" and I've tried setting the host to the different values that it can be (It's currently set as just the name of the machine that the server is running on). I've also set the user name and password to what I use to login to the Vault client. I also have the Version set to "Vault 4, Vault 5".

I then closed the options dialog and tried again. This time I got the following error...

 

Error occured when trying to retrieve repository list : 

VAULT INTERNAL EXCEPTION: VaultClientIntegrationLib.UsageException: Please specify -user, -password, and -host.

   at VaultClientIntegrationLib.ServerOperations.Login(AccessLevelType altCommand, Boolean bAllowAuto, Boolean bSaveSession)

   at VaultClientIntegrationLib.ServerOperations.Login()

   at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)

   at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)

 

I have each of the fields being requested filled in. What am I missing?

 

2

I don't know why, but it seems to be working now. I tried changing the values to connect to Vault, but they are now set to the same as when it wasn't working. The only other thing I did was try running the Vault commands directly in the command-line. After I ran it, I went back to FinalBuilder and that's when it started working.

This is the last Vault command-line that I ran:

vault LISTREPOSITORIES -host dev -user me -password mypassword

I didn't even use the same username/password that I'm using for FinalBuilder. It seems unlikely that this had anything to do with it working now, but I don't know what else it could have been.