Transactions not working

dan · Post by **dan** » Tue Jun 29, 2004 2:27 pm

The GUI client certainly shouldn't lock up. But, we've not been able to reproduce the problem here, so unfortunately, we are kind of stuck.

Can you post the output of Help->Technical Support here (from the Vault GUI client), so we can see the the configuration of your setup? There probably isn't much we can glean from it, but it might help...

dneal · Post by **dneal** » Tue Jun 29, 2004 2:38 pm

Client Information
Vault Client Version: 2.0.3.2174
Operating System: Microsoft Windows XP Professional
Service Pack: 1.0
OS Version: 5.1.2600
Total Physical Memory: 1023.23 MB
Time Zone: (GMT-06:00) Central Time (US & Canada)

Server Information
Vault Server Version: 2.0.3.2174
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 0.0
OS Version: 5.2.3790
Timezone: (GMT-06:00) Central Time (US & Canada)
SQL Version: Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: )

License Information
License ID: 26959
Customer ID: 34723
Number of Licenses: 5
License Type: Starter
Creation Date: 11/25/2003
Activated: Y

Jerry R · Post by **Jerry R** » Thu Jul 01, 2004 2:22 pm

It looks like one of the users here has the exact same problem. Vault GUI Client occasionally locks up for her for no apparent reason. Says "Beginning Transaction" and then hangs.

dan · Post by **dan** » Fri Jul 02, 2004 7:21 am

Has setting the automatic refresh down to 3 or 4 minutes helped any with this problem?

dneal · Post by **dneal** » Fri Jul 02, 2004 7:25 am

No, the problem is still there. After a while, the status text in the GUI client says something like "Refreshing repositories." It allows me to gracefully close the program. I can then launch it again and commit the latest changes.

Post by **jeremy_sg** » Tue Jul 20, 2004 1:21 pm

Gerald wrote:Jeff,

There is no proxy or firewall between me and the server. The other machines that can successfully access the server are on the same switch that I am. My Windows Personal firewall is not running, I have no other firewall software and I have uninstalled my virus scanner (McAfee) just in case.

Any other suggestions? Thanks!

Gerald

After talking to Gerald on the phone, and because this was a network issue, that looked like an active connection was getting dropped, I recommended that Gerald use drtcp from
http://www.dslreports.com/drtcp
to set his MTU to a lower value.

We started at 1200. Setting the MTU caused everything to work. When I hung up, Gerald was instructed to keep trying higher vaules until he found the highest setting that would still work. The maximum value is 1500, which is the default.

dneal · Post by **dneal** » Thu Jul 22, 2004 8:50 am

Changing the MTU does not solve my problem. I've tried an MTU of 1200, and I also followed one of the FAQs at DSL Reports to discover my optimal MTU setting. The problem persists.

I've also recently moved the VaultService to another Windows Server 2003 server. The same problem still exists. We are moving this server to a colocation facility today. I'll let you know if that makes any difference.

Thanks,
David

dneal · Post by **dneal** » Thu Jul 29, 2004 7:04 am

The case is sol-ved (read as Inspector Clouseau).

I believe I have discovered the culprit. I've been using the BSafe Online content filter on all my computers. Recently, I've been working on a project that uses HttpWebRequest and it was failing with an error that indicated the filter. So, I temporarily uninstalled BSafe to complete my development and testing. I had Vault running for quite some time and didn't see the usual "Refreshing repositories..." status message that indicated it was hung up. I was able to commit changes without restarting or it locking up! I've been monitoring the application for a while, and it seems to be working perfectly.

Now... I plan to reinstall BSafe. Do you have any suggestions on how I could get Vault and BSafe to play nice?

Thanks!
David