Exception: 2100 : FailExistingDownload

Zenda · Post by **Zenda** » Wed Jul 12, 2006 11:14 am

A user got this exception when trying to GetLatest:

An exception was encountered during the get latest operation. Exception: 2100 : FailExistingDownload

[6/28/2006 4:27:26 PM] An exception was encountered during the get latest operation. Exception: The Vault server could not be contacted to perform the operation. Your network connection to the server may have been interrupted. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client.The request failed with HTTP status 504: Proxy Timeout ( This operation returned because the timeout period expired. ).

The problem seems to disappear when the user reboot the client PC. But we still need to know what might have caused it. The following was extracted from the server log:

----6/28/2006 3:21:20 PM nkhan--216.123.167.52(216.123.167.52)--SSL Disabled Login
----6/28/2006 3:28:09 PM nkhan--216.123.167.52(216.123.167.52)--SSL Disabled Logout
----6/28/2006 3:33:24 PM nkhan--216.123.167.52(216.123.167.52)--SSL Disabled Login
----6/28/2006 3:41:52 PM nkhan--216.123.167.52(216.123.167.52)--SSL Disabled FailExistingDownload
----6/28/2006 3:45:25 PM kli--216.123.167.52(216.123.167.52)--SSL Disabled Login
----6/28/2006 3:46:37 PM nkhan--216.123.167.52(216.123.167.52)--SSL Disabled FailExistingDownload
----6/28/2006 3:48:35 PM boliver--sms4-pool118-0219.bmts.com(209.240.118.219)--SSL Disabled Login
----6/28/2006 3:48:47 PM nkhan--216.123.167.52(216.123.167.52)--SSL Disabled FailExistingDownload
----6/28/2006 3:51:49 PM nkhan--216.123.167.52(216.123.167.52)--SSL Disabled FailExistingDownload
----6/28/2006 3:52:13 PM nkhan--216.123.167.52(216.123.167.52)--SSL Disabled FailExistingDownload
----6/28/2006 3:52:42 PM nkhan--216.123.167.52(216.123.167.52)--SSL Disabled FailExistingDownload
----6/28/2006 3:53:10 PM nkhan--216.123.167.52(216.123.167.52)--SSL Disabled FailExistingDownload
----6/28/2006 4:15:19 PM nkhan--216.123.167.52(216.123.167.52)--SSL Disabled Logout
----6/28/2006 4:16:38 PM nkhan--216.123.167.52(216.123.167.52)--SSL Disabled Login
----6/28/2006 4:19:57 PM nkhan--216.123.167.52(216.123.167.52)--SSL Disabled Logout
----6/28/2006 4:23:47 PM nkhan--216.123.167.52(216.123.167.52)--SSL Disabled Login

Beth · Post by **Beth** » Wed Jul 12, 2006 3:47 pm

Can you provide me with more information?

Which version of Vault are you using? What is the environment that you have Vault installed in (servers, databases, and clients)? Are you integrating it with other software such as Visual Studio or Dreamweaver?

Are you finding connection errors in the machine log as well, or only the Vault log?

It looks like a Proxy issue.

Zenda · Post by **Zenda** » Mon Jul 24, 2006 11:27 am

We are using 3.1.8 server and the client was 3.1.5. We have the server and the database installed on different server PCs. The client which had the problem does not use any integration.

Beth · Post by **Beth** » Mon Jul 24, 2006 3:54 pm

We are using 3.1.8 server and the client was 3.1.5.

Though I can't say if this is or isn't contributing to the issue, it is known that not having the versions of the client and server match can cause issues. Since your server is more recent than your client, you can pull the client from your server. Just go to http://<vaultservername>/Vaultservice.

Was it only the one time that it happened? If anything happened with your network connections at all, then Vault would have the one time where it couldn't connect. That's where I would usually look to first...network connections and what the proxy server was doing at the time.

Thanks
Beth