Load rule scope returns error pathname does not begin with a \

why an IBM® Rational® ClearCase® CCRC or CCWeb view results in the error Error: Pathname "load \" is not a full VOB pathname: it does not begin with a "\". after adding a new load rule, and gives steps to resolve the problem.

Cause

When submitting load rules in the Load rule scopes of a ClearCase Web or ClearCase Remote Client view the following occurs: ccweb: Error: Pathname "load \\" is not a full VOB  pathname: it does not begin with a "\" There are two possible causes to this problem: 1. The config spec was manually edited as if it were a standard snapshot view. Although standard snapshot views require the word load at the beginning of the load rule, these are not required when editing a CCWeb or CCRC load rules. Example (using a Windows VOB): load \myVob element * CHECKEDOUT element * /main/LATEST 2. It is also possible that an incorrect VOB path was used. For example a VOB does not have a slash or has an incorrect slash. Example: myVob element * CHECKEDOUT element * /main/LATEST

Solution

Solution 1: Remove the word load from the load rule. Solution 2: Ensure the correct VOB pathname is used paying attention to the slashes (forward slashes / for UNIX® or Linux™ and back slashes \ for Microsoft® Windows®) and make sure there are no spaces before the VOB pathname in the rule. An example config_spec should look as follows for Windows: \myVob element * CHECKEDOUT element * /main/LATEST An example config_spec should look as follows for UNIX or Linux: /vob/myVob element * CHECKEDOUT element * /main/LATEST

CCRC cheat sheet fails to open

why attempts to open the IBM® Rational ClearCase® Remote Client cheat sheet called Tutorial: Getting started with base ClearCase (Eclipse) for the stand-alone client will generate errors when the action buttons are clicked.

Cause

Access the cheat sheet by clicking Help > Cheat Sheets. The only cheat sheet that is applicable to the Stand-alone application is Tutorial: Getting started and working with base ClearCase (standalone client) The other two are only applicable if using Eclipse with the ClearCase Remote Client plug-in.  Tutorial: Getting started with base ClearCase (Eclipse) Tutorial: Working with base ClearCase (Eclipse) Here is how the options as they appear: An example of when the problem occurs is in the Creating an Eclipse workspace for your ClearCase view module; using the Click to Perform button will generate the following error: A Problem Occurred "Reason: The action could not be run because the class 'com.ibm.rational.clearcase.ui.actions.OpenWorkspaceAction' could not be loaded." This problem has been logged as defect RATLC00730381.

Solution

This defect has been resolved in release 6.14.3 of CCRC. Review the Updated Release Notes for the ClearCase Remote Client for more information as well as the location of the CCRC update packages.

No locks available error from CCRC on Red Hat Linux

Problem

This technote describes a problem starting the IBM® Rational® ClearCase® Remote Client (CCRC) on Redhat® Linux™, along with instructions to solve the problem.

Cause

Attempts to start CCRC (stand-alone application) on Red Hat Linux results in the following error: An error has occurred.  See the log file                /.eclipse/configuration/.log Upon review of the log, the following message related to the error states: "/ /.eclipse/configuration/org.eclipse.core.runtime/.manager/.fileTableLock": "No locks available". This problem relates to one of two problems: The file system is not enabled to properly handle file locking. This problem can be the result of the statd (network status monitor) and lockd (network lock daemon) daemons being stopped on the machine that CCRC is installed on. An unsupported version of Java Runtime Environment may be in use on the CCRC host.

Solution

One of the foloowing solutions will resolve your issue: Make sure lockd and statd are started on the machine that the ClearCase Remote Client is installed on. Refer to the appropriate man pages on lockd and statd for more information. Review technote 1181478 for more information about the supported JRE versions for use with ClearCase.

RWP and WWW Publishing Service on Windows Server 2003

why the IBM® Rational® ClearCase® Remote Client (CCRC) cannot be accessed when hosted on Microsoft® Windows Server™ 2003 if the World Wide Web (WWW) Publishing Service is running.

Cause

