Resolving Checksum Errors
Checksum verification ensures data integrity between the PTC RV&S server and the client. Checksums are calculated and verified when a new member revision is committed to the repository. PTC RV&S automatically verifies the checksum on add member and check in operations. If no errors are found during the verification, the check in or add member operation completes successfully.
 |
Checksum verification on the PTC RV&S Server is enabled by default.
|
If checksum errors are found during verification, the revisions are not fetched into the repository, and a warning message is displayed:
In such scenarios, the MaxRetriesOnCheckinChecksumMismatch policy tries to resolve the errors and check in the member again after resolution. This policy is enabled by default and is set to 0. When the values are non-positive integers or floating values, it reverts to the default value. It is recommended to set the value of the policy between 1 to 10. The value of the policy determines the number of times the policy retries to resolve the checksum mismatch.
If checksum validation fails, even after the specified number of attempts, the failed checksum member files are saved at the following location in the PTC RV&S Server installation directory:
server/data/failed_checksum
The details of the checksum errors are logged in the server.log and the IntegrityClient.log files.
| | The PTC RV&S administrator must regularly delete any unwanted files from the failed_checksum directory to ensure that sufficient space is available in the directory. |
Understanding Log Messages for Checksum Mismatches
When the checksum analysis detects a discrepancy, the server.log file records the following information:
• Name of the corrupt member
• Project which contains the member, along with the configuration path, when available
• Name of the user adding or checking in the member
• Hostname of the PTC RV&S client.
For example,
• Client: MKS969178_ChecksumsDoNotMatch=A checksum mismatch has been encountered while uploading new revision of member {1} in project {0}. Please contact your PTC RV&S administrator. Check in checksum mismatch retry count is <>. This message is printed until the retry count reaches the limit specified by the administrator.
• Server: MKS970388_CHECKSUM_MISMATCH=User {0} encountered a checksum mismatch error on client host {1} for new revision of member {2} in project {3}. The computed checksum of {4} does not match the stored checksum of {5}. Please contact PTC RV&S Support. The file location and name is {policy path\member file}.
To Set the MaxRetriesOnCheckinChecksumMismatch Policy
Follow the steps below to set the value for the MaxRetriesOnCheckinChecksumMismatch policy:
1. Start the PTC RV&S Administration Client, expand the Configuration Management node and select Policies.
2. Select Global Policies, right-click, and select Edit. The Global Policies editor dialog displays.
3. To display other policies, click the Other tab.
4. Type the policy option you want to include, adding only one policy option per line. For example, MaxRetriesOnCheckinChecksumMismatch=value
For more information on formatting policy options, see Formatting Configuration Management Policy Options.
5. To apply the changes and exit, click OK.