Eric J Ostrander's

ClearCase / ClearQuest / Git/Stash "how to" pages.



Unified Change Management (UCM) Errors




Go to the home page if you want to do a search.

Simple, case-insensitive, site-wide, search (your browser must allow scripts to run):

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
Updated: 06/02/14
Version: 7.1.2

This error occurred while attempting to CQ enable a UCM project.
The cause is unknown. When integrating a UCM project, no other changes can happen to the CQ database, or that error will occur. The error will be accompanied by other errors when attempting to log in via the web, or run an existing query in the full client. Finish the integration and/or restart the integration when no other activity is going in the same CQ db.
The error only seemed to occur for a subset of records though.

When the following command was run from the CLI after receiving the error, the same error occurred again for the same number of unlinked records, but they got UCMUtilityActivity records this time. That is, even though the error occurred again, the records appear to be linked. WARNING, don't run the chproject command again though, as it will create duplicate UCMUtilityActivity records for the ones that received the error the first time. So, even though the activities causing the error appear to be linked, the command will re-process them anyway.
	cleartool chproject -crmenable user-db -connection schema-repo project

On further inspection of the existing activities that were linked when the UCM project was integrated with CQ, some activities had the same title. When not integrated with CQ, the users were allowed to make up an activity "title", which automatically becomes the "name". Apparently some users wanted to re-use the same title, so they created a new activity, which got a new name, but then changed the title to be same as an existing one. This looks like it may have caused problems during the integration. Also, ultimately in CQ there now UCMUtilityActivity records that have the same headline, but different change sets, which is confusing. Fortunately, after integrating the two tools, those problems go away.

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.




Can't link an object into a directory with a different component root directory.
Updated: 12/20/11
Version: 7.0.1.8
This error occurred after renaming a component that was a sub-VOB component. Renaming the component itself doesn't rename the directory it's associated with in the VOB. The error occurred when attempting to rename the directory in the VOB.
Directories that are component roots inside a multi-component VOB cannot be renamed. See: http://www-01.ibm.com/support/docview.wss?&rs=984&uid=swg21135606

Back to the INDEX.




cleartool: Error: Object is in unexpected VOB: "record-id@vobtag".
Updated: 01/12/12
Version: 7.0.1.8
This error occurred when attempting to set an activity into a view from the CLI.
If you use setactivity, you can simply provide the activity ID. If you specify a full activity-selector including the VOB, you must explicitly specify the PVOB and not the working VOB.
NOTE: It shouldn't be necessary to specify the PVOB though. If you're sitting inside the correct view no the CLI, the system will understand where to find the activity. If you specify -view, say from a script or sitting on the C: drive, the system will understand that the view is associated with a given UCM project and will automatically find the PVOB.

Back to the INDEX.




The UCMUtilityActivity "..." has been recently modified. Aborting delete action.
Updated: 01/18/12
Version: 7.0.1.8
This error can occur when attempting to delete a UCMUtilityActivity from a script or from the GUI.
UCMUtilityActivity records cannot be deleted if there are any entries in the change set.
If the change set is empty, in the GUI simply reload the record in a query and try the delete again. In a script, reload the entity object before attempting the delete.
	$entity->Reload;$session->DeleteEntity(\$entity,"Delete");

Back to the INDEX.



Error creating component
Updated: 05/28/13
Version: 7.1.2.4
This simple error occurs when attempting to create a new component using the GUI.
This error can occur for any of the following reasons:
• Prior to 7.0, if the root VOB was not mounted.
• If "Create a Component in a VOB" and the specified VOB is a single-component VOB. Instead, use Import -> VOB as Component.
• The component name has non-alpha-numeric characters, such as spaces, in it.
• You don't have sufficient permissions in the PVOB to create a component object.
• A trigger is preventing creation of the the root folder.

To get a better error message, run the mkcomp command from the CLI. For example, if creating a component within a VOB, run the mkcomp command in the top level folder of the VOB.
	ct mkcomp -root component component@\myPVOB

Back to the INDEX.