After installing Rational ClearCase on Windows Server 2003, attempts to start the Rational Web Platform (RWP) service results in an error. Go to Start > All Programs> Administrative Tools > select Services, right-click Rational Web Platform, HTTP server, and click Start: ERROR: [Services] ! Windows could not start the Rational Web Platform, HTTP server on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to the service-specific error code 1. This service must be running to access the ClearCase Web Interface (CCWeb) and or CCRC on this web server. However, there is a conflict preventing the RWP service from starting if the WWW Publishing Service is already started. In this configuration, the RWP service cannot coexist with the World Wide Web Publishing Service on Windows Server 2003. Note: This error does not occur when starting the RWP service on Windows 2000 even if the WWW Publishing Service is running.

Solution

Stop the WWW Publishing Service, then you will be able to start the RWP service. 1. From the Services window, right-click the World Wide Web Publishing Service and select stop. The status will no longer be listed as Started: 2. When the WWW Publishing Service is stopped, right-click Rational Web Platform, HTTP serverand select Start. The service will start with no errors, and the status will be listed as Started. Once the service is running, CCRC (or CCWeb) can be accessed on this web server.

The directory is not a valid location for a web view

why attempts to create an IBM® Rational® ClearCase® Remote Client (CCRC) or ClearCase Web (CCWeb) view results in the error The directory is not a valid location for a web view.along with steps to resolve the issue.

Cause

Either the directory tree to which the view is being created does not exist Example: Attempts to create a new web view at C:\webviews\ccrc_view will fail if the directory webviews does not exist. or The directory being designated as the view root (private workspace) is either already a view root for another view, or is a sub directory of an existing view root. Example: Attempts to create a new web view at C:\webviews\ccweb_view will fail if either the directory webviews or C: has been previously designated as storage for another view.  Check for the existence of one or both of the following files in both directories (in this example webviews and C:): .copyarea.dat .copydb.dat These files represent the home of a CCRC or CCWeb view and effectively invalidate the use of the directory (or its sub directories) as a view root for other views.

Solution

1. Ensure the directory tree structure is in place. If the directory is missing, create it and recreate the view.  Note: This is expected functionality as a CCWeb or CCRC views cannot be created in a nonexistent location. This is to prevent mistakes in typing an incorrect pathname which would result in an entire directory tree that is not wanted or needed. 2. Until the two files (.copyarea.dat & .copydb.dat) are removed either by removing the view through CCWeb or CCRC (recommended) or by hand using operating system delete operations (not recommended), a new CCRC or CCWeb view cannot be created in that path space. Choose a different location to store the view.

CCRC installation error on Linux: jvm is not defined

why a jvm error is displayed when installing the IBM® Rational® ClearCase® Remote Client on Linux®.

Cause

A jvm not defined error is displayed at the end of an install when CCRC setup is initiated using the setup.jar file rather than the setup.bin file. Example: java -jar /disk1/setup.jar

Solution

When installing the ClearCase Remote Client on Linux, use the following command: java -jar /disk1/setup/setup.bin

Error creating an IBM Rational ClearCase Remote Client View

This technote outlines two possible causes why attempts to create an IBM® Rational® ClearCase® Remote Client view results in the error:Unable to login to the specified server. along with instructions to resolve the problem.

Cause

Creating a view in CCRC using a UNC or other type of path in the ClearCase Web server URL section can result in the error Unable to login to the specified server. Error: "java.langlIllegalArugmentExceptions: host parameter is null" or Unable to login to the specified server. Error: "Malformed ClearCase Web Server URL: "\\host\ccrc"" Example: BEFORE: AFTER: Cause 2 This error can also be received if attempts are made to connect to a CCRC server that is behind a firewall which requires authentication prior to access.

Solution

Enter the proper URL string (not path) to the CCRC web server. Example:http: ///ccrc Solution 2 Authenticate through the firewall prior to using CCRC.

Unable to initialize group list for user error from ClearCase Web applications

why logging into an IBM® Rational® ClearCase® console through the ClearCase Web, ClearCase Remote Client or the MultiSite® Administration Web console, yields the error: unable to initialize group list for user , along with the steps to resolve the problem.

Cause

