IBM Support

Failed condition error with m_pPerl, when creating a new record in ClearQuest

Troubleshooting


Problem

This technote explains how to resolve an error, "Failed condition:m_pPerl != 0". This can occur when creating a new record in IBM® Rational® ClearQuest®.

Symptom


When creating a new record, such as a new TestPlan, an error similar to this might occur:

Execution of a hook failed during the action Import. It was the ACTION_INITIALIZATION hook attached to the Defect "SAMPL00000001". The reason for the failure was:
Failed condition: m_pPerl != 0
Location: ClearQuest Core:adperlhooks.cpp:237


In ClearQuest 7.1, this error might also occur:

Creating Perl interpreter failed. Please run command "cqperl -V" to validate cqperl installation.


In addition to these symptoms, the New Record drop down does not display all available record types if there are Submit actions controlled by Perl hooks.

Cause


This issue can occur if there are conflicts with the following environment variables:

  • Perl and the PERL5LIB Environment Variable. This is common if there is Oracle software recently installed on the computer.
  • Java and the PATH environment variable.

Other reported causes
  1. This error has also been known to occur from a corrupt or incomplete install of the Perl libraries supplied with ClearQuest. In this instance, neither Oracle, nor any additional Perl libraries where present on the system. Reinstalling ClearQuest after an uninstall resolved the problem.
  2. If on UNIX or Linux, ClearQuest might not have access to the Perl libraries, JRE, or associated files.
  3. This error can also be caused by a broken network file system mount to the network install area.

Resolving The Problem



Resolving the Perl environment variable

If the PERL5LIB variable has any values that are set by installing other applications, try setting the value for PERL5LIB to the Perl libraries installed by ClearQuest. You can also move the ClearQuest-based Perl location to the beginning of the PERL5LIB variable. These paths are based on the default installation directories:

ClearQuest 7.0.x

Windows: C:\Program Files\Rational\Common\lib\perl5\5.8.6
Linux and UNIX: /opt/rational/common/lib/perl5/5.8.6

ClearQuest 7.1.x



Windows: C:\Program Files\IBM\RationalSDLC\common\lib\perl5\5.8.6
Linux and UNIX: /opt/IBM/RationalSDLC/common/lib/perl5/5.8.6


It is also possible that the Environment Variable PATH contains a version of Perl that creates a conflict with the ClearQuest Perl modules v5.8.6 that it requires. Check for other Perl libraries in the Path and temporarily remove them to see if there are any changes in behavior.


Resolving the Java environment variable

Make sure that the PATH variable contains the value for the ClearQuest JRE location. If it is there already, move the ClearQuest-based JRE location to the beginning of the environment variable. These paths are based on the default installation directories:

ClearQuest 7.0.x

Windows: C:\Program Files\Rational\Common\java\jre\bin
Linux and UNIX: /opt/rational/common/java/jre/bin


ClearQuest 7.1.x

Windows: C:\Program Files\IBM\RationalSDLC\common\JAVA5.0\jre\bin
Linux and UNIX: /opt/IBM/RationalSDLC/common/java/jre/bin


Notes:
  • You can find the environment variables for Microsoft® Windows® in the Control Panel. Select the System folder. In the Advanced Tab, click on Environment Variables.
  • Changing environment variables might require a reboot of the machine in order for the changes to take effect.
  • On Windows, you will have to place this information in the System environment variable path if experiencing this problem in ClearQuest Web, with the web services ran as a Local System account.


Assure that ClearQuest Web on UNIX or Linux has access to the Perl and JRE libraries
  1. Change the user that runs the ClearQuest Web server or ClearQuest client processes.
  2. Assure the proper permissions to the processes and paths. This includes permission to access the release area. For example, add the user to the group that owns the library paths and release area.
  3. Do not assume the user can traverse as the "other" group. Test the path by doing a "cd" at each step of the path into each sub-directory until you get a permission denied error as the user.
  4. Consider a "Full Copy" installation instead of "Standard Install" so that no symbolic links are involved with varying permissions.

[{"Product":{"code":"SSSH5A","label":"Rational ClearQuest"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Client - Eclipse RCP","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.0;7.0.1;7.1;7.1.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 June 2018

UID

swg21246579