Workaround: Incoming synchronization of a ClearQuest record blocked by synchronization of attachment with a null pointer exception
Lorelei Ngooi
Last Updated: March 28, 2011
Build basis: Rational Team Concert 3.0
Summary
This workaround describes how to unblock the incoming synchronization of a CQ defect that is blocked by the synchronization of an attachment whose synchronization status is incoming error due to a null pointer exception.
More Information
Viewing the external properties of the attachment in the synchronization status view shows the attachment content property is null. This is the cause of the null pointer exception.
To workaround this issue, perform the following steps:
- In RTC, stop synchronization of the attachment by selecting the context menu option in the synchronization status view.
- In ClearQuest, make a backup copy of the attachment.
- Delete the CQ attachment.
- Re-add the CQ attachment.
© Copyright 2011 IBM
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means.
Learn more here.