FailFileInvalidCheckSum

khuster · Post by **khuster** » Sat Nov 12, 2005 11:31 am

Dear all,

could it be that the keyword expansion setting in the Repository options is preventing a successful VSS import? I attempted to import a few hundred .ASP and .HTML files from VSS to Vault, and I got around 60% failures, the importer said 'Reestablishing connection' and in the logs I could find that VaultFileUpload.aspx was throwing "FailFileInvalidCheckSum" exceptions mostly.

After changing the repository options to deny keyword expansion, it worked smoothly. Strangely, not every file is affected.

I suspect that the Vault VSS importer messes up the keyword expansion, such that the checksum differes during an import.

Can you confirm this bug? If yes, I suggest you include it into your suggestion list for a successful VSS import, or even better, fix the bug.

Cheers,

Karsten

lbauer · Post by **lbauer** » Mon Nov 14, 2005 1:51 pm

We believe this is a bug and have it logged to our bug database to investigate and fix for Vault 4.0.

We should add something about this to the import tips -- thanks for the suggestion.

aduggan · Post by **aduggan** » Fri Dec 23, 2005 9:02 am

Yes, please do add a note to the import tips.

Unfortunately for me, I lost a weekend to a failed import due to this same issue. I checked the update tips before I started, so that would have saved me.

Thanks!

lbauer · Post by **lbauer** » Fri Dec 23, 2005 9:45 am

I just added that information to the tips. Thanks for the reminder.