Clearcase CCRC command 'checkin' failed: Unable to create pathname for file - clearcase

I have CM Server for ClearCase Remote Clients in windows 2003 server.
Installed package in server.
I'm getting below error in CCRC client:
"CRVAP0087E CCRC command "checkin" failed: Unable to create pathname for
file "C:\ccweb\v973012\v973012_Latest_FMC": Permission denied"
Can you please help me to fix this issue?

The most efficient way to troubleshoot right issue is to go directly to the CCRC server, under the CCRC web (snapshot) view and type:
cd c:\ccweb\v973012
cleartool lsview -l -full -pro -cview
That way, you see with which group the user has created the CCRC view in the first place.
That group must be one of the groups associated with the Vob of the element being checked-in.
Check also this technote:
During the installation of Rational ClearCase, you are asked for a temporary directory to use during the installation to unzip large artifacts.
This temporary directory is used to preserve user configuration settings during an update or uninstall process.
If you specify a directory that is mounted on a file system that is separate from the installation directory, the file permissions and owners are not preserved when the files are moved across the file systems.
Finally, check for any trigger set on the Vob: they can have an unwanted side-effect with that CCRC 'checkin' operation.
In the specific case of the OP mth123, he suggests:
Go to the Windows Explorer and try these steps:
Go the the following directory: C:\ccweb
Rename the folder v123412 to V123412 (Only change the first letter and put "V" capitalized.)
Check if the problem is solved.
So depending on the actual tag of the view, this could be an issue about case-sensitive path.

The latest patch caused this issue. While applying patch CC preserving some file inclusing ccweb folder. while restoring those folder during post install these directory might have changed with lowercase/upper case. This is currently with IBM queue.
If you are going to upgrade CCRC please make a copy of ccweb directory with proper ACL or use ccopy.exe (clearcase utility)

Related

How to resolve .checkedout file in IBM Clearcase?

My eclipse suddenly shut down, and after that for a particular file, there are two files present:
the main file and
a .checkedout version of it.
Now the main file is not checkedout out from my machine, still if anyone else tries to check out the file: it shows it is checked out already.
I have seen from Clearcase explorer too, it is the same there.
Any solution for this?
It depends on the version of ClearCase (client and server, including their OS), and of the type of ClearCase view you are using (snapshot, dynamic, web view)
But in general, if a file is checked out and should not be, you can delete any checked out status associated to your view.
However, please note it will cancel all your checked out files done in this particular view (for that particular Vob), so make sure it won't impact your current work in progress (save it first elsewhere to be safe).
cleartool descr -l vob:\myVob
# get the uuid of the user's view from the description of the vob
cleartool mount \myVob
cd m:\mynewView\myVob
cleartool rmview -force -uuid old_view_uuid
Note: you can also get your view UUID with
cd path/to/my/view
cleartool lsview -l -full -pro -cview
That way, nobody else will see any of your previously checked out file as "checked out".
Note that a .checkedout file is typically the result of a failed checkout for permission issue.
Example:
Unable to rename "M:\myView\myVob\path\to\afile.png" to "M:\myView\myVob\path\to\afile.png.keep": Permission denied.
Checked out version, but could not copy data to "M:\myView\myVob\path\to\afile.png" in view: File exists.
Correct the condition, then uncheckout and re-checkout the element.
Copied checked-out version data to "M:\myView\myVob\path\to\afile.png.checkedout".
Checked out "M:\myView\myVob\path\to\afile.png" from version "\main\myStream\0".
Attached activity:
activity:deliver.stream_myStream.20120426.115512#\myPVob

Setting up ArangoDB cluster wihout DCOS

