Can't connect using command line tool

This forum is now locked, since Gold Support is no longer offered.

Moderator: SourceGear

Locked
thecramgroup
Posts: 11
Joined: Wed Oct 20, 2004 1:24 pm

Can't connect using command line tool

Post by thecramgroup » Fri Sep 23, 2005 1:36 pm

Hi there,

I have a vault server running on server1 port 8008.

I can see the server at http://server1:8008/VaultService/VaultService.asmx

I am also able to connect to it using the GUI client.
However, the following command fails:

C:\Program Files\SourceGear\Vault Client>vault listusers -host "server1:8008" -
user xxxxxxx -password "xxxxxx" -repository xxxxxx
<vault>
<error>
The connection to the server failed: server cannot be contacted or uses a protoc
ol that is not supported by this client. 1000 : FailNotValidLogin
</error>
<exception>
System.Exception: The connection to the server failed: server cannot be contacte
d or uses a protocol that is not supported by this client. 1000 : FailNotValidLo
gin
at VaultCmdLineClient.VaultCmdLineClient.Login(Boolean bAllowAuto, Boolean bS
aveSession)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)
</exception>
<result success="no" />
</vault>


Please advise,

-Oleg.

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Fri Sep 23, 2005 2:45 pm

Which version of Vault are you using? There was a problem with ports in the command line client quite awhile ago.

thecramgroup
Posts: 11
Joined: Wed Oct 20, 2004 1:24 pm

Post by thecramgroup » Mon Sep 26, 2005 7:02 am

dan wrote:Which version of Vault are you using? There was a problem with ports in the command line client quite awhile ago.
Vault.exe version is 3.0.2.2812

dan
Posts: 2448
Joined: Wed Dec 17, 2003 5:03 pm
Location: SourceGear
Contact:

Post by dan » Mon Sep 26, 2005 8:18 am

I checked the latest release with port numbers, and everything seems to work, so that doesn't seem to be the issue.

Did the command line stop working, or has it ever worked from that machine? Does it work from other machines in the same network?

Does this client go through a proxy to get to the server? If so, the command line was updated in 3.0.6 to support proxies, which it didn't support in 3.0.2.

thecramgroup
Posts: 11
Joined: Wed Oct 20, 2004 1:24 pm

Post by thecramgroup » Mon Sep 26, 2005 9:41 am

dan wrote:I checked the latest release with port numbers, and everything seems to work, so that doesn't seem to be the issue.

Did the command line stop working, or has it ever worked from that machine? Does it work from other machines in the same network?

Does this client go through a proxy to get to the server? If so, the command line was updated in 3.0.6 to support proxies, which it didn't support in 3.0.2.
My bad, the versions of the server and client didn't match. I've upgraded the client, and it worked. Thanks.

Locked