This error can be returned when the permissions on the ccweb executable are not set correctly. Check the permissions on the ccweb executable by running: $ ls -l /usr/atria/web/bin/ccweb  (2002.05.00) or $ ls -l /opt/rational/clearcase/web/bin/ccweb (2003.06.00) The output should be similar to: -r-sr-xr-x   1 root     other     376316 Sep 22  Note: This executable should be owned by root, it does not matter what the group is. One of the symptoms will be an error message in the logs (such as /var/adm/messages) on the system such as: ccweb: Setuid execution not allowed In the RWP error_log file, you will also see the following entry: setgroups: Not owner

Solution

The permissions for the ccweb executable should be r-sr-xr-x. Note that the set-uid bit is enabled. This ensures that this application is run as 'root' even when other users execute it. If the set-uid bit is not enabled, enable it by running the following command as root: $ chmod u+s ccweb (or $ chmod u+s /opt/rational/clearcase/web/bin/ccweb) If this does not seem to solve the problem, and the filesystem where the ccweb application resides is mounted using NFS, check the mountpoint settings, specifically for the presence of the 'nosuid' mount option, documented in the man pages of mount_nfs: suid | nosuid    Allow or disallow setuid execution. The default    is suid. You can see this by looking at your operating system mount tables (such as /etc/vfstab or /etc/mnttab) for signs of the 'nosuid' option. Example: . . . /opt on /dev/vg00/lvol5 delaylog,dev=40000005 on Fri Apr 7 15:04:38 2006 /opt/web/server on /dev/vg01/lvol11 nosuid,delaylog,dev=4001000b on Fri Apr 7 15:04:38 2006 /opt/web/content on /dev/vg01/lvol12 nosuid,delaylog,dev=4001000c on Fri Apr 7 15:04:39 2006 /opt/scopus on /dev/vg01/lvol14 nosuid,delaylog,dev=4001000e on Fri Apr 7 15:04:39 2006 /opt/oracle on /dev/vg01/lvol2 nosuid,delaylog,dev=40010002 on Fri Apr 7 15:04:39 2006 /opt/CCASE_2003A on /dev/vg01/lvol20 nosuid,delaylog,dev=40010014 on Fri Apr 7 15:04:39 2006 . . . If this setting needs to be changed, it will be necessary to redo the mount of the affected filesystem. Consult your system administrator or operating system manuals for assistance.

Cannot delete or rename elements with long pathnames in Eclipse 3.0

This technote identifies a problem where attempts to delete or rename an IBM® Rational® ClearCase® element that has an extremely long pathname from within the Eclipse 3.0 IDE using the ClearCase Remote Client (CCRC) plug-in , does not wrap the text in the pop up confirmation dialog box causing the Yes or No buttons to be cut off.

Cause

The CCRC plug-in is running under Eclipse 3.0. Eclipse 3.0: Note: The stand alone version of CCRC does not exhibit this problem.

Solution

Upgrade to Eclipse 3.1 or later and the text will be wrapped in the pop up dialog box, enabling you to click the Yes or No buttons. Eclipse 3.1:

Black squares are in the CCRC task bar instead of icons

why the task bar icons for IBM® Rational® ClearCase® Remote Client (CCRC) are appearing as black squares and provides solutions to resolve the issue.

Symptom

Attempts to use CCRC results in black squares appearing in place of the task menu buttons and directory tree icons:

Cause

This can occur due to the Buffer Overflow Protection option being enabled for McAfee VirusScan Enterprise 8.0i. Note: This behavior is also known to occur when using some IBM WebSphere® products, refer totechnote 1180700 for more details. Cause 2 This problem can also occur when your local image directory for the glyphs are corrupt, specifically  C:\Program Files\IBM\Rational\ClearCase\CCRC\plugins\ com.ibm.rational.clearcase_\icons  Cause 3 This problem can also occur when there is spyware installed on the machine. Example: Fiddler and its related RPASpy was found to be problematic.

Resolving the problem

