I have a very strange error today on windows ClearCase.
I encounter the following error while delivering from my old stream to the parent stream.
Meanwhile I made a new child stream on windows and delivered from there and it was OK.
The most amazing thing is I used the same old stream on unix and delivery completed without any problem.
What might be the reason behind this failure of my old stream on windows?
Do you wish to continue with this deliver operation? [no] yes
cleartool: Warning: Trigger "dlvr_start_pre" has refused to let deliver_start proceed.
cleartool: Error: A deliver_start preop trigger does not allow this operation.
cleartool: Error: Unable to do integration.
cleartool: Error: Unable to deliver stream "...".
You need to find that "dlvr_start_pre" script and see what it does.
This isn't a script automatically put by ClearCase: it has been written and put in place by your ClearCase admin, in a path accessible form any Windows workstation.
But you also need to consider your current ClearCase client.
For instance, "non-interactive triggers fail with warning about interactivity using CCRC or CCWeb".
That old stream could also have been created with different rights (owner/group) than the new one (that happens if the CLEARCASE_PRIMARY_GROUP environment variable changes)
Related
i just uninstall oracle 12c manually on windows 10 and now am reinstalling it shows errors:
Cause - Failed to access the temporary location. Action - Ensure that
the current user has required permissions to access the temporary
location. Additional Information:
- Framework setup check failed on all the nodes
- Cause: Cause Of Problem Not Available
- Action: User Action Not Available Summary of the failed nodes desktop-81i87ss
- Version of exectask could not be retrieved from node "desktop-81i87ss" - Cause: Cause Of Problem Not Available
- Action: User Action Not Available
In some cases, there is a possibility that your computer name contains some special character, unique installer throws same error in that case. Try removing any special character by renaming your system to a new name and then try installation again.
For Example: My system had name "LAPTOP-GENCONIAN". Problem was solved for me after renaming to "GENCONIAN"
I come across similar issue and was able to resolve with this method
Open CMD
CD into the folder in which setup file exits
3.Run the command - setup.exe -ignorePrereq -J"-Doracle.install.client.validate.clientSupportedOSCheck=false"
Now the intallation window will open without validation check and you can continue
Hi,
I am getting the below error when trying to update my view . Also, creds manager service is stopped and not getting started.
As long as the credmanager.exe is not started, none of the view (snapshot or dynamic) will work. So you need to debug that first.
Typically, you would check the ClearCase logs, and the Windows event, to see what the issue is. See "how to fix or investigate 'Operation “view_ws_is_ws_view” failed'?", using cleartool getlog.
That kind of error ("This application has failed to start becauselibatriaks.dllwas not found. Re-installing the application may fix this problem") was seen with rather old versions of ClearCase (7.0.1).
See for instance this thread.
If the DLL is present and the directory is in your path you should never
get this error.
Check to see how far ...\rational\clearcase\bin is down your SYSTEM path, and make sure the DLL's are in there.
ccgzip.exe will be called (by the client process) when checking in any files that fall back to the "compressed_file" element type. It may be called by the view server during file opens and checkouts to construct cleartext if needed. The former uses your user path, the latter will normally use the SYSTEM path.
We've seen odd behavior on Windows when the path gets >500 characters
long, though there seems to be no "official" limit to the length this environment variable (%PATH%) can grow to.
The error message you see is likely a path issue. Whether that's related to the other issue is unknown...
Is the albd server process running? The credential manager service is flagged to depend on this service. If that service fails to start, or terminates, the credential manager service will also fail.
A service startup failure should be in the Application or System Event logs. and from there the "Troubleshooting albd startup failures" technote on ibm.com would likely be a good place to start.
Every time I try to copy clearcase file from view location to another location, it generates the following error:
The file cannot be opened because it is being used by another process.
Please close all applications that might access this file and try again.
Any ideas why this is happening?
That explains probably your previous question: some process must keep an handle on the files you want to copy.
Try to close as many apps as you can, or even try that copy just after a reboot.
That is not a ClearCase issue. Its totally Windows one. You need not to close all apps to find the lock. try to install the "unlocker" application it will notify you what is locking your process
http://download.cnet.com/Unlocker
Enjoy,
Eli
I tried to update a clear case view with CCRC tool. Sometimes the view will be locked if last update was aborted for some reason, and couldn't be updated before the lock is broke. Is there anyone could help to tell me how could I unlock this view with CCRC tool?
Here's the error message when i run command update in rcleartool.
CRMAP7009: CCRC command "Update" failed: Error:
"com.ibm.rational.clearcase.remote_core.copyarea.CopyAreaLockedException:
Copy area "/Users/vizmacmini2/Jenkins/jenBranch941u1_vizmacmini2" is
locked by another process. Retry the request once that operation
completes. Lock info: last-refreshed:Nov 14, 2013 5:38:02 PM
locked-on:Nov 14, 2013 4:41:07 PM user-id:vizmacmini2
hostname:10.197.40.115 process-id:unknown." conflict
If the file is locked because of a process keeping an handle on it, it can be as simple as killing that process, and relaunching the update through the CCRC Navigator View
Refresh > Update from Repository
Regarding a ""com.ibm.rational.clearcase.remote_core.copyarea.CopyAreaLockedException" error message, the IBM help page mentions:
The Copy Area Locked prompt appears when ClearCase encounters a copyarea.lck file after a user has attempted to rebase or deliver from a ClearCase Remote Client that resides on the same machine as the ClearCase native client.
So I suspect that your script need to find and remove that copyarea.lck file, in order to proceed.
But I would also recommend to check why (or if) there is a pending rebase or deliver in progress.
It would be best if that "rebase or deliver" was fully completed before your script runs.
The OP jingxw adds in the comments:
The progress is pending because of last progress is fail due to a timeout or manually quit. So the lock is expected.
Why do I get these .MKELEM files? How do I get rid of them?
I found some docs that said they are temp files created by ClearCase GUI when adding files to source control. But sometimes, they don't go away.
ADDITIONAL INFORMATION: I "get access denied" trying to delete or rename the .MKELEM. They seem to get created when I add new files to clearcase.
As mentioned in the mkelem tip page:
During the element-creation process, the view-private file is renamed to prevent a name collision that would affect other Rational® ClearCase® tools (for example, triggers on the mkelem operation). If this renaming fails, you see a warning message.
If a new element is checked out, mkelem temporarily renames the view-private file, using a .mkelem (or possibly, .mkelem.n) suffix. After the new element is created and checked out, mkelem restores the original name. This action produces the intended effect: the data formerly in a view-private file is now accessible through an element with the same name.
If mkelem does not complete correctly, your view-private file may be left under the .mkelem file name
The fact that a .mkelem stays can be, like LeopardSkinPillBoxHat mentions in his answer, because of a file blocked due to a process.
It can also happens:
in ClearCase view incorrectly protected (where ClearCase can checkout the new element, creating a version 0, but cannot check that element in.
alt text http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m1/topic/com.ibm.rational.clearcase.dev.doc/topics/cc_dev/images/creating_element.gif
when a trigger prevents the checkin part of the new element creation
when the view actually exclude CHECKEDOUT versions! (no 'element * CHECKEDOUT' rule...)
on Solaris 10, due to an incorrect format in one of the ClearCase jvm config file. (ClearCase 7.1)
when add to source control is used on Windows in views mapped to a mount point (Mount points are persistent directories that point to disk volumes), only in old ClearCase 2002 or 2003.
See also the Under the hood: What happens when you add to source control article.
The .mkelem files are temporary files generated by ClearCase when adding a file to source control. If the file gets added succesfully, they are usually deleted. If something goes wrong during the process (e.g. it cannot create the branch specified in your config spec), the .mkelem file may be left behind.
I'm guessing that a process or service somewhere has a lock on the file. Rebooting should fix the problem. Or try using something like Process Explorer to see what may have locked the file.
Also, from this page:
.mkelem
Files being added to source control
from the GUI will use this extension
during an "Add to Source Control"
operation.
If you see this file in your view
during the mkelem process, that is OK.
If you still see the file after the
mkelem operation is complete, that is
not ok. You will likely need to rename
the file (remove the .mkelem
extension) and add it to source
control again. This can be seen when
your antivirus software is scanning
the mvfs. Refer to technote 1149511
Support Policy for Anti-Virus and
ClearCase for further information.
You may try the following from command prompt:
ct ls -l {filename}.mkelem
This will show the links,
then please try the following to link the actual file:
ct ln -c "scm:relink" {link} {actual filename}