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.
b) Click Add.
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: LDAP Authentication failed because an empty password was supplied. Failed condition: AdCryptIsNonEmpty(username)
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 can log into CQ on the same machine.
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
Return to the home page .
This page last modified: 08/27/2020