The latest patches for McAfee VirusScan Enterprise 8.0i must be installed on the local host, which can be obtained directly from McAfee, see article KB40531. For assistance contact McAfee Enterprise Support. WORKAROUND: Until the McAfee patches are installed, the behavior can be corrected by disabling the Buffer Overflow Protection. For directions, refer to the McAfee VirusScan Enterprise 8.0i Product Guide. Solution 2 Remove if needed or simply reinstall the plug-in to fix the corrupt glyphs in the icons directory. Solution 3 Remove the spyware application if it is determined to be conflicting with ClearCase.

Error when installing CCRC.NET: The prerequisite software for clearcase visual studio .net integration is not installed

why the error The prerequisite software for clearcase visual studio .net integration is not installed occurs when attempting to install IBM® Rational® ClearCase® Remote Client (CCRC).NET on Microsoft® Windows®.   Symptom If the machine, where the CCRC.NET should be installed is a clean machine with only Visual Studio 2008 installed, the CCRC install of the integration will fail with the following error: The prerequisite software for clearcase visual studio .net integration is not installed

Cause

The install of CCRC.NET for 2005 has not found the entry in the registry denoting the presence of Visual Studio 2005. Note: The original integration was designed for Visual Studio 2005, thus ClearCase checks for the existence of Visual Studio 2005 installed on the host.

Resolving the problem

The integration with Visual Studio 2008 was introduced in ClearCase 7.0.1. The registry key below will enable a new installation of CCRC.NET to work with Visual Studio 2008. Note: This solution contains information about modifying the system registry. Before making any modifications to the Microsoft® Registry Editor, it is strongly recommended that you make a backup of the existing registry. For more information describing how to back up the registry, refer to the Microsoft Knowledge Base article 256986. Open regedit (Start > Run type: regedit) Navigate toHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0.  Note: This key will have to be created if it does not already exist. Make a new string value InstallDir and enter c:\temp for the value: Click OK, close the registry editor and attempt to install ClearCase. Refer to download document 4017991 Integrate ClearCase, CCRC and ClearQuest 7.0.1 with Visual Studio 2008 for further instructions on how to correctly enable the integration with Visual Studio 2008.

Checkout from CCRC fails with mastership error even when unreserved, nonmastered checkout preference is selected

This technote explains why the error, ccweb: Error: Master replica of branch "\main" is "remote-site", may occur when using IBM® Rational® ClearCase® Remote Client even though the unreserved, nonmastered checkout preference is selected. Symptom In the ClearCase Remote Client (CCRC) 7.0.1, there is a feature under Preferences, Always checkout unreserved and nonmastered for replicated elements, that can be set as the default behavior. However, even with that option selected, the following errors are still being reported: Unable to checkout "C:\ccweb\NL60989\NL60989_webview\ramp\test" Problems performing checkout. ccweb: Error: Unable to perform operation "checkout" in replica "ralf2" ccweb: Error: Master replica of branch "\main" is "ming". ccweb: Error: Unable to check out "C:\ccweb\NL60989\NL60989_webview\ramp

Cause

CCRC does not recognize the VOB as being replicated, which is a requirement for the checkout request to be successful. CCRC only sends the request for a nonmastered checkout, if it believes the VOB to be replicated. To verify if a VOB is replicated, CCRC uses the entry for the VOB in the ClearCase registry, which should have (replicated) at the end of it. Note: The setting of the VOB's (replicated) attribute value was first implemented in ClearCase MultiSite version 2003.06.14. Cause 2 Another cause is due to a known defect APAR PK57433 where unreserved and nonmastered checkout falls back to unreserved, mastered checkout. This happens ONLY with Multi-level VOB tags (on UNIX® or Linux®). For example /vobs/test Only when double clicking the file in the Details Windows

Diagnosing the problem

You can check the registry on a native client using cleartool lsvob to see if the replicated attribute is set or not for the VOB that is reporting the problem. In the below example, we can see that the replicated attribute is set for the \abc-vob VOB, but is not set for the \ramp, yet both of these VOBs are actually replicated. Example: > cleartool lsvob * \ramp \\scorpio-I\data\clearcase_storage\vobs\ramp.vbs private * \abc-vob \\Scorpio-i\data\clearcase_storage\vobs\abc-vob.vbs private (replicated) In the case with the issue the entry looks like: \ramp \\scorpio-I\data\clearcase_storage\vobs\ramp.vbs private The correct entry would look like: \ramp \\scorpio-I\data\clearcase_storage\vobs\ramp.vbs private (replicated) Check the CCRC client Preferences to verify that the preference, Always checkout unreserved and nonmastered for replicated elements, is selected:

Resolving the problem

Solution for the first Cause The replicated attribute for the VOB reporting the error needs to be set in the Rational ClearCase registry. Either of the 2 options below can be performed to resolve the issue. Re-register the VOB: cleartool register -vob -replace OR Run the rgy_upgrade script to set the (replicated) attribute. Example: Windows: On a ClearCase replica server, run the following command for each replicated VOB: \bin\rgy_upgrade.exe -tag vob-tag [...] UNIX/Linux: On a ClearCase replica server, run the following command for each replicated VOB: /etc/rgy_upgrade -tag vob-tag [...] Alternate Option If there are many VOBs on the server that need to be updated, you can use the following syntax to update all VOBs on the current host rather than specifying each VOB-tag individually. UNIX/Linux: /etc/rgy_upgrade -vobs Windows: \bin\rgy_upgrade.exe -vobs For more information About rgy_upgrade, refer to technote 1207026. Solution for Cause 2 The defect has not been resolved. WORKAROUND: Use the Navigator Window (expanding directories) to browse through Directory tree. Note: If the error has already occurred, disconnect and then reconnect the CCRC client from the server to reset.

Failed to execute runnable error integrating CCRC with Eclipse

This technote explains why attempts to integrate the IBM® Rational® ClearCase® Remote Client (CCRC) with Eclipse™ versions 3.1.x or greater results in the error, Error: Failed to execute runnable (java.lang.NoClassDefFoundError: org/eclipse/ui/internal/progress/PendingUpdateAdapter), and details how to resolve the error.

Cause

Attempts to integrate CCRC with Eclipse 3.1.x or greater fails with the following error: Error: Failed to execute runnable (java.lang.NoClassDefFoundError: org/eclipse/ui/internal/progress/PendingUpdateAdapter) The version of CRCC that ships with ClearCase version 7.0 does not support Eclipse versions greater than 3.1.x. Review technote 1224586 for Eclipse plug-in compatibility and version support for CCRC. Also the Eclipse API is using org.eclipse.ui.internal.progress.PendingUpdateAdapter, which has been moved in 3.2.x to a new location, org.eclipse.ui.progress.PendingUpdateAdapter.

Resolving the problem

Update to a later ClearCase 7.0 CCRC client update for 3.2.x support; see technote 1215611 for directions on Installing or updating CCRC for Eclipse. Update the CCRC Eclipse plug-in to a minimum of client update CU01. After updating CCRC, you can update the Rational Web Platform (RWP) Server as needed.

Version tree is empty when displayed from a CCRC client

This technote identifies a defect where attempts to display a version tree from an IBM® Rational® ClearCase® Remote Client (CCRC) results in the display of only white space and provides information on how to workaround the issue. Symptom When displaying a version tree a loading screen is displayed, but when finished only white space is shown in the window.

Cause

The cause of this issue has been traced to having an instance of a branch locked. The problem occurs when attempting to display a version tree in which there is a lock on any branch instance that the version tree is attempting to display. Defect APAR PK63076 has been opened to investigate this issue. To be added to the list of clients reporting this issue, contact IBM Rational ClearCase support.

Environment

This behavior is seen after upgrading a CCRC client to the following build id: Build id: BALTIC_MR1_PATCH_CCRC_UPDATE.D080123 All previous build versions work as intended.

Diagnosing the problem

You can find the build id by displaying the Help menu option in an active ClearCase Remote Client window and selecting the About Rational ClearCase Remote Client option. Here is an example of the screen displaying the build id information for CCRC:

Resolving the problem

There is currently no resolution available for this defect. WORKAROUND: The following workarounds are available: In order for the version tree to be displayed all branches would have to be unlocked. Unlock all branches so the version tree displays. Avoid upgrading to D080123 of the CCRC client. All previous CCRC versions work as intended.

CCRC login error Unable to connect to server URL

