Transactions not working

GeraldS · Post by **GeraldS** » Mon Mar 22, 2004 12:09 pm

Hello,

I am running Vault 2.01 (server Win2003 svr, client Win XP - both with latest updates). This is a new installation, not an upgraded database.

Whenever I do any type of transaction (add file(s), change a folder name, etc) Vault displays "Beginning Transaction" in the lower left status bar and then hangs until it times-out and gets an error message that it has lost the connection with the server.

Upon reconnecting (from either waiting until it times-out or killing the process and restarting it) it shows that transaction in the Pending Change Set, and when commited the transaction completes.

This behavior only happens on one workstation, from others it all works fine. On this workstation, I have VS.net 1.1 and .net frame 1.0 and 1.1.

Any suggestions?
Thanks,
Gerald

Post by **jclausius** » Mon Mar 22, 2004 2:05 pm

is there anything configured between the client and server which would block network traffic? (personal firewall, proxy server, etc)

Gerald · Post by **Gerald** » Mon Mar 22, 2004 3:12 pm

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

Gerald · Post by **Gerald** » Mon Mar 22, 2004 3:40 pm

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

Post by **jeremy_sg** » Mon Mar 22, 2004 3:49 pm

Do the transactions work if you try to commit them from the Vault GUI client. Does the messages pane give any hints as to what is going on?

dneal · Post by **dneal** » Thu Jun 17, 2004 10:36 am

I've been having the same exact problem for some time. After sitting idle for a while, VS.NET 2003 will hang when attempting to do any source control operation, and the SourceGear Valult client will hang with "Beginning transaction..." in the status bar. It doesn't matter if I'm at work with a direct connection to the Web server, or working from home over VPN.

I've tried changing the IIS application pool settings, and even assigning the Web site its own application pool. Please help... every day I'm growing more and more frustrated with this!

Post by **jeremy_sg** » Thu Jun 17, 2004 10:46 am

Does the GUI client exhibit the same behavior? Is it possible that there is a firewall or router that is timing out the connection after some idle time? Also, check the properties of the VaultService web application to make sure that IIS isn't recycling the process.

http://support.sourcegear.com/viewtopic ... er+process

dneal · Post by **dneal** » Thu Jun 17, 2004 11:20 am

Yes, I thought I made all of that clear in my post. The GUI client hangs with "Beginning transaction..." when I try to commit. There is a firewall between me and the VaultService when I'm working from home, but there is only a switch between me and the server when I'm working in the office. The behavior happens either way. I have configured the IIS application pool to not recycle the process or shutdown the worker process after a period of idle activity.

dneal · Post by **dneal** » Mon Jun 28, 2004 7:53 am

Hi. Any more suggestions on how this might be resolved? This problem continues to occur every day. I just now went to edit an ASCX and the IDE locked up, apparently in limbo trying to check out the file for editing. This is a new file that was recently added, and I had not remembered to do a "Get Latest Version..." from the GUI client so that the files would be marked writable.

lbauer · Post by **lbauer** » Mon Jun 28, 2004 10:23 am

Is there any relevant information in the Vault server log file?

I'd suggest enabling debug logging in the Admin Tool->Server Options-> logging. After the next hang, send me a copy of the sgvault.log file from the Vault server %windir%\temp\sgvault folder.

dneal · Post by **dneal** » Mon Jun 28, 2004 1:17 pm

I enabled the debug mode and restarted IIS (as the Admin client instructed). I opened the GUI client and waited perhaps 30 minutes. I then tried to check in the latest changes to a project. The status bar in the GUI displays "Working" and nothing more happens. I checked the sgvault.log file, and there are no new entries. I did the same test with the IDE. The status bar in the IDE reads "Checking in item(s)" and nothing more happens. No new entries are written to the sgvault.log file.

dan · Post by **dan** » Tue Jun 29, 2004 9:22 am

This is very mysterious, and our lack of responses is a result of that.

Another question: Is the problem that the client works for awhile on the workstation (after logging in), and then mysteriously stops working after a period of inactivity, or is it that the client never works from that workstation?

dneal · Post by **dneal** » Tue Jun 29, 2004 10:00 am

Yes, the GUI client works for a while when it first loads. That's my current work-around. When I first launch the GUI client I can commit changes, or when I first load the VS.NET IDE I can check-in newly added files. Just this morning the GUI client locked up when I went to commit changes, and I know it not been running more than 10 minutes. The GUI client never times out... it just sits there with a "Working" status until I kill it from the Task Manager.

dan · Post by **dan** » Tue Jun 29, 2004 11:29 am

So, this looks like some sort of timeout issue related to connections between the client and server.

I'm assuming you've looked at all the settings described in http://support.sourcegear.com/viewtopic.php?t=1014, but thought I'd mention it. Win 2003 has multiple recycle and timout settings, and any one of them can cause the connection to go away.

One workaround might be to have your client automatically refresh every 3-5 minutes (instead of the default of 10), and see whether that works as a way keep the connection going.

dneal · Post by **dneal** » Tue Jun 29, 2004 1:23 pm

I have configured the recycle and timeout settings in IIS. I've even created a separate application pool for the Vault Web application and disabled all recycle and timeout options.

I've changed my client refresh to 5 minutes. However, I don't recall seeing any activity in the sgvault.log file when I had debug mode turned on that leads me to believe that the client actually refreshes with the server. Maybe I'm wrong and this is yet another symptom of the problem.

Even if this is some sort of time out issue, why does the GUI client lock up? Why won't the client eventually time out or otherwise gracefully handle the problem? I've tried using the "Abort Current Operation" menu option, and it only causes the client to lock up completely so that even the form won't repaint.