Error determining recommended baseline(s) for this project. Not a vob object:
Updated: 06/05/13
Version: 7.1.2
This error occurred when attempting to join a project that had not been joined by anyone before.
The cause is unknown.
See http://www-01.ibm.com/support/docview.wss?uid=swg21131415 for a possible solution.
Basically, just run the following command to clear all the recommended baselines from the stream and then re-recommend the desired ones.
	ct chstream -nrecommended stream-name@\pvob-tag

Back to the INDEX.



INTERNAL ERROR detected and logged with the NT Event Service. See the Event Viewer for the error message.
Internal Error detected in "\atria\lib\sum\sum_activity.cxx" line 469. Unexpected error. Name "stream:activity-id already exists.

Updated: 11/27/12
Version: 7.1.2
These errors occurred when attempting to check out a file for the first time using a new Activity in a new UCM project.
The stream/branch name cannot be the same as the activity. In this case, the UCM project was integrated with CQ. The Activity id was "C9HLT00003787", so the UCM activity had the same name. Therefore, when joining the project, don't name the stream "C9HLT00003787". Instead, name it something like "C9HLT00003787_dev".

Back to the INDEX.




The ClearQuest connection dbset for database db is not valid, please verify the connection name.
Updated: 11/28/12
Version: 7.1.2
This error occurred when attempting a deliver from a development stream to its default integration stream on the CLI.
The deliver was being made in a Perl script using CAL. While the CAL system can make external cleartool calls that are not provided for in the CAL library, it fails if the call needs to connect to make a UCM connection to CQ. For unknown reasons, the CAL fails whenever SQUID is needed, which is true during a CQ-integrated UCM deliver.
The solution is to make a plain system call to run the deliver: system("cleartool deliver ...

Back to the INDEX.




cleartool: Error: Integration activity change set is not empty. cleartool: Error: Unable to cancel deliver.
Updated: 03/29/13
Version: 7.1.2
This error occurred when attempting to resume or cancel a deliver from a regular development stream to the default integration stream. It's unknown how the delivery got into this condition, nor what the real problem is, but the delivery needs to be cancelled manually using command line cleartool commands. The following talks about "rebase", but it's essentially the same error: http://www-01.ibm.com/support/docview.wss?uid=swg21179696

Back to the INDEX.




cleartool: Error: No tag in region for view "uuid".
Updated: 05/30/13
Version: 7.1.2.4
This error occurred when attempting to remove a stream. See http://www-01.ibm.com/support/docview.wss?uid=swg21127922 for a solution. Basically you need to rmview the view reference from the PVOB.
	cd PVOB
ct rmview -uuid uuid

Back to the INDEX.



Unable to retrieve modifiable component list of project
Updated: 05/31/13
Version: 7.1.2.4
This error occurred when attempting to view a project's policies.
The cause was deleting a component that was listed as modifiable in the project.
Solution #2 fixed it: http://www-01.ibm.com/support/docview.wss?uid=swg21443204

Back to the INDEX.




Can't use baseline "bl" of component "comp" because it is not an ancestor of the stream's foundation baseline.
Updated: 06/19/13
Version: 7.1.2.4
This error occurred when attempting to recommend a new component baseline in a stream.
The cause and solution are unknown.

Back to the INDEX.




Internal Error detected in "\atria\lib\sum_stream.cxx" line 608.
Updated: 06/19/13
Version: 7.1.2.4
This error occurred when attempting to recommend a new component baseline in a stream.
The cause and solution are unknown.

Back to the INDEX.




cleartool: Error: The remote procedure call failed. Unable to complete a rebase or deliver because the destination is corrupt or missing.
cleartool: Error: Unable to find view by uuid:UUID, last known at "unknown:unknown".
Updated: 07/19/13
Version: 7.1.2.4
This error occurred when attempting to complete a deliver to an integration stream. For an unknown reason, the integration view used to start the deliver was no longer available.
The cause of the original "remote procedure call failed" is unknown. The reason the integration view was missing is unknown. However, the delivery can be completed by using a new integration view and telling the deliver -complete to use that other view.
	ct deliver -complete -stream stream:stream-name@PVOB -force -reset -to new-integration-view

Back to the INDEX.



Unable to find replica in registry for VOB with object ID: "UUID".
Updated: 07/23/13
Version: 7.1.2.4
This error occurred when attempting create a view for a UCM stream.
The stream is created in the PVOB, the PVOB is synced with a remote site, but the associated component/VOB has not been replicated to that remote site.

Back to the INDEX.




cleartool: Error: Unable to resolve component root directory
Updated: 07/23/13
Version: 7.1.2.4

This error occurred when attempting create a component inside a VOB from the CLI.
The real cause is unknown, but running the command from within the VOB solved the problem, as in:
	C:\> M:
M:\> cd myview_generic_view\MyVOB
M:\myview_generic_view\MyVOB> ct mkcomp -root component-name component-name@\MyPVOB

Back to the INDEX.



Version map for baseline "baseline" is unavailable.
Updated: 08/09/13
Version: 7.1.2.4

This error occurred when attempting create a UCM view.
This is generally caused by multi-sites being out of sync. That is, this is most likely a multisite synchronization issue. Need to look at outgoing and incoming packets and epoch tables for the sites involved.

This error can also occur if a set of VOBs are copied to another storage location. If the VOBs weren't locked during the copy, there's a chance that a change was made to one VOB, say a PVOB, that wasn't there when a component VOB get copied. Baselines and such will be out of sync then.

Back to the INDEX.




cleartool: Error: There are no credentials registered for database db.
Updated: 08/20/13
Version: 7.1.2.4

This error occurred when attempting setactivity inside a scheduled job while the job's owner was logged out. This error was accompanied by a request for the user to run the crmregister command.
The crmregister command was known to be correct, as the scheduled job would run without errors while the user was logged in.
To ensure a scheduled job gets run with the correct privs while logged out, perform the following steps.

1) Open the Control Panel -> Administrative Tools -> Component Services.
2) Navigate to Component Services -> Computers -> My Computer.
3) Right-click to get the Properties and go to the "COM Security" tab.
4) Perform the following steps for both the "Access Permissions" and "Launch and Activation Permissions".
a) Click on Edit Default.
c) Add the user that needs to run the scheduled job while logged out.
d) Ensure Local Access and Remote Access are checked.
5) Close Component Services.

