TerryYoung

One of the files in the TFS Version Control repository is corrupt (that is, TFS reports that "The CRC in GZip footer does not match the CRC calculated from decompressed data"). It is likely the file was corrupted on transmission as this file was checked in remotely over a VPN and there haven't been any problems when using the same laptop connected locally to the network.

TFS reported to the developer that the checkin was successful. We discovered the problem through events in the TFS server application event log. The first event reported was a TFS Version Control error reporting the following exception for the developer account ¡°Exception Message: TF15009: The proxy could not validate the request signature. (type DownloadTicketValidationException)¡±. The next TFS Version Control error event reported the following exception for the developer account ¡°Exception Message: Invalid character in a Base-64 string. (type FormatException)¡±. The next TFS Version Control error event reported for the developer account was ¡°TF14043: An error occurred computing the delta for item <file pathname> version 10316.System.IO.InvalidDataException: The CRC in GZip footer does not match the CRC calculated from the decompressed data.¡±. After that there are TFS Warehouse error events approximately every hour reporting ¡°Microsoft.TeamFoundation.VersionControl.Adapter: An error occurred while processing changeset 10331, unexpected exception: Exception Message: The CRC in GZip footer does not match the CRC calculated from the decompressed data. (type InvalidDataException)¡±.

The developer has since locally checked in an uncorrupted version of the file. However, the corrupted file is still in the repository and we continue to get the TFS Warehouse error events.

Questions:

1. What is the best way to clean up the corrupted file in the TFS Version Control repository

2. Why doesn¡¯t TFS check and report the corruption to the user right away on checkin Better yet, why doesn¡¯t TFS prevent a corrupted file from being checked in



Re: Team Foundation Server - Version Control Corrupt file

Mario Rodriguez- MSFT

Hi:

I think for this scenario the best thing to do is to contact Product Support and we can provide a script that fixes the problem. In the future we can have a better more automated way of doing this.

i think you are already in talks with our support group but I will give you my email address in case you need to contact me mariorod@microsoft.com

Thanks,mario






Re: Team Foundation Server - Version Control Corrupt file

Scott Davis

I have this same error in my error log. Is there a recommended method of clearing this error now





Re: Team Foundation Server - Version Control Corrupt file

Cindy_XIN

I got the same problems. I resolved it by this way:

1. Check the databases of TFS by "DBCC CHECKDB" , you may find some of the datatables have index errors.

2. Rebuild all the indexes in these datatables.

Hope it is helpful for you!