FailFileInvalidCheckSum on Check In

Ken · Post by **Ken** » Tue May 25, 2004 9:36 am

I am getting the following error when checking in a file through the vault GUI client:

VaultServiceBase.VaultResponseCheckIn returned: FailFileInvalidCheckSum

I tried making a copy of the file, undoing the checkout of the file, checking out the file again, and copying over the newly checked out file with the copy made before Undoing the checkout.

This results in the same error. I looked at the upload limit and this is fine as well. Please help, I need to get these files checked in.

Using Vault 2.0.1, same for client.

Post by **jeremy_sg** » Tue May 25, 2004 10:09 am

Ken,

The usual cause of this is a network problem (but we've been through that before http://support.sourcegear.com/viewtopic ... hlight=ken ). Did you set up the Don'tUseSendChunked registry setting? If yes, then did you run through the troubleshooting guide at http://support.sourcegear.com/viewtopic.php?t=721

Another possiblity is that you have a corrupted baseline file. Try running the client diagnostic tool at http://support.sourcegear.com/viewtopic.php?t=29
-Jeremy

Ken · Post by **Ken** » Tue May 25, 2004 10:35 am

I decided it was not a network problem since other files were checking in just fine. I downloaded the dianotic tool and the files are showing failed checks when I select the "Validate Cached Versions" option. The list shows several version of the file in the cached versions and the most recent and a previous version (version 9 and version 6) failed the test.

With this information, how do I go about correcting the problem with the corrupt baseline versions?

Post by **jeremy_sg** » Tue May 25, 2004 11:01 am

Ken,

Your absolute safest bet would be to set a new working folder for the directory, get latest, copy your file into the new directory, and check in from there. That will make sure that your changes make it in. To fix the current working directory, delte it, and delete the hidden folder (assuming that the Client Diagnostics tool told you which hidden folder had the bad data) that corresponds to it. Now a fresh get will have you working again.

Ken · Post by **Ken** » Tue May 25, 2004 11:35 am

Thanks, this worked but I still have no idea how the baseline versions would get corrupted. Do you know what would cause this to happen? Also the files showed numerous baseline versions in the diagnostic tool. Do you need all versions or is it safe to get rid of previous versions and keep the most recent version only?

sterwill · Post by **sterwill** » Tue May 25, 2004 1:15 pm

When the hidden directory is stored inside your working folders (it's named "_sgvault"), it's easy to perform a recursive find/replace or other action that inadvertently modifies the baseline files. If any byte was changed in these files, the new delta may still apply (because of the nature of the vcdiff format we use), but the resulting target file won't pass the CRC check.

GregM · Post by **GregM** » Tue May 25, 2004 2:04 pm

Shouldn't those files be read-only, then, since they're so important?

sterwill · Post by **sterwill** » Tue May 25, 2004 4:16 pm

Earlier versions of Vault didn't make these files read-only. The more recent versions do (it was an oversight in older versions). I think the change was made sometime around 2.0.0, although it could have been near the 1.2 timeline.

GregM · Post by **GregM** » Tue May 25, 2004 8:09 pm

Shaw, thanks for the clarification. That makes me feel much better.