Back to the INDEX.




cleartool: Error: Unable to deliver stream "stream-name".
Updated: 06/18/14
Version: 7.1.2.4

This error occurred when attempting a deliver from the command line on a Linux build server.
The specified -to "view" was not associated with the destination stream. The following command will return the name of the stream associated with the view. If nothing is returned, it probably isn't a UCM view.
	ct lsstream -s -view view-tag

Back to the INDEX.



Merge Manager: Error: An error occurred while merging file elements in the target view.
Updated: 02/23/16
Version: 2003

This error occurred when attempting a graphical rebase on Solaris. The user had previously, successfully performed graphical rebases using the same development view.
The cause and solution are unknown yet. Back to the INDEX.



cleartool: Error: Unable to set activity.

Updated: 03/09/16
Version: 2003

This error occurred when attempting a setact on the CLI on Solaris.
The user does not get this error message for other CQ databases.
The solution was to perform an actual checkout inside xclearcase. The user had changed their password. Unfortunately, the lab they were in was running CC 2003, which didn't yet have crmregister and they were only working from the command line. Performing the checkout and uncheckout in xclearcase cached the CQ db password.
Note that just logging into CQ itself on the same machine doesn't cache the CQ password for the purpose of the CC/CQ integration.

Back to the INDEX.




cleartool: Error: Unable to cancel rebase because another operation is trying to complete.
Updated: 05/04/16
Version: 7.1.2.14

This error occurred when attempting to cancel a rebase that was stuck for a very long time. The view used in the original rebase was removed. The normal way of cancelling a rebase when the view is missing resulted in the error. That is "... -cancel -reset -view view -force ..." didn't work.
For some reason, forcing a complete of the original rebase worked:
	ct rebase -complete -stream stream@pvob -reset -view view -force

Back to the INDEX.



cleartool: Error: Cannot get view info for current view: not a ClearCase object.
cleartool: Error: Cannot determine view context.

Updated: 05/05/16
Version: 7.1.2.14

This error occurred when attempting a describe an activity from the Unix CLI.
You must be set into a view configured for the stream associated with the activity being described.

Back to the INDEX.

ejostrander@cox.net