This technote explains why the error, Unable to connect to server URL, occurs when attempting to login from a IBM® Rational® ClearCase® Remote Client. Symptom The following error is reported during an attempt to login from a CCRC client... Unable to connect to server ...where URL above is the url to which the user was logging in. You can successfully start-up CCRC 7.0.1, but cannot login to the RWP server from CCRC. The user had no problem logging into CCWeb using a Web browser.

Cause

A change in the environment was not reflected in the CCRC profile (.Rational).

Resolving the problem

Delete .Rational from your home directory and CCRC will start. By default, the profile is located in this path, C:\Documents and Settings\{USERNAME}\.Rational. Note: .Rational will be automatically recreated and updated during CCRC startup.

CCRC Windows client fails to finish a load reporting errors in CCRC trace: Unable to commit item

his technote explains why an IBM® Rational® ClearCase® Remote Client (CCRC) on Microsoft® Windows® may fail during a load and the debug trace output reports the error, ccweb: Error: Unable to commit item. Symptom When attempting a load from a CCRC Windows machine when the VOB and RWP server are hosted on a UNIX® or Linux® host, the load hangs. When a CCRC client side trace is performed, errors like these are seen for many files: Apr 14, 2008 4:50:45 PM GMT::TRACE::HTTP_CLIENT::content::log::[DEBUG] << ".ccweb: Error: INTERNAL ERROR detected and logged in "/var/adm/rational/clearcase/log/error_log".[\n]" Apr 14, 2008 4:50:45 PM GMT::TRACE::HTTP_CLIENT::content::log::[DEBUG] << "ccweb: Error: Unable to commit item "src/" "file.txt"[\n]" The error log reports errors like: ccweb: Error: Mon Apr 14 09:00:00 EDT 2008. host "vob_server", pid 762036, user "jdoe" Internal Error detected in "../ccw_ws.cxx" line 4122 Refer to technote 1234118 How to setup up debug tracing for the ClearCase Remote Client for further information about CCRC tracing. When an attempt is made to load the view through CCWeb, an error like this is generated: Error: "java.io.FileNotFoundException: C:\ccwebviews\web_view\vob\src\con.loading.1.2.3.4.5... ...6751.6752.6753 (The system cannot find the path specified)" Note: If the same load is attempted on a UNIX/Linux machine, the load finishes successfully.

Cause

A file or folder being loaded into the view has a Windows' reserved word as its name. The CCWeb error actually shows the problem file. In the example above the file is named 'con'. The load is not completing because 'con' is a reserved word on Windows, but it is not a reserved word on UNIX or Linux; hence, there is no problem on either OS. When the attempt is made to create the file or folder, the OS changes the name to something else without throwing an error, which results in the path not being found and the CCRC load hangs at that point.

Resolving the problem

To resolve this issue, the file must be renamed to an allowable name on both Windows as well as UNIX and Linux. To prevent this problem, you must avoid using names that are reserved by the operating system, especially in a mixed environment, refer to technote 1131223 for more details About naming conventions and characters used to create ClearCase objects.

Element is not checked out message when attempting to resolve hijacked files

This technote explains why the error, Element is not checkedout, might occur when using the IBM® Rational® ClearCase® Remote Client (CCRC) to checkin an element. Symptom After checking out a hijacked element in CCRC, attempts to checkin the file results in the following error: Element is not checkedout

Cause

The error is caused by a discordance issue with the CCRC view.

Resolving the problem

To resolve this issue right-click the parent directory of the element and select Restore Resource. Refer to technote 1305088 About Discordance in ClearCase Remote Client for further information.

Unable to login user: invalid session / login information supplied

This technote explains how to resolve an error that can occur in a web browser while attempting to create or reuse a view using the IBM® Rational® ClearCase® Web Interface (CCWeb) or ClearCase Remote Client (CCRC). Symptom Attempts to create a Web view results in the following error: Unable to login user: invalid session / login information supplied. Unable to login: username or password is incorrect

Cause