I'm working on setting up an ArangoDB cluster in an Ubuntu machine based on these instructions :
https://docs.arangodb.com/3.0/Manual/Deployment/Distributed.html
I keep getting the below error when i execute the first command in the above documentation with sudo. I ensured that all the directories
pointing to in the /etc/arangod.conf file has the required permissions. Please can you let me know if i'm missing something here.
Below is the error i get :
2016-08-23T07:29:52Z [26629] FATAL unable to create database directory: Failed to create directory [agency1] Permission denied
The command passes the database directory on the command line (agency1) and arangodb doesn't seem to have rights to create agency1 in your current working directory.
Either provide a proper working directory on the command line or specify one in the config file.
You need to first change the directory to /var/lib/arangodb3 or whatever data directory you have set and then run the command.

How to make a recursive checkout of files & subdirectories with CCRC

I am using following version of clearcase -
Rational ClearCase Remote Client Version: 7.1.2
In my attempt to checkout files and folders recursively, I read these links:
How do I perform a recursive checkout using ClearCase?
http://www.ibm.com/developerworks/rational/library/4687.html
The issue is I am not able to locate these bin files used in these articles:
cleartool.exe not located in (c:\Program Files\Rational\ClearCase\bin\cleartool.exe)
clearmenuadmin.exe not located in (C:\Program Files\Rational\ClearCase\bin\clearmenuadmin.exe)
Not to mention windows search could not locate any of these files in C:\Program Files.
Please suggest what I am missing here ?
You cannot use cleartool commands with CCRC, only the GUI and CCRC/Teamapi (as in "Rational clear case CM API fail to checkout source code").
The CCRC is a ClearCase Remote Client, with none of the executables of a full ClearCase client.
Maybe the simplest way is to use Use "Environment -> ClearCase Search" GUI, to search for all elements, and select them all to checkout them.

Using WinMerge as ClearCase diff viewer for xml files

I just installed WinMerge and checked its "Integrate with ClearCase" option. ClearCase now runs Winmerge when i execute "compare with previous version" on my java source files. However, when I run the same command on an xml file, it opens xml diff merge. How can I get it to open Winmerge instead?
See for instance "How do I integrate Beyond Compare with ClearCase?"
You need to modify
# up to ClearCase 7.0
c:\program files\rational\ClearCase\lib\mgrs
or
# ClearCase 7.1 and more
c:\program files\IBM\RationalSDLC\ClearCase\lib\mgrs
See the technote swg21256807 for detail on Changing the XML Diff/Merge Type Manager.
For any type manager that uses xmldiffmrg, replace the xmldiffmrg executable with your own.
Example (not for your tool, but you get the idea):
_xml2 compare ..\..\..\..\KDiff3\KDiff3.exe
_xml2 xcompare ..\..\..\..\KDiff3\KDiff3.exe
_xml2 merge ..\..\..\..\KDiff3\KDiff3.exe
_xml2 xmerge ..\..\..\..\KDiff3\KDiff3.exe
Note: The mapfile uses a relative path from its current location to find the executable.
In this example, KDiff3 was installed to the default directory on Windows (C:\Program Files\KDiff3) thus the relative path defined in the map file reflects as such.

Unable to resolve symlink

When updating my clearcase (snapshot) view I get the following symlink errors:
Unable to resolve symlink
"setups.cmd". The symlink
target will not be loaded.
Unable to resolve symlink "setup.sh".
The symlink target will not be loaded.
Unable to resolve symlink
"setupwithdomain.doc". The
symlink target will not be loaded.
What do I do or tell my admin to do to get rid of this errors.
Are you on Windows? And with which ClearCase version
There is this IBM Technote, which explains why attempts to create an IBM Rational ClearCase symbolic link on Microsoft® Windows in ClearCase Explorer from a snapshot view fails when the snapshot view root is created with a lower case drive letter.
But that would only be for CC2003.
This thread mentions a similar issue:
We have had problems resolving symlinks when loading snapshot views.
It appears that the resolution of the pathname to the linked file is case sensitive.
The solution for us was to ensure that all symlinks used the correct case for the pathname to the linked file.

Resources