Project Check-In fails.

Guest · Post by **Guest** » Fri Nov 04, 2005 10:27 am

Hi everyone,

I recently started getting an error for this particular file when checking-in the project folder. I have to undo the checkout in order to resolve the issue. Any thoughts?

Upload for item $/Projects/Contact/Console/ContactApp.vbp 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: VaultFileUpload.aspx encountered: FailFileInvalidCheckSum"
An exception was encountered during the transaction. Exception: The server returned an unknown error header: VaultFileUpload.aspx encountered: FailFileInvalidCheckSum at VaultClientOperationsLib.ClientInstance.UploadItem(ChangeSetItem item, String txID, Byte[]& streamBuffer, Int32& bytesWrittenThisFile, Boolean bIsImport)
at VaultClientOperationsLib.UploadThread.ProcessCommand(UploadThreadCommand command, UploadThreadCommandResult& outputResult)

Post by **jclausius** » Fri Nov 04, 2005 1:36 pm

What version of Vault are you using?

Are there any errors reported in the Vault server log file when you run these commands?

Evo · Post by **Evo** » Sat Nov 05, 2005 1:00 pm

Version: 3.1.1

----11/5/2005 1:57:00 PM admin--localhost(127.0.0.1)--SSL Disabled VaultFileUpload.aspx encountered: FailFileInvalidCheckSum

Evo · Post by **Evo** » Sat Nov 05, 2005 1:17 pm

I tried updating to 3.1.5 and it hasn't made a change. I still can't check in this file.

Post by **jclausius** » Sat Nov 05, 2005 2:57 pm

Is it possible something modified the baseline file on your hard drive? Something like a global find/replace in all files?

In any case, can I ask you try the following test to see if that is the case.

1) Set a new working folder for the parent folder of the file in question. This working folder should be a NEW folder, which does not currently exist. The file's status should go to MISSING

2) Do a fresh GET on the file into the NEW working folder. The file's status should now be blank.

3) Copy the file in your old working directory over this new file. The status should now be EDITED.

4) Do a diff to make sure your changes are the correct changes.

5) Commit the file.

6) Reset your working folder.

Did step 5 succeed?

Evo · Post by **Evo** » Sun Nov 06, 2005 9:04 am

I solved the problem differently.

I just made a copy of the file (in Windows) - deleted it from Vault, renamed the copy of the file, and added it back to Vault. Easy enough.

Post by **jclausius** » Sun Nov 06, 2005 1:38 pm

I'm glad you worked it out.

We don't have any known issues for checkin in this manner, so if it happens again, can you try the above suggestion? It would be helpful to know if something is unintentionally modifying the base line files.