Unexpected recurring CRC validation failures

If you are having a problem using Fortress, post a message here.

Moderator: SourceGear


Posts: 2
Joined: Wed Jan 27, 2010 9:11 am
PostPosted: Wed Jan 27, 2010 9:43 am
Hello. My company has recently started to have problems with some of our Fortress repositories related to CRC checks. Here's some background info:

We're using Fortress Client and Server version 2.0.1.18729. We have a single database with 45 repositories; of these we are actively running CI and Release build scripts for about 8. About midway through last week our CI scripts began failing for 4 of these 8 projects (we been unable to detect any sort of pattern or reason why those particular four are failing). Our scripts are failing when we try to get latest from the code repository. Executing the command via the command prompt returns the following:

Code: Select all
C:\Program Files\SourceGear\Fortress Client>vault get -user "buildmaster" -password "<PASSWORD>" -host "<REPOSITORYHOST>" -repository "<REPOSITORY NAME>" -nonworkingfolder "c:\BuildFolder\<REPOSITORY NAME>_CI" "$/Trunk/"
<vault>
  <!--An error occurred reading from the download stream ("CRC value in header 1918987296 does not match computed CRC value 3024175977!"), retrying...-->
  <!--An error occurred reading from the download stream ("CRC value in header 1918987296 does not match computed CRC value 3024175977!"), retrying...-->
  <!--An error occurred reading from the download stream ("CRC value in header 1918987296 does not match computed CRC value 3024175977!"), retrying...-->
  <!--Too many errors were encountered downloading files.  Some files may not have been updated.-->
  <result>
    <success>True</success>
  </result>
</vault>
C:\Program Files\SourceGear\Fortress Client>


We do not use a working folder because our CI scripts and Release scripts each build to separate folders. If we connect to the repository, set a working folder and then try to get latest on the trunk line, it fails due to CRC problems (visible in the Messages tab of the Fortress client). Although, we can get latest on individual files that have failed.

One project seems to have been recovered by logging into Fortress on our build server as our build account (buildmaster), setting a working folder, getting latest on the individual files failing the CRC, and then unassigneding the working folder. We attempted this with another project but the problem did not go away; the files with the CRC errors are not constant (sometimes our 3rd party component folder fails, sometimes the code folder fails, etc). The reported message has always been...

An error occurred reading from the download stream ("CRC value in header 1918987296 does not match computed CRC value 3024175977!"), retrying...


...the referenced header or computed CRC value are these same constant values for all reported failures.

Our buildmaster account is not set to use explicit CRC validation (in Fortress Client under Tools -> Options -> Local Files -> Detect modified files using CRC...)

Any ideas? LIke I said, this happened suddenly and painfully. We turned on detailed logging in the client (via ctrl + alt + shift + F12) and debug logging in the server, but nothing appeared out of place for us.

Posts: 2
Joined: Wed Jan 27, 2010 9:11 am
PostPosted: Thu Jan 28, 2010 11:18 am
Update:

Setting a working folder does not resolve the problem; I was just lucky on that build and there were no CRC problems.

Posts: 7157
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
PostPosted: Thu Jan 28, 2010 11:26 am
This issue is being taken offline.

HS: 218970

Return to Support (Fortress)

Who is online

Users browsing this forum: No registered users and 0 guests