Problem with Command-line Client since 2.0.x

[swildermuth]

I have used the command-line client (vault.exe) for several months now. WHen I upgraded to 2.0.0 (and subsequently all the way to 2.0.3), I get an error when trying to connect to do a get with the client. I am told:

"The connection to the server failed: server cannot be contacted or uses a protocol that is not supported by this client. Unable to connect to XXXXX. No server was found at the specified URL. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client. Web Exception: The underlying connection was closed: The remote name could not be resolved."

WHen using the client, I have tried a number of things for the -host option:

machinename:8888
localhost:8888
http://machinename:8888
http://machinename:8888/vaultservice

Nothing works. I can go to the http address with a browser, no problem. I can connect with the GUI client and the Vault Admin no problem. Here is the commandline I use (with the private bits replaced with *'s):

"c:\program files\sourcegear\vault client\vault.exe" get $/Source -destpath c:\primed\source -overwrite -user ********** -password ******** -host **********:8888 -repository "****"

Any ideas would be most appreciated!

[swildermuth]

I finally got it to work but it seems that the order of arguments is important. Did not work when I did:

vault.exe -user XXX -password XXX -host XXXX:8888

but did work when I put host first:

vault.exe -host XXXX:8888 -user XXX -password XXX

[dan]

Hmm - sorry for the frustration. We'll log this as an issue, since the order of the arguments really should not matter.

[kevin_w_kraus]

This is my first time using Vault.exe commandline, and I have not been able to connect to the server. The exact same scenario applies as described above. I can connect to the vault website and the web services, my GUI client works using the "mc-devsource:8888" server name, but command line always gives me this message.

I have reordered the options every which way, to no avail.

Please help, thx

Kevin

C:\Program Files\SourceGear\Vault Client>vault.exe CHECKOUT $/source.MFS/build.xml -host "mc-devsource:
8888" -user "username" -password "password" -repository "repositoryname"
<vault>
<error>
The connection to the server failed: server cannot be contacted or uses a protoc
ol that is not supported by this client. Invalid URI: The hostname could not be
parsed.
</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. Invalid URI: The host
name could not be parsed.
at VaultCmdLineClient.VaultCmdLineClient.Login(Boolean bAllowAuto, Boolean bS
aveSession)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommandCheckout(ArrayList str
ItemArray)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)
</exception>
<result success="no" />
</vault>

[dan]

Hmmm. I'm assuming you are on the latest Vault client (version 2.0.2 fixed a problem with regard to ports)?

Also, is port 8888 a non-ssl port? If it requires SSL to connection, you'd need to pass that flag along, otherwise it wouldn't connect properly.

Also, the simplest clc command is "listrepositories". Try that one and see if it also fails in the same way.

[kevin_w_kraus]

Thanks Dan for the info.

I am currently on 2.0.1 (2137), as indicated by the help menu in the GUI client.

Can I just download the latest client and keep my server at 2.0.1?

I tried the LISTREPOSITORIES command and had the same issue.

Kevin

[dan]

We recommend keeping clients/servers on the same version. If you are in a real bind and can't upgrade the server right now, I would recommend installing the latest client on a separate machine, and then copying the vault.exe file (which is the CLC) over to your 2.0.1 installation. The CLC itself would not have any incompatibilies with later versions of the server.

[haughtycool]

I'm using the version: 3.0.5, but it show the error:
<error>
The connection to the server failed: server cannot be contacted or uses a protoc
ol that is not supported by this client. Unable to connect to http://206.100.100
.16/VaultService. No server was found at the specified URL. Please verify your
network settings using the Options dialog under the Tools menu in the Vault GUI
Client. Web Exception: The request failed with HTTP status 400: Bad Request.
</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. Unable to connect to
http://206.100.100.16/VaultService. No server was found at the specified URL.
Please verify your network settings using the Options dialog under the Tools men
u in the Vault GUI Client. Web Exception: The request failed with HTTP status 4
00: Bad Request.
at VaultCmdLineClient.VaultCmdLineClient.Login(Boolean bAllowAuto, Boolean bS
aveSession)
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommandListRepositories()
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)
</exception>
<result success="no" />
</vault>

Please help me

[lbauer]

Were you able to connect previously with the Vault Command Line Client?

Can you connect with a Vault GUI Client?

Can you connect via web browser to:
http://206.100.100.16/VaultService/Vaultservice.asmx ?

See this link for some basic troubleshooting tips:

http://support.sourcegear.com/viewtopic.php?t=736

[haughtycool]

Thank you very much.
It has worked perfectly.
Thanks again