HTTP Error 417 Connecting to Vault Server

A collection of information about Vault, including solutions to common problems.

Moderator: SourceGear


Posts: 256
Joined: Thu Nov 06, 2003 10:01 am
Location: SourceGear
PostPosted: Tue Feb 10, 2004 10:02 am
Certain web proxies ("AdSubtract" is one) cause the Vault client to be unable to connect to the Vault server. The symptom is an error message with text like the following:

Unable to connect to http://servername/VaultService. No server was found at the specified URL. Web Exception: The request failed with HTTP status 417: Unexpected status code.


Vault uses the proxy settings that Windows and Internet Explorer are configured to use. You can instruct Vault to bypass the proxy by editing the proxy setting of your Vault.exe.config file, which is located in "C:\Program Files\Sourcegear\Vault Client" by default. Changing the line:

Code: Select all
<proxy usesystemdefault="true"/>

to
Code: Select all
<proxy usesystemdefault="false"/>


will override the system default proxy. The same setting can also be changed in the .Net Framework's machine.config file, which would override the system default proxy for all .Net applications.

UPDATE
In Vault 3.x and later, the proxy settings can be set in the Vault GUI client. Go to Tools - Options - Network Settings.
Shaw Terwilliger
SourceGear LLC
`echo sterwill5sourcegear6com | tr 56 @.`

Return to Knowledge Base (Vault)

Who is online

Users browsing this forum: No registered users and 3 guests

cron