Why do files received from Team Foundation Server lead to a corruption error on only one computer?

Question

We have a dozen developers working in VS2013 with Team Foundation Server 2010. Only one of these machines is facing this problem. When trying to get the latest messages, an error message is displayed:

"the downloaded file is damaged. get the file again"

We already: - cleared the cache in the tfs cache folder on the local machine - cleared the cache on the tfs server; - tried to reboot the local machine.

As mentioned earlier, no one else has this problem. We are all working on the same project. Besides the goat sacrifice, we are just not sure what to do. Any help would be appreciated, thanks!

Answer 1

I can not reproduce the problem, but I found a solution. I'm not sure why and how, but for some reason, a conflict arose between VS2013 and VS2010. The project in question was originally created in VS2013, but the original workspace was created in VS2010 (I know this sounds confusing). After uninstalling and reinstalling vs2013 and without hope, I read several articles about the difficulty of updating TFS projects from one version of VS to another. Therefore, I decided that I would just try to delete my workspace and get the latest version from VS2010. After he finished receiving the latter, none of the files were damaged, and I was able to work fine in VS2013. Since then, I have not been able to recreate the problem.

Decision

VS2013

Step 1: Delete the workspace (in the source control explorer, select the drop-down list next to the label "Workspaces:" and select the last option "Workspaces ..."

Step 2: Click the “Delete” button (this will completely disconnect your project from TFS and all mappings.)

VS2010

Step 3: Get the latest in the project in a new folder. Then close VS2010.

VS2013

Step 4. Open the project from TFS and PROFIT!

Answer 2

I encountered the same problem when performing my 4th test migration / upgrade from TFS2010 on one server to TFS2013 on another server. Previously, this was not, and it was very unpleasant to just appear in a blue manner after it was not a problem before. I am new to this company and do not have VS2010, so the proposed solution was not an option for me. After a while, I found a super simple solution:

Stop building the project in the TFS Administration Console, clear the cache in "Program Files \ Microsoft Team Foundation Server 12.0 \ Application Tier \ Web Services_tfs_data \". Restart the project collection. Then, in Version Control Explorer → Get Last.

Answer 3

We had a similar problem because the FIPS Algorithm compliance policy is enabled on some developer workstations and disabled by others. To resolve this issue, the FIPS compliance policy must be identical across all developers workstations. Then get the files with inconsistent hashes from TFS and check them again to correct (synchronize) the hash values.

MSDN forum: TFS 2010 VS2012 Get latetest version: file is damaged, it works fine in vs2010