Eric J. Ostrander's
ClearCase / ClearQuest pages.
Unified Change Management (UCM) Errors
Go to the home page if you want to do a search.

Simple, case-insensitive search:

NOTE: There may be more causes for the errors than the ones listed. The listed cause is just the one that caused it when I made the record. In addition, the solutions may not be the only solution, but the one that was used at the time.
The selected property page is currently unavailable because an error occurred while trying to access ClearCase data.
This error occurred when attempting to view the project Policy information via the Project Explorer GUI on NT. Cause unknown at this time.

Back to the INDEX.
cleartool: Error: Activity "activity" is setworked in view "view-tag".
cleartool: Error: Unable to remove activity "activity".
These errors occur when attempting to remove an activity that is currently set in a stream. The following will unset the activity so that it can be deleted. 
  # ct setact -none -view view-tag
Back to the INDEX.
IDispatch error #13273
This error occurred on an NT running CC 4.0 and CQ 2.0 while attempting to CQ-enable a UCM project. It means that the schema associated with the database to which you are connecting is currently checked out by someone. Simply check back in the schema and redo the CQ-enable.

Back to the INDEX.
IDispatch error #18005
A CException occurred, but no details are available.
This error occurred during checkout of an element in a VOB that is integrated with CQ using UCM. It occurred after the CQ record ID had been selected and the OK button clicked. UCM enabled schemas have a field called Project. The Project field must be filled in with the name of a Project to which your component VOB belongs prior to associating that ticket with a checkout.

Back to the INDEX.
IDispatch error #14094
Defect number does not exist or has already been deleted
Cannot set activity "activity" in view because of a ClearQuest error.
These error messages occurred when attempting to set a view to an acitivity. However, this view was already set to an activity associated with a ticket that no longer existed in CQ.
Under normal circumstances, a ticket cannot be deleted if an activity is using it. In this case, the database was moved and the UCM Project reconnected to it by clicking "Ensure All Activities Are Linked" in Project Explorer -> project -> Properties -> ClearQuest. If activities become disconnected from their respective tickets for some reason and the original tickets still exist, the activity and ticket will be correctly linked. However, in this case, after the database had been moved and before it was reassociated with the UCM project, some tickets were deleted (on purpose). If any activities cannot be relinked with their original ticket, a new ticket is created under the UCMUtilityActivity record type. So, a view was now set to a ticket that didn't exist in the Defect record type. Attempts to associate the view with a new activity produced the error message. A "ct setact -none" also produced the error. However, after logging out of NT and logging back in, the corrupt activity was no longer set. At this point, it is unknown if the "setact -none" really worked even though it gave the error, or the act of logging out and back in cleared the issue.

Back to the INDEX.
clearmrgman: Error: Unable to convert diffs to versions.
clearmrgman: Error: Unexpected error in deliver.
clearmrgman: Error: Unable to perform merge.
clearmrgman: Error: Unable to do integration.
These errors occurred when attempting to deliver a posted delivery in a UCM MultiSited environment. The Project Manager correctly reported that there were posted deliveries. However, the deliver button generated the error messages. In this case, the PVOB had been synced, but not the component. So, the Project Explorer knew about the posted delivery, but the component VOB had no data to work on. Simply ensure both the PVOB and component VOBs are synced at the same time.

Back to the INDEX.
Internal Error detected in "../map_cache.c" line 2191
This error occurred when attempting to join a UCM project on Windows in CC 5.0/2002 (no patches). An attempt was being made to use an existing development stream as the integration stream for a development stream heirarchy.
Immediately after upgrading to CC 5.0/2002 there won't be any recommended baselines in any integration stream. In the project explorer, right-click on the main integration stream for the project and select Recommend Baselines. This will also throw an error message unless you have already upgraded the feature level of the PVOB to 3 (see Change a VOB's feature level).

Back to the INDEX.
Error creating the recommended baselines for the stream.
This error occurred when attempting to recommend baselines. The project had several components, some read-write, some read-only. The error occurred because we tried to change the recommended baseline for one of the read-only components. But, this isn't how you change the baseline you see from a read-only component. That is, you are only allowed to "recommend" baselines that were created in the project. Baselines that are part of read-only components from another project must be simply rebased against. To see a different baseline for a read-only component, rebase the integration stream against a different baseline in that read-only component. By default, that single baseline you've rebased against is now the recommended baseline for your current project for that read-only component.

Back to the INDEX.
IDispatch error #18019
Failed condition: AdIsNonEmpty(def_name)
Location: ClearQuest Core:admetadatamgr.cpp:1844
This error occurred while attempting to CQ enable a UCM project running CC 2002 and CQ 2003.
Cause and solution unknown.

Back to the INDEX.
Unable to find replica in registry for VOB with object ID:"uuid"
Unable to locate versioned object base with object id: "uuid".
Root directory element for component "component" is unavailable.
Cannot get activity diffs for component "component".
This error occurred while attempting to complete or undo a delivery. The error most likely occurred because an unused MultiSite replica was removed while the deliver was in progress. The fix is unknown.

Back to the INDEX.


Return to the home page .

This page last modified: 05/24/2006