Problems checking in...

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
JadedATB
Posts: 2
Joined: Wed Feb 03, 2010 11:35 pm

Problems checking in...

Post by JadedATB » Thu Feb 04, 2010 12:11 am

I installed the Vault server and client (v5.0.2.18753) on a Windows 7 (64-bit) machine and everything seemed to be going well. I was able to add several existing projects using the Vault Client and then was able to set the source control bindings in Visual Studio 2008. It was relatively easy to set up and had all the features I was looking for, and then I tried adding a file and checking in. I get the following errors when checking in from Visual Studio or from the Vault Client:

====================================================================
Preparing data to begin transaction
Beginning transaction
Add $/XUtil/ListViewManager.cs
Upload for item $/XUtil/ListViewManager.cs failed, retrying...
Upload for item $/XUtil/ListViewManager.cs failed, retrying...
Upload for item $/XUtil/ListViewManager.cs failed, retrying...
Ending the transactionUpload for item $/XUtil/ListViewManager.cs failed too many times, aborting transaction.
Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client.
The specific error was "The server had an error processing the file upload but did not return an error header. The remote server returned an error: (500) Internal Server Error."
An exception was encountered during the transaction. Exception: The server had an error processing the file upload but did not return an error header. The remote server returned an error: (500) Internal Server Error. at VaultClientOperationsLib.ClientInstance.UploadItem(ChangeSetItem item, String txID, Byte[]& streamBuffer, Int32& bytesWrittenThisFile, Boolean bIsImport)
at VaultClientOperationsLib.UploadThread.ProcessCommand(UploadThreadCommand command, UploadThreadCommandResult& outputResult)

Transaction failed
Transaction failed
====================================================================

I've tried going through the Knowledge Base article, but haven't had any luck fixing this problem.
I've tried toggling all of the options in the Network Settings of the Vault client to no avail. I'm not using a proxy.
In IIS, "Anonymous Authentication" is set to Enabled. ASP.NET Impersonation is Disabled. I have no problems accessing the web service from Firefox.
I don't have much experience managing SQL Server 2008, but I opened the Management Studio and everything looked reasonable.
There are no error messages in the sgvault.log.

I'm sure this has to be a permissions error of some sort, but I have no idea what needs to be changed. Is there a concise list of all the permissions that need to be set in order for the system to work?

Any help would be much appreciated.
--Andy

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Re: Problems checking in...

Post by lbauer » Thu Feb 04, 2010 9:46 am

This is probably a network error, rather than a permissions error.

The first thing I would suggest is to try chunked encoding for uploads. This can reduce memory consumption.

This setting is in the Vault GUI Client under tools->Options->Network Settings.

If you already have that checked, you could try unchecking it.
Linda Bauer
SourceGear
Technical Support Manager

JadedATB
Posts: 2
Joined: Wed Feb 03, 2010 11:35 pm

Re: Problems checking in...

Post by JadedATB » Fri Feb 05, 2010 12:34 am

I've tried changing all of the network settings (chunked encoding, 100-continue headers, and request database delta). I get the same error in all cases. Is there anything else I can try to troubleshoot this?

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: Problems checking in...

Post by Beth » Mon Feb 08, 2010 8:40 am

Are other users able to check out files of the same size as the ones you are checking out, edit them, and check them in?

Can you look in the IIS logs on the server and find the 500 errors there to see if it gives more details? There's usually 3 numbers in an error. A success will be 200 0 0.

Do you see any errors in your Event Viewer logs on either your Vault server machine or your local machine when you are trying to check in?
Beth Kieler
SourceGear Technical Support

Post Reply