If the server running the Rational Web Platform (RWP) is a hosted from a Windows host this error can occur if the user account is removed from the Domain (on the domain controller) and added back to the Domain with same username. Cause 2 If the server running the Rational Web Platform (RWP) is hosted from a UNIX® or Linux® host this error can occur if The umask on UNIX (or Linux) for the user account is set to 077 rather than 002 or 005, so permissions in directory /var/adm/atria/ccweb/ are too restrictive. The umask on the root account can also cause this error if it is too restrictive, such as 027. Cause 3 If the RWP server is running on Linux, the /usr/lib/libpam.so.0.XX file needs to be linked to /lib/libpam.so.0 as shown in the example below: $ ls -al libpam* lrwxrwxrwx 1 root root 14 Jul 23 2006 libpam.so.0 -> libpam.so.0.77 -rwxr-xr-x 1 root root 32024 May 12 2006 libpam.so.0.77 lrwxrwxrwx 1 root root 19 Jul 23 2006 libpam_misc.so.0 -> libpam_misc.so.0.77 -rwxr-xr-x 1 root root 9524 May 12 2006 libpam_misc.so.0.77 lrwxrwxrwx 1 root root 15 Jul 23 2006 libpamc.so.0 -> libpamc.so.0.77 -rwxr-xr-x 1 root root 9108 May 12 2006 libpamc.so.0.77 Cause 4 There is no pam-devel package installed on the RWP server: $ rpm -q pam-devel package pam-devel is not installed $ rpm -q pam pam-0.75-62 Without this package the following links will be missing: # ls -al libpam* lrwxrwxrwx 1 root root 25 Jun 15 10:23 libpamc.so -> ../../lib/libpamc.so.0.75 lrwxrwxrwx 1 root root 29 Jun 15 10:24 libpam_misc.so -> ../../lib/libpam_misc.so.0.75 lrwxrwxrwx 1 root root 24 Jun 15 10:25 libpam.so -> ../../lib/libpam.so.0.75 Cause 5 The ccweb file should have the following permissions: -r-sr-xr-x 1 root other 579916 Jun 9 20:23 /usr/atria/web/bin/ccweb Note: /opt/rational/clearcase/web/bin/ccweb for version 2003.06.00 and later. Cause 6 The variable tmpdir is not set, or is set incorrectly in the ccweb.conf file. Cause 7 The login fails when a UNIX or Linux RWP server set up to authenticate using Samba that is configured to verify credentials from a Windows Active Directory server.

Resolving the problem

Solution 1 Note: Every CCWeb and CCRC user has their own session.dat file which contains references to their web views. The session.dat files is stored in the following directory (by default): Windows: C:\Program Files\Rational\ClearCase\var\ccweb\ UNIX & Linux: /var/adm/rational/clearcase/ccweb/ On the RWP server, navigate to the directory where the user session.dat files are stored. Rename the session.dat file and move to a temp directory. Attempt the CCWeb or CCRC operation again. Note: A new session.dat file will be created for the user. Solution 2 You can use CCWeb or CCRC through RWP with a different user account that has group access to the directory, or change the user's umask to 002 (chmod 775) and remove file /var/adm/atria/ccweb//session.dat. The root user must have a umask of 022 on the RWP server. For additional information on configuring RWP, see IBM Rational ClearCase Administration Guide > Configuring the Rational Web Platform . Solution 3 If the the /usr/lib/libpam.so.0.XX file is not linked to /lib/libpam.so.0, link them using a standard Linux symbolic link. If the file is properly linked, you will need to consult your Linux vendor for the newest version of libpam.so as the version in use may be too old to work with the CCWeb components. Solution 4 Install the pam-devel package on the RWP server. Solution 5: If the permissions are not -r-sr-xr-x, then run chmod 4555 ccweb (in the directory) If the file is not owned by root, then run chown root ccweb (in the directory) Solution 6 Manually set the tmpdir variable as noted in technote 1125332. Solution 7 This is not a supported configuration. If your RWP server is on Linux/UNIX, you will not be able to use Windows to verify credentials; you must authenticate from Linux/UNIX.

Triggers not firing when using ClearCase Remote Client (CCRC)

This technote explains why triggers might not fire when using a IBM® Rational® ClearCase® Remote Client. Symptom Setting up a trigger on CCRC with a UNIX RWP server does not work.

Cause

The server config file (rwp.conf, ccrc.conf) can be modified to add environment variables, but the SetEnv variables are not being initialized.

Diagnosing the problem

You can display the current system environment for the CCRC server using the dump option in the CCRC server URL as follows: Windows Server dump: http://host.com:port_num/ UNIX and Linux Server dump: http://host.domain.com:port_num/ccweb/bin/ccweb?cmd=dump Refer to technote 1207634 Writing triggers for the ClearCase Remote Client for further information about displaying the system environment details.

Resolving the problem

Restarting Rational Web Platform (RWP) on the Web server will initialize the variables and triggers will then fire.

Non-interactive triggers fail with warning about interactivity using CCRC or CCWeb

Problem(Abstract) This technote explains why the error Interactive triggers are not supported in the Web interface might occur when using non-interactive triggers with the IBM® Rational® ClearCase® Remote Client (CCRC) or ClearCase Web client (CCWeb). Symptom Error reported when a trigger fails while using either a CCRC or ClearCase WEB (CCWeb) client: Interactive triggers are not supported in the Web interface. If the trigger was interactive, it may have failed for that reason.

Cause

CCRC An error in the trigger script makes CCRC think the trigger is interactive. Below are 2 scenarios that will cause this error. The trigger used to generate the error below did not include the full file system path to cqperl in the script which caused the script to require input thus making the non-interactive script, interactive. An example of the full error message: ccweb: Warning: Trigger "Deliver_CQRequired" has refused to let deliver_start proceed. Interactive triggers are not supported in the Web interface. If the trigger was interactive, it may have failed for that reason. The trigger script was referencing a user defined environment variable which was set on the client but could not be found on the RWP web server. In this example the user defined environment variable MYCC_TRIGGER_TMP was set on the client to define an alternate temp directory and is referenced by the trigger script. However, it was not defined on the RWP web server. An example of the full error message: Unable to checkin "" Error: directory for environmentvariable "MYCC_TRIGGER_TMP" or "TMP" not found ccweb: Warning: Trigger "ci_pre" has refused to let checkin proceed. Interactive triggers are not supported in the Web interface. If the trigger was interactive, it may have failed for that reason. ccweb: Error: Unable to check in "". CCWeb ClearCase always displays that message when a trigger script fails or fails to execute. ClearCase can find the trigger, however, it can't find the trigger script.

Resolving the problem

HINT: Trigger scripts should be carefully tested to ensure that they are properly structured and functional for your environment. Solution 1: Update the trigger script to include the full file system path to cqperl. You must define the environment variable on the RWP web server in the ccweb.conf file and rwp.conf (or rwp_startup) scripts. Examples: In /var/adm/rational/common/rwp/conf/ccweb.conf DirectoryIndex bin/ccweb ... # This passes the LANG environment var to allow the ccweb CGI program # to correctly get the locale. PassEnv LANG PassEnv NLSPATH PassEnv MYCC_TRIGGER_TMP In /var/adm/rational/common/rwp/conf/rwp_startup or rwp.conf # Assume success to begin with # Ensure an appropriate path. On Linux, standard UNIX executables like ls and rm # are typically in /bin, whereas on Solaris, HP-UX, and AIX they are # typically in /usr/bin. We put both on the path. We also put # the system /sbin and /usr/sbin on the path. PATH=/org/st32/log2_snapshot/advantage/tooling/cm/cc_trigger:/bin:/usr/bin:/sbin:/usr/sbin:$PATH export PATH MYCC_TRIGGER_TMP=/var/tmp export MYCC_TRIGGER_TMP Refer to technote 1207634 Writing triggers for the ClearCase Remote Client for further information. Solution 2: You need to specify a path for the trigger script that can be easily located. The script isn't aware of the CCWeb view that you are using on the client system, thus scripts located inside VOBs or only on the VOB server cannot be located from the view or RWP server. The trigger is run from the view or RWP server and the path specified in the script must be one that can be located from the view server. If the view server is a UNIX® or Linux® system, then it is the -execunix phrase that fires. Review the ClearCase Command Reference Guide on the topic of mktrtype (cleartool man mktrtype) for more information.