Commit: Ending Transaction freezes

IsaackRasmussen · Post by **IsaackRasmussen** » Fri May 09, 2008 6:29 am

I have experienced quite alot of time where when checking files, it will get stuck at Ending Transaction and a 100% progressbar.

At first I thought it was due to large uploads, but this time, it was two small source files.

Each time, it gets stuck, there doesn't seem to be any way of cancelling or go back to VS, meaning that it's necessary to terminate Devenv.exe.
However, that leaves the SourceGear database for that project in a mess.

This time, when I reopened the solution, I got a new error

"Unable to save changes

Value does not fall within the expected range."

My setup is:
Vista SP1 x86
VS2008
Vault 4.1.1.18060

Server version
4.1.1.18060
Win2003 x64 serving only SourceGear

Beth · Post by **Beth** » Fri May 09, 2008 7:37 am

Which client do you have set in the VS Tools - Options - Source Control?

Can you provide me with your Vault Server Log? You can either post it here and then remove it later if you want, or you can email it to support at sourcegear.com (attn: Beth) with a link to this thread.

IsaackRasmussen · Post by **IsaackRasmussen** » Thu May 15, 2008 6:30 am

Sorry for the late reply. I was actually waiting for a reply notice email which never arrived.

I use the SourceGear Vault Enhanced Client.

Unfortunately, I don't have Debug Log enabled... I'll try and get the log emailed to you.

Beth · Post by **Beth** » Thu May 15, 2008 1:34 pm

What type of project is this?

IsaackRasmussen · Post by **IsaackRasmussen** » Fri May 16, 2008 1:26 am

It's a .NET 2.x C# Solution, with a mixture of Assemblies, Windows Forms and .ASMX WebServices.

The log may be a bit delayed. I'll email it when I can and include a history of this conversation.

Beth · Post by **Beth** » Fri May 16, 2008 3:57 pm

We're going to try and reproduce this.

ian_sg · Post by **ian_sg** » Sat May 17, 2008 9:33 am

Does the solution use any web references? There's a good chance there's a fix for this in the upcoming 4.1.2 release. You have a couple of options:

1) Try a 4.1.2 release candidate, see if the problem goes away. Email me (ian at sourcegear dot com) if you'd like to try this. If this doesn't resolve the issue, or it you'd rather not try a pre-release build you can:

2) Turn on logging in the enhanced client and send us a log. (You can attach it here or email it to ian at sourcegear dot com.) The log should reveal the issue.

Sorry for the inconvenience.

IsaackRasmussen · Post by **IsaackRasmussen** » Sat May 17, 2008 11:05 am

Yes, actually, we use alot of them. Also at times, multiple per project.

The behaviour is inconsistent. I'm not sure when it happens, let me try and wait for the next time and then email you for the RC.

ian_sg · Post by **ian_sg** » Tue May 20, 2008 2:02 pm

I await your email or a response here then.