Please read this document to learn about known product issues, important tips, and other Rational ClearQuest product information.
Release Notes, version 10.6.00
2.0 Known Defects
1.1 List of Supported Platforms and Operating Systems
1.2 Upgrading from Previous ClearQuest Releases
1.3 What's New in ClearQuest 2000 Patch 2
1.4 Defects Fixed in ClearQuest 2000 Patch 2
1.5 Oracle Database Connection Options
3.0 Troubleshooting Web Services
2.1 Installation
2.2 CQ Client
2.3 CQ Designer
2.4 CQ Web
2.5 CQ Import and Export
2.6 User Documentation
2.7 UCM Integration
3.1 Basic Troubleshooting Tips
3.2 Advanced Troubleshooting Tips
This section describes the steps to install Rational ClearQuest 2000 Patch 2. Customers may upgrade to this patch release from a variety of previous releases including ClearQuest 2000 Patch 1, ClearQuest 2000, ClearQuest 2.0 SP2, ClearQuest 2.0, ClearQuest 1.1 SP1, etc. Instructions to upgrade to this patch version from any of the previously mentioned releases are described in detail in this section.
If you are currently using Rational ClearQuest 2000 and need to generate report formats using Crystal Reports, please refer to section 1.2.1. If you are using Rational ClearQuest 2000 or ClearQuest 2000 Patch 1 and either already upgraded to Crystal Reports 8 or do not need to generate report formats, please refer to section 1.2.2. Please also refer to section 1.2.3 for additional details on the upgrade process.
If you are using Rational ClearQuest 2.0 or ClearQuest 2.0 Patch 1 or ClearQuest 2.0 Patch 2, please refer to section 1.2.4. If you are using a ClearQuest version prior to ClearQuest 2.0, please refer to section 1.2.5.
1.2.1 Upgrading from Rational ClearQuest 2000 and upgrading from Crystal Reports 6 to Crystal Reports 8
In order to create new report formats in ClearQuest 2000 Patch 1 or Patch 2, Crystal Reports 8 is required. You cannot create new reports in ClearQuest 2000 Patch 1 or Patch 2 using Crystal Reports 6 (see defect 12965 in section 2.2). In this scenario, you will be required to upgrade both Crystal Reports and Rational ClearQuest. To upgrade in this scenario, follow these steps:
Please refer to section 1.2.3 for more information on the upgrade process.
1.2.2 Upgrading from Rational ClearQuest 2000 or ClearQuest 2000 Patch 1
To upgrade, follow these steps:
Please refer to section 1.2.3 for more information on the upgrade process.
1.2.3 Customers upgrading from Rational ClearQuest 2000 or ClearQuest 2000 Patch 1 to ClearQuest 2000 Patch 2 should be aware of the following:
1.2.4 Upgrading from Rational ClearQuest 2.0
If you have installed Rational Suite 1.5 or ClearQuest 2.0, you may install ClearQuest 2000 Patch 2 over the previous installation. To upgrade, follow the steps:
Customers upgrading from ClearQuest 2.0 to ClearQuest 2000 (or ClearQuest 2000 Patch 2) should note the following:
1.2.5 Upgrading from Rational ClearQuest 1.0, 1.1, or 1.1 SP1
Customers upgrading from ClearQuest 1.0, 1.1, or 1.1 Service Pack 1 should refer to the documentation in Chapter 7 of the manual, Installing Rational ClearQuest. Please be especially aware of the following:
If you do not apply the needed upgrade packages after upgrading the ClearQuest software and databases, the existing functionality (notification mail, integration with your source code management system, etc.) will be inoperative.
NOTE: Be careful when selecting the packages to install. Some packages (such as Email and Visual SourceSafe) have a version for first-time installations (for example, version '1.0') and a version for upgrades (for example, version 'Upgrade 1.0'). Be sure to select the correct version. As a general rule of thumb, when installing upgrade packages, if there is more than one version, always apply the highest-numbered version. Record types, fields, and actions that were added by the add-ins are modified by the packages. The package takes "ownership" of these entities (record types, fields, and actions) so that in some cases they become read only in the ClearQuest Designer.
Introduction
ClearQuest 2000 Patch 2 provides an update to ClearQuest 2000 and ClearQuest Patch 1, offering a variety of fixes in a number of areas that may be critical to deploying ClearQuest in certain configurations. These include:
ClearQuest Web and Perl Scripting
Prior to Rational ClearQuest 2000 Patch 2, ClearQuest Web could not be used if hooks were authored using Perl. This was due to improper support for multiple threads in CPAN's Perl (v 5.00502). As a consequence, ClearQuest Web server hung when multiple users accessed ClearQuest via the Web interface. This problem made the Web interface unusable if hooks were authored in Perl. In addition to the instability of the Web server, there were many memory leaks and corruption problems such as the $entity variable pointing to the wrong entity when Perl hooks were nested, etc.
ClearQuest 2000 Patch 2 addressed the above issues by using Active State's Perl (v 5.6, build 616) which has support for multiple threads and multiple Perl engines. As a consequence, customers can now author hooks in Perl and successfully deploy ClearQuest Web. A Perl engine is created when an action is performed and destroyed upon the completion of the action. New actions started within a hook will also create a new Perl engine. This ensures that memory is efficiently managed and built-in $entity object is set correctly.
ClearQuest Web has been tested extensively with the new version of Perl. In order to ensure web stability under high loads, Rational is performing load testing involving 50 simultaneous users performing normal operations (e.g., submit, modify, query) which is equivalent to a typical user community of approximately 300 users per web server. Based on this load testing, Rational recommends the following configurations for best performance and stability under high loads:
IIS performance tuning: In order to ensure top performance from ClearQuest Web in a multi-user environment, please be sure the following IIS tuning is completed:
Note: Rational ClearQuest was load tested using Rational Performance Studio. Rational recommends at least 1 GB of RAM and a Pentium II processor (500 MHz and greater) on the Web server for optimal performance.
Other Issues
The following lists a number of other defects that have been addressed in ClearQuest 2000 Patch 2. See section 1.4 for a more complete list.
Oracle Connection Options
The connect_options database property has been expanded to support Oracle 8 clients. This option is a site-wide setting per database. The ClearQuest user sees these options as a string in the Connect Options field in the ClearQuest Maintenance tool when attempting to connect to an Oracle database. The permissible values are:
host=<host>;sid=<sid>;server_ver=<ver>;client_ver=<ver>;lob_type=LONG
where,
<host> is the network hostname of the Oracle database server;
<sid> is the instance ID of the Oracle database server;
<ver> is the Oracle version number, either, 7, 8.0 or 8.1;
server_ver is the Oracle database server version number;
client_ver is the Oracle client version number;
lob_type is the Oracle data type used for text fields; currently, this
must be of type LONG.
You can override each, or all, of the connect options values per machine by using installutil registeroracleoptions command-line utility. This will not change the setting in the master database, only the way a specified client will connect to the database. A sample registry entry looks like:
[HKEY_CURRENT_USER\Software\Rational Software\ClearQuest\2000.02.10\Core] "OverrideOracleConnectOptions"="client_ver=8.0"
For Unix, the client-based connect override can be achieved by setting the environment
variable:
CQ_OVERRIDE_ORACLE_CONNECT_OPTIONS
The Oracle client connect options are also described in the guide, Installing ClearQuest. Please refer to the section, "Creating ClearQuest Databases." Also note that, while not all the Oracle connect values are required, it's a good practice to set all the values to avoid any undesirable default behavior.
What Does This Mean to the ClearQuest User?
Oracle 7 and 8x Servers; Oracle 7 Clients:
This is the supported configuration prior to ClearQuest 2000 Patch 1 and customers don't have to set any Oracle connect options in order to continue using this Oracle client/server configuration.
Oracle 7 and 8x Servers; Oracle 8 and 8i Clients:
Customers should use the appropriate Oracle connect options for their configuration. For example, if they can connect to an Oracle 8.0.5 server via an Oracle 8i client, they should use:
Oracle 7 and 8x Servers; Oracle 7, 8, and 8i Clients:
This configuration will require setting the Oracle connect options for the site, as well as on machines that deviate from the site setting. If most of the ClearQuest clients are using Oracle 8.0.5 client, they should set connect options with client_ver=8.0 in the master database. Then, for the ClearQuest client machines that have Oracle 7 or Oracle 8i clients, those users will need to use the installutil registeroracleoptions command-line utility in order to override the 8.0-client master DB setting.
Setting Connect Options for New Databases:
You should set the appropriate connect options using the guidelines above.
Setting Connect Options for Existing Databases:
To set the connect options for an existing schema repository (i.e. not newly- created with the ClearQuest Maintenance tool), use the installutil registeroracleoptions command-line utility to set the connect options for existing user databases. After that, use ClearQuest Designer and execute the "Database Property" dialog and enter the connect options there. Make sure to answer "NO" when it asks whether you want to physically move the database. Another way is to run the installutil relocateuserdb command-line utility.
An Example: The server is an Oracle 8i instance; and there are existing ClearQuest 2000 Patch 1 clients with Oracle 7 client software; as well as new ClearQuest 2000 Patch 2 clients with Oracle 8i client software.
There are two methods to set up this site:
Method 1: Set the client 8 option per ClearQuest client machine.Please note that, if your existing ClearQuest client machine is still using a non-patched 2000.02.10 version of ClearQuest, the only option is to use method 1 above (See also defect 12405 in section 2.1).
NOTE: All defect numbers listed here are "RAMBU" database defect numbers.
| Defect ID | Description |
| 5607 | Minimal
client install looks for an .ini file in the target install directory.
During a minimal client installation, if cqprofile.ini exists in the source directory, it is not copied to the client's local destination directory. The workaround is to copy the cqprofile.ini file manually to the local destination directory. |
| 6533 | Unable
to do defect association with SQL Server that is configured for case sensitivity.
When installing SQL server, make sure you set the dictionary sort order to case insensitive. Otherwise, VSS integration will work, but you will get a "cqvssmgr:Error:GetVSSEntityByItem" error. If the admin installs SQL Server with the wrong sort order, the user databases will have to be removed before any reinstallations of ClearQuest with a different sort order. |
| 8097 | Schema
list is missing with minimal/evaluation install.
The set of out-of-the box schemas are not available in the pull-down list box for Schema Setup after installing a minimal evaluation configuration of ClearQuest. By copying the sample_dbs directory from the network directory to the local drive, the schema list can be populated by ClearQuest Maintenance Tool and you'll be able to create a sample db. |
| 9963 | Cannot
build a SQL/Anywhere schema repo for ClearQuest on Win2000.
When creating a SQL Anywhere schema repository for ClearQuest, an error dialog will appear. Currently, creation of SQL/Anywhere schema repos on the Windows 2000 isn't supported. A patch provided by Sybase, SQL Anywhere patch 5.5.05ebf build 2734, is recommended. |
| 10675 | SQL
Anywhere setup clarified.
Sybase SQL/Anywhere has limitations with respect to its ability to smoothly cross IP subnet and Windows/NT domain boundaries. To successfully create and use SQL/Anywhere databases, if any of the relevant machines (the one on which the database server is running, the web server, or your client workstation) are in separate IP subnets or Windows/NT domains you should be aware of certain precautions and limitations. These are spelled out at length in Rational Technical Support TechNote 10773. To summarize the information in the TechNote:
|
| 11079 | ClearQuest
release notes cannot be accessed from the RS Release Notes link on a minimal
install.
After doing a minimal install of Rational Suite Enterprise, if you launch the Readme for all products, and click on the ClearQuest release notes link, it points to the network location from where the install took place. However, the Readme file is installed onto the local machine. Look inside the ClearQuest directory under the installation directory and look for the readme.htm file. |
| 11989 | Connection error when upgrading from 1.1 Oracle 8 DB to ClearQuest 2000 Patch 1 with an Oracle 8 client.
If you use a machine, which has the Oracle 8 client installed on it, to perform a ClearQuest upgrade, the ClearQuest Maintenance Tool ignores the client_ver option and you will get a connection rejected error. Workaround: use either the installutil registeroracleoptions command or use an Oracle 7 client machine. |
| 12405 | Oracle 8 client version setting doesn't work with previous ClearQuest releases.
If the connect option, client_ver (set either to 8.0 or 8.1), is set for any of the databases, ClearQuest2000
and earlier releases will not be able to run. Workaround: set the registry: Please note that this doesn't address the problem where the server_ver connect option is set (to 8.0 or 8.1). Also, this registry setting is only enforced in ClearQuest 2000 Suites (not patched) releases and up. For further details and examples, see section 1.5. |
| 12470 | Should save Oracle Connect options in profile file.
The Oracle database connection options, client_ver, server_ver, host, and SID are not saved in the profile file. There isn't a workaround at this time. |
| Defect ID | Description |
| 5924 | Multi-line
fields losing last line via OLE.
In multi-line text fields, like Description, sometimes the last line of text gets dropped off of field values before it's stored in the database. |
| 6421 | ClearQuest
crashes when changing styles for an empty report.
If you run a chart that does not return any data, then open the property box, and select either the "Display Type" or "Style" tab, ClearQuest will crash. |
| 7344 | Run
report, click Export icon gives GPF.
This appears on Windows 95 with no service packs. After starting ClearQuest, run a report, then click on the Export button from the toolbar and an error dialog will appear. The error does not occur on other platforms. |
| 7421 | Crash
occurs while changing Form fonts in ClearQuest client.
An access violation error message will appear. The workaround is to use the default Windows font in ClearQuest client forms. |
| 7780 | Query
on Groups causes crash when no default is given for filter item.
The access violation will follow when you click Run. It appears that a lack of a default value causes the violation here. A suitable workaround is to provide a value for the query to run with. |
| 10899 | Database
timeout ignored on Windows 95/98.
There was a problem with the database timeouts on the Windows 95 and 98 platforms, so database timeouts on these platforms have been disabled in the 2000 Patch 1 Final release. |
| 11895 | CR8 can't author reports with Attachments and History fields.
Crystal Reports 8 users: The ClearQuest Client user cannot create a new report format if either the Attachments or History fields have been selected to be displayed as a part of the report. After such a query has been created in the Client, the Author Reports button does not function. |
| 12965 | ClearQuest 2000 Patch 2 support for CR6 limited.
Crystal Reports 6 users: The ClearQuest 2000 Patch 2 Client user cannot create a new report format with Crystal Reports 6. However, formats generated in ClearQuest 2000 installations with Crystal Reports 6 can be utilized to create new reports. Also recommended is an upgrade to Crystal Reports 8. |
| 13298 | ClearQuest 2000 Patch 1 integrations broken.
The following integrations with ClearQuest 2000 Patch 1 were broken: VSS; Rational Administrator; Robot; Team Test; CC; UCM; and, RequisitePro. Download the file found in the "K2.1.1" folder in the ClearQuestPatches ftp site. In that K2.1.1 ftp folder, find and read the accompanying K2.1.1 Readme file on how to utilize the downloaded file. |
| Defect ID | Description |
| 4517 | Option buttons will exhibit unexpected runtime behavior if the option button value attribute is not set during form authoring. |
| 5745 | After
importing a form you lose the form data if you don't modify the form.
If you just import a form into the Designer, close the form window, and then re-open it, the form will be empty. The work- around is to modify the form after importing it. |
| 7436 | Perl Scripting support should allow global variables.
There are variables local to a routine and variables available to an entire Perl script. However, the Perl editor only allows variables to be declared within a routine and not outside. Use session vars name-value pairs as a workaround. |
| 10887 | Crash
when exiting ClearQuest on Windows 95/98 after adding Perl hook.
On the windows 95 and 98 platforms, when you've created a new record type in Designer without creating a default form, and you've launched the Client, followed by the selection of the "New Defect" command, you may see an error dialog after exiting the client. |
| 10852, 11934 | Error message appears when a UCM-enabled schema is applied without a UCM install.
The error message happens only when a UCM-enabled schema is used, but UCM has not been installed. The message appears in the terminal window where the ClearQuest was started, each time a form is displayed that needs to show the UCM information. Due to this error, the area in the form is simply blank. However, the error has no other effect and can be ignored. |
| 11994 | Client GUI controls have max character value of 50; if exceeded app crash may occur.
There is a real limit of 50 for various GUI items, such as tab names and labels, but the Designer does not enforce this limit. If the limit is exceeded, the Windows client may crash. |
| 12240 | Hooks dependent upon "::new" API may experience a run-time error.
A "bus error" or Client application crash may appear when Perl hooks fire which are looking for "::new" PAI methods, CQEmailRules::new and CQWorkSpace::new. The workaround is to replace "::new" with "::Build". |
| Defect ID | Description |
| NA | User edits are not allowed during DUPLICATE and UN- DUPLICATE type actions. There is no workaround for this. |
| 5919 | Controls
for the second tab using the same name of a prior tab do not appear on
the form.
Using Internet Explorer version 4.72.3110.8 as the ClearQuest Web browser and,
if a form has two tabs with the same name, the 2nd tab with the same name
doesn't show the field controls - just the title bar. An error dialog will
appear saying, "Error getting form items".
Netscape Navigator v4.05 displays similar symptoms, except that when you go to Single Tab Display in view mode, when you click on the link to go to the 2nd same name tab, you'll get a blank screen. Here, the workaround is to log off and log back on, and you'll see the first tab. |
| 8244 | Resizing
and reloading after setting a presentation while Web Setting dialog is
open crashes ClearQuest Web.
This problem appears when using ClearQuestWeb using a Netscape browser. If you load a presentation set or use the Apply button in the Web Settings dialog in Netscape and then resize the window, Netscape suggests that you use the reload button to refresh the page. This leads to a state that will cause you to restart Netscape. The work- around is to click the web-settings menu item to refresh rather than the reload button. IE does not have this problem. |
| 9137 | Identifying the anonymous IIS user when "Run in Separate Memory Space"
is used
Chapter 6 of Installing Rational ClearQuest describes setting up ClearQuest/Web. One detail it does not mention is that the identity of the anonymous NT userid which effectively "runs" the ClearQuest/Web application varies depending on whether the "Run in Separate Memory Space" option is chosen on the IIS configuration dialogs. For details, see Rational Technical Support Technotes 8597 (setting up/troubleshooting ClearQuest/Web) and 7975 (setting up email notification). |
| 10819 | On
IIS5, no dbwin32 log when the anonymous user is not a local admin.
When using IIS5 (a component of Windows/2000), if you need to run the debugging utility 'dbwin32' you must make the anonymous IIS user a member of the local machine's "Administrators" group. If you do not, no output will be logged to the dbwin32 window due to tighter security restrictions in Windows/2000. |
| 10982 | Using
Back button will crash the browser.
Using Netscape Communicator 4.7 on a UNIX platform, using the Back button while viewing a defect record can sometimes cause the browser to hang or crash. |
| Defect ID | Description |
| 5988 | Two
versions of cqimport running on the same machine causes one to crash.
While running two cqimport processes on just one machine, the first process may crash after the second cqimport process is started. |
| 10912 | Using CQEXPORT on a schema with no default record type gets runtime
error '91'
Workaround: Define a default record type in your schema. |
| Defect ID | Description |
| 8695 | Unified
Change Management (UCM) not documented in the Introducing Rational ClearQuest
guide.
The information on available schemas in the Introducing Rational ClearQuest guide is incomplete; it does not mention the UnifiedChangeManagement schema. For information on that schema and using UCM with ClearQuest see, "Appendix A, ClearQuest schemas and packages," and "Appendix B, Enabling ClearQuest for Unified Change Management," in the Administering Rational ClearQuest guide. |
| 10961 | Packages
replace the add-ins used in previous versions of ClearQuest. If you are
upgrading from a previous version of ClearQuest and your schemas use add-ins,
install the upgrade version of the package(s). Upgrade packages contain
the word "upgrade" in their version string. To install an upgrade version
of a package, your schema must contain metadata for the upgrade package
to modify. For example, installing a package that modifies the Email_Rule
record type will succeed only with a schema that already includes the Email_Rule
record type.
See section 1.2 of this readme file for additional information. |
| 12487 | ClearQuest 2000 Patch 2
Installation guide needs further details on setting up Oracle 8i Context/interMedia text server.
(Errata to Chapter 2, the two sections for enhancing search capabilities for Oracle 7.X and Oracle 8.0.x, as well as Oracle 8.1.x.) In addition to Step 1 shown in the Install Guide, perform the Post-Installation Setup procedures seen in the guide, Oracle InterMedia Text 8.1.5 Technical Overview. You can find this at: http://www.oracle.com/support/Step 2 as shown in the Install Guide is incorrect. You should run the following command: ctxsrv -user ctxsys/ctxsys -personality M -logfile $ORACLE_HOME/ctx/log/ctxsrv.log where ctxsys/ctxsys is the default username/password. You may have to create that ctx/log directory. You'll also want to run this in the background. Oracle doesn't provide anything to start this automatically, say at boot time, so you'll either have to run these processes manually or develop a shell script for that purpose. Step 3 as shown in the Install Guide, for the section entitled, "For Oracle 7.X and Oracle 8.0.X", is incorrect. You should, instead, use the following steps: The Oracle user must have these priviledges: CTXAPP role, select on ctxsys.ctx_servers, execute on ctxsys.ctx_ddl The SQL script, setup_cq_ora_user.sql, can be used to grant the necessary priviledges. setup_cq_ora_user.sql can be found in the ClearQuest installation directory, \\Rational Software\ClearQuest\. This script must be run with Oracle's SQL interface, sqlplus, program as the Oracle ctxsys user, via: sqlplus ctxsys/ctxsys@<tnsname> @setup_cq_ora_user.sql <cq_user> where, <cq_user> is the Oracle user name assigned to ClearQuest dbo. Note: Oracle's SQL interface can be "plus33" or "plus80" and is also accessible via the Windows start menu. Step 3 as shown in the Install Guide, for the section entitled, "For Oracle 8.1.X", is incorrect. You should, instead, use the following steps: The Oracle user must have these priviledges: CTXAPP role, select on ctxsys.ctx_servers, execute on ctxsys.ctx_ddl The SQL script, setup_cq_ora_user.sql, can be used to grant the necessary priviledges. setup_cq_ora_user.sql can be found in the ClearQuest installation directory, \\Rational Software\ClearQuest\. This script must be run with Oracle's SQL interface, sqlplus, program as the Oracle ctxsys user, via: sqlplus ctxsys/ctxsys@<tnsname> @setup_cq_ora_user.sql <cq_user> where, <cq_user> is the Oracle user name assigned to CQ dbo. Note: Oracle's SQL interface can be "plus33" or "plus80" and is also accessible via the Windows start menu. |
| Defect
ID |
Description |
| 8669 | With
UCM integration, file check in only works with Access database.
If you are using the UCM/ClearQuest integration with a ClearQuest database other than Microsoft Access, you will see the following problem:
|
| 8670 | Unclear
Error message after trying to select Activity without UCM info.
After running a ClearQuest query on activity items (like defects) defined via the UCM integration, and then selecting an activity which lacks project info from check-in/-out, a misleading error dialog may appear like, "IDispath error ... ACException occurred", after selecting a member of the query. When this error dialog appears, close the dialog then fill out the UCM Project field and a more useful info box will appear. |
| 8678 | RunTime
Error after trying to delete Activity with non-empty change set.
If, in the UCM tab, the Change Set field is not empty and the user tries to delete an activity, a run-time error will appear. Close this error dialog, then a more useful ClearQuest dialog box will appear. |
| NA | In
order to use Rational ClearQuest 2000 Patch 1 with the UCM/ClearQuest Integration
in ClearCase 4.0, you must do the following:
|
Failed condition: disposition == (0x00000001L) Location: ClearQuest Core:adregistry.cpp:569occurred in BBOLEI~1See the printed document, Installing Rational ClearQuest, to set the proper permissions.
Logon Error 80020009 Could not create directory occurred in ClearQuest.FileCache.1See the printed document, Installing Rational ClearQuest, to set the proper permissions.
Logon Error Unable to logon to the MS_ACCESS database "\\This indicates a permissions problem regarding an Access Database. Try the following steps:\ \ .mdb". The vendor error message was: SQLConnect: RETCODE=-1, State=S1000, Native Error=-1032 [Microsoft][ODBC Microsoft Access 97 Driver]The Microsoft Jet database engine cannot open the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view its data.
error 'ASP 0113' Script timed out
The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.Script.Timeout or by changing the value for ScriptTimeout in the Registry. error '800a041d'By default Active Server Pages Scripts (which are the providers of the ClearQuest Web pages) are given 90 seconds to complete. If they do not complete in 90 seconds the IIS Server terminates them and presents the user with an error message similar to the above. You may increase the value from the default 90 seconds by editing the following registry key value with regedit.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ W3SVC\ASP\Parameters\ScriptTimeout
HKEY_USERS\.DEFAULT\Software\Rational Software\ClearQuest\2000.02.10\Core HKEY_USERS\.DEFAULT\Software\Rational Software\ClearQuest\2000.02.10\Install
If you have used cqdbsetup to change the schema repository characteristics, it might change the values under these keys in HKEY_CURRENT_USER, and HKEY_LOCAL_MACHINE but these settings will be overridden because the web server uses keys from HKEY_USERS\.DEFAULT instead of HKEY_CURRENT_USER. To make it see the right values, delete the values as described above; then, the ones from HKEY_LOCAL_MACHINE will be used.
http://www.rational.com/support/usergroups/
Your e-mail address will not be given out to anyone.
http://clearquest.rational.com/cqhooks
To gain access enter:
username: userYou can browse the existing hook scripts for ideas, or add a script you would like to share with others.
password: password
Rational's web site contains an extensive library of Technical Notes. To access the Technical Notes, go to http://solutions.rational.com/solutions/.
Rational maintains Support Centers in different geographic regions.
To contact the center nearest you, consult the chart below. If you are
contacting Technical Support by phone, dial the phone number shown below
and follow the voice prompts to select ClearQuest Technical Support.
| Support Location |
Telephone
|
Electronic
Mail
|
|
North America
|
(800) 433-5444
(408) 863-4000
|
|
|
Europe
|
PHONE:+31 20 454-6200
+31
20 454-6201
|
|
| Asia Pacific |
+61-2-9419-0111
|
(c) 2000 Rational Software Corporation and its subsidiaries. All rights reserved. Rational Software Corporation and its subsidiaries ("Rational") claim copyright in this Program and documentation as an unpublished work, versions of which were first licensed on the date indicated in the foregoing notice. Claim of copyright does not imply waiver of Rational's other rights. See Notice of Proprietary Rights.