Troubleshooting synchronization problems

When a synchronized stream has a status of Error in the ClearCase Synchronized Streams view, the most recent synchronization request has failed. You can get more information about the error by viewing the latest synchronization results.

About this task

To get information about a failed synchronization:

Procedure

  1. Right-click the stream in the ClearCase Synchronized Streams view and click Open Latest Synchronization Details.
  2. In the editor, go to the Logs page and open the Full Build Log.

What to do next

Most synchronization failures occur because process controls in one repository reject a change made in the other repository. The message in the log from the Rational® ClearCase® trigger (if Rational ClearCase rejected the change) or Rational Team Concert™ process (if Rational Team Concert rejected the change) tells you what went wrong. Fix the problem, and run the synchronize operation again.

If you are having problems with the Rational ClearCase dynamic view, you can try to fix them by creating a new Rational ClearCase dynamic view for that ClearCase Synchronized Stream. For more information, see Changing the Rational ClearCase dynamic view.

If you notice the following error in the sync log, then set MVFS to preserve case by navigating on your system to Control Panel > ClearCase > MVFS and setting Case Insenstive MVFS and Case Preserving:
 javax.wvcm.WvcmException: Failure while trying to execute cleartool command: 
 cleartool checkout -nc M:/some_pathname 
 cleartool: Error: Pathname not found: "M:/some_pathname". 

Synchronization failures can also be caused by network errors (failure to contact one repository or another), permissions errors (the synchronization process account does not have sufficient rights in the Jazz™ repository, or the synchronization process itself is running with credentials that do not allow access to the specified Rational ClearCase stream), or both. The details of the error messages are different for different cases. Fix the problem, and then run the synchronize operation again.

In addition to the message in the log, a synchronization stack trace log is created for the error. This log provides additional information that can help IBM® Software Support interpret the error and resolve the problem.


Feedback

Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug