Transaction Failed

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

Moderator: SourceGear

Post Reply
jpearson
Posts: 8
Joined: Mon Mar 14, 2005 4:21 pm

Transaction Failed

Post by jpearson » Fri Oct 17, 2008 10:39 am

Hi,
A person in our office is getting the following error when she tries to check in a file from the Vault Client 4.1.1:

Beginning transaction
[10/17/2008 10:23:37 AM] Check in $/Sharp Manual/ModelComponents.fm
[10/17/2008 10:23:43 AM] Upload for item $/Sharp Manual/ModelComponents.fm failed, retrying...
[10/17/2008 10:23:47 AM] Upload for item $/Sharp Manual/ModelComponents.fm failed, retrying...
[10/17/2008 10:23:50 AM] Upload for item $/Sharp Manual/ModelComponents.fm failed, retrying...
[10/17/2008 10:23:50 AM] Ending the transaction
[10/17/2008 10:23:50 AM] Transaction failed
[10/17/2008 10:23:50 AM] Transaction failed
[10/17/2008 10:23:50 AM] Upload for item $/Sharp Manual/ModelComponents.fm 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 returned an unknown error header: FailFileInvalidCheckSum"
An exception was encountered during the transaction. Exception: The server returned an unknown error header: FailFileInvalidCheckSum at VaultClientOperationsLib.ClientInstance.UploadItem(ChangeSetItem item, String txID, Byte[]& streamBuffer, Int32& bytesWrittenThisFile, Boolean bIsImport)
at VaultClientOperationsLib.UploadThread.ProcessCommand(UploadThreadCommand command, UploadThreadCommandResult& outputResult)

Any ideas? No one else in our office seems to be having any checkin errors.

thanks,
Jake Pearson

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Re: Transaction Failed

Post by jeremy_sg » Fri Oct 17, 2008 1:00 pm

Jake,

The FailFileInvalidCheckSum error occurs most often when a baseline file has been corrupted. There is a bug in the 4.1.1 version which prevented the client from automatically correcting the error as it should. If you upgrade your client to 4.1.3, the checkin should work.

You will not have to upgrade your server to 4.1.3 to use the 4.1.3 client.
Subscribe to the Fortress/Vault blog

Post Reply