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.
Can't connect using command line tool
Moderator: SourceGear
-
- Posts: 11
- Joined: Wed Oct 20, 2004 1:24 pm
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.
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.
-
- Posts: 11
- Joined: Wed Oct 20, 2004 1:24 pm
My bad, the versions of the server and client didn't match. I've upgraded the client, and it worked. Thanks.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.