Problems Checking Out Files After Upgrade
Article ID: 130883
Updated On:
Products
Issue/Introduction
After upgrading Harvest, we are seeing random errors and problems when performing checkout operations. Example errors include:
E02020053 Cannot open signature record for <filename>
E03020566 Cannot write signature record for <filename>
E03020175 Server cannot communicate with the agent on machine <servername>
We also find that when checking out in "synchronize" mode, at times, Harvest will check out all files in the folder, even if there were only one or two files in the package being checked out.
What causes this and how can we resolve the problem?
Environment
CA Harvest SCM all versions
Cause
These types of problems can happen
- If a signature file has become corrupted,
- If the format of the signature file for the new version of Harvest has changed
- If the user connecting to the remote agent does not have appropriate permissions to read and update the file
Resolution
For the first two possibilities, the difficulty is that no utility or tool exists that can "repair" or "refresh" a signature file. In such cases, the best solution is to delete the "harvest.sig" file causing the problem and do a fresh checkout. In this process, Harvest will create a new signature file.
For the third possibility, check the ownership and permissions for the signature file and the folder it is in on the remote server to ensure the user connecting through the agent has the appropriate permissions to make updates.
Additional Information
You can read more about the signature files in the documentation here: Use Check-In and Check-Out in CA Harvest SCM - Signature files
Information about the error messages listed above can be found here:
E02020053 Cannot open signature record for <filename>
E03020566 Cannot write signature record for <filename>
E03020175 Server cannot communicate with the agent on machine <servername>
Feedback
