Checkin failed: Checksum error?

ajj3085 · Post by **ajj3085** » Fri Sep 21, 2007 11:18 am

I'm getting an odd problem trying to check a file in. Here's the text from the Messages window of the Fortress client:

[9/21/2007 1:15:44 PM] Beginning transaction
[9/21/2007 1:15:44 PM] Add $/dotnet/MedQuotes.Business/MedQuotes.Business/Reports/QuoteProForma.rdlc
[9/21/2007 1:15:44 PM] Check in $/dotnet/MedQuotes.Business/MedQuotes.Business/Quote.cs
[9/21/2007 1:15:44 PM] Check in $/dotnet/MedQuotes.Business/MedQuotes.Business/MedQuotes.Business.csproj
[9/21/2007 1:15:44 PM] Check in $/dotnet/MedQuotes.Business/MedQuotes.Business/Properties/Resources.resx
[9/21/2007 1:15:44 PM] Check in $/dotnet/MedQuotes.Business/MedQuotes.Business/Properties/Resources.Designer.cs
[9/21/2007 1:15:44 PM] Upload for item $/dotnet/MedQuotes.Business/MedQuotes.Business/MedQuotes.Business.csproj failed, retrying...
[9/21/2007 1:15:44 PM] Upload for item $/dotnet/MedQuotes.Business/MedQuotes.Business/MedQuotes.Business.csproj failed, retrying...
[9/21/2007 1:15:44 PM] Upload for item $/dotnet/MedQuotes.Business/MedQuotes.Business/MedQuotes.Business.csproj failed, retrying...
[9/21/2007 1:15:44 PM] Ending the transaction
[9/21/2007 1:15:44 PM] Upload for item $/dotnet/MedQuotes.Business/MedQuotes.Business/MedQuotes.Business.csproj 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)
[9/21/2007 1:15:44 PM] Transaction failed
[9/21/2007 1:15:44 PM] Transaction failed

Here's the server log:
----9/21/2007 1:16:31 PM andyj--ANDYJ(172.18.1.20)--SSL Enabled VaultFileUpload.aspx encountered: FailFileInvalidCheckSum
----9/21/2007 1:16:31 PM andyj--ANDYJ(172.18.1.20)--SSL Enabled VaultFileUpload.aspx encountered: FailFileInvalidCheckSum
----9/21/2007 1:16:31 PM andyj--ANDYJ(172.18.1.20)--SSL Enabled VaultFileUpload.aspx encountered: FailFileInvalidCheckSum

Also, this error initially happened in the VS IDE; no error message ever is displayed, VS simply goes to Not Responding and you have to kill the task.

Thanks
Andy

Also, something weird. I've noticed that the checkin comments are pre-populated, and the comments persist after a reboot. I didn't expect that they would last through a reboot. Maybe not related at all though.

Beth · Post by **Beth** » Fri Sep 21, 2007 2:50 pm

What is the size of the file?
Is anyone else able to check it out, edit it, and check it back in? (The edit is needed or else it will just do an Undo Check Out instead of a Check In.)

Try first resetting your cache by going to the Fortress client - Tools - Options - Local Files - Cache. There is a button in there for resetting.

Also, while you are in the client, can you go to Help - Technical Support and copy the environment information there to me?

ajj3085 · Post by **ajj3085** » Mon Sep 24, 2007 6:23 am

Hi,

The file isn't that big, I have other .csproj files which are larger.

I installed the client on a coworkers workstation, and was able to check in there, so I was able to continue. I'll try clearing the cache though. I have the latest Fortress client & server versions.

Andy

Beth · Post by **Beth** » Mon Sep 24, 2007 8:34 am

We also have a change relating to checksums coming in the next maintenance release (due out soon), and that may help as well.

ajj3085 · Post by **ajj3085** » Tue Sep 25, 2007 6:53 am

Ok. I haven't had any problems since I checked in the file or reset the cache.

It might be good though if VS didn't just stop responding when this error occurs.

ajj3085 · Post by **ajj3085** » Tue Oct 02, 2007 8:48 am

Hi,

Wanted to follow up; I got this error again, and again it was on a project file (not the same project file as before).

Resetting the cache DID NOT fix the problem, but again I was able to do the checkin on another machine, get latest on mine and work with the file again (and check in).

I'd like to re-iterate here that if this happens in the VS IDE, the IDE immedately goes to Not Responding, and you have to tell windows to close the application. At the very least the error should be displayed and the IDE should not lock when this happens.

Thanks
Andy

Beth · Post by **Beth** » Tue Oct 02, 2007 1:29 pm

I think this is something that could be fixed with Fortress 1.0.5. We have the pre-release version ready if you want to try it. Send me an email at support at sourcegear.com (attn:Beth) with a link to this thread and I'll send you that pre-release.