Vault Client 3.5.2 not working with Vista

mjain · Post by **mjain** » Sat Jul 21, 2007 2:32 pm

Hi,
I have XP in one drive of my system and Vista on other. I downloaded Vault 3.5.2 client on both XP and Vista. Now when I do Get latest version on XP, it works fine but when I am doing same thing on Vista, I get different error
one of them is " An exception was encountered during the get latest operation. Exception: There is an error in XML document (1, 660557).
InnerException: The operation has timed out."

Please help, I have checked the network settings and everything. I have firewall disabled on Vista. I have no anti-virus installed. What is stopping it from working.

Beth · Post by **Beth** » Mon Jul 23, 2007 8:49 am

Is this occurring for any file you try a get latest on, or just some files? Try doing a get latest on just one small file first.

SMT_Roland · Post by **SMT_Roland** » Thu Dec 06, 2007 10:02 am

I am having a similar issue. We are running Vault Server 3.5.2.5087 and I have installed Vault Client 3.5.2.5087 on a brand new Vista Ultimate machine (clean install).

Connection to the server seems extremely slow, and sometimes unresponsive, but finally does connect. I have successfully branched a folder and am able to set working directory correctly.

However, when I perform a Get Latest on a directory Vault hangs and then spits out the following message in the Messages tab:

[12/6/2007 10:46:18 AM] 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 underlying connection was closed: An unexpected error occurred on a receive.Unable to read data from the transport connection: An established connection was aborted by the software in your host machine.An established connection was aborted by the software in your host machine

I have verified my network settings and Vault is connected. When I reviewed my target location (working directory) I found that all of the folders within the selected directory had been created, however none of the files were downloaded.

I am running through a Cisco VPN Client (latest version 5.x) on Windows Vista Ultimate (32-bit).

Any help is appreciated. Thanks!

**Various file types exist in this directory as it is a web project - aspx, xml, pdf, gif, jpg, htm, etc.. - none are transferred.
I was able to do this the day before on a Win XP SP2 machine without problem. Same setup, but using Vista.

SMT_Roland · Post by **SMT_Roland** » Thu Dec 06, 2007 10:15 am

As an update to the above /\ /\ /\

I was playing around with settings, trying to see if there was anything that could be affecting the network connection and found 1 setting that I changed. After I changed it and tried to GL again it worked fine.

Tools -> Options -> Local Files
Prompt before overwriting locally modified files was unchecked. I checked it and retried GL and it worked.

It doesn't make much sense to me right now, and it could just be a coincidence, but it worked after I selected that checkbox and clicked OK.

Post by **jclausius** » Thu Dec 06, 2007 10:15 am

Would there be any kind of firewall or other device (including the VPN) which may be doing any kind of stateful packet inspection?

Unexpected results happen when the HTTP stream for the vault client is modified.

Post by **jclausius** » Thu Dec 06, 2007 10:16 am

SMT_Roland, glad you're up and running.

mjain, did you try the small file get? Any change in status?

SMT_Roland · Post by **SMT_Roland** » Thu Dec 06, 2007 10:19 am

Thanks for the quick reply. Firewall settings in Vista are disabled, I'm behind the same firewall I was able to go through with XP the day before without changes.
Although the Cisco client is new (required for Vista) I don't think any packet modification or inspection would go on at the VPN level.

I will keep you posted if this reverts, but looks like things are moving along at this point.

Thanks!