Eric J. Ostrander's
ClearCase / ClearQuest pages.
ClearQuest Errors
Simple, case-insensitive search:

NOTE: For brevity, the following are used: ct=cleartool, CC=ClearCase, mt=multitool, CCMS=ClearCase MultiSite, DDTS=ClearDDTS, CQ=ClearQuest, CQMS=ClearQuest MultiSite, mu=multiutil, MS=Microsoft, and UCM=Unified Change Management. On most NT systems cq-home is C:\Program Files\Rational\ClearQuest.
Failed to check out a ClearQuest_TeamTest license key: FLEXlm Error -2, Invalid license file syntax OR no licenses in file
This error occurred immediately after initial install. This install was going to be a stand-alone server. Even though this was to be a server, the "client side" of the install needs to know where to find a license.
In CQ 2003.06.00+, in the Rational License Key a Administrator, go to Settings-> Client/Server Configuration. Click the box that says "Add Server". In right-hand pane, fill in the license Server Name in the Values column.
In CQ 2001+, in the Rational License Key Administrator, go to Settings->Service Configuration and check the box "Use License Server. In CQ 2000A-, in the Rational License Key Administrator go to the Settings tab and select Client at the bottom of the page. For both, select "Use single server" and type in the name of the license server. Restart the license server: Start -> Settings -> Control Panel -> FLEXlm License Manager -> Control tab, Stop & Start. If the Stop reports that "Server stop failed", it was probably never started in the first place.

Back to the INDEX.
Failed to check out a key. FLEXlm Error -15, Cannot connect to license server
For some reason, the FLEXlm license manager failed to start after a reboot. Simply go to Start -> Settings -> Control Panel -> FLEXlm License Manager -> Control and Start the License Server.

Back to the INDEX.
ERROR! Execution of a hook failed during the action Action.
Can't locate auto/CQEntity/GetFieldval.in @INC
The hook is attempting call a function called "GetFieldvalue" which doesn't exist. Check the hook code and change it to GetFieldValue, with a capital V.

Back to the INDEX.
Line Number <integer> : Unrecoverable Error: All values need to be quoted. e.g. "BLA BLA BLA"
This error occurred when importing date into CQ using the Rational ClearQuest Import Tool. It's telling you that the quotes surrounding the import field data in the import file are out of order. Ensure that all field values are surrounded by double quotes. Also ensure that there are no field values that have quotes inside them, such as might be found in multi-line text fields. Simply correct the problem and rerun the import.

Back to the INDEX.
Unable to create SQL Anywhere database service.
This error occurred on an NT while attempting to create an SQL database service via the Rational Administrator. At the point where you type in the Account, make sure you have selected Other Account and that the login name is in the syntax of domain\sql-login. If this SQL server is not on a domain and the sql-login is a local account, simply replace the domain name with the local server name.

Back to the INDEX.
Could not start the Flexlm license manager service on \\hostname.
Error 0002: The system cannot find the file specified.
This error occurred immediately after installing Flexlm on NT and attempting to start the service. The permanent license keys were already successfully imported. In the FLEXlm control panel, under the Setup tab, ensure that the License File entry only has the path to rational_server_perm.dat. If rational_server_temp.dat is listed, remove it.

Back to the INDEX.
FLElm error: -15,10. System Error: 10061 "WinSock: Connection refused"
machine: Cannot connect to license server -15,10:10061 (Winsock: Connection refused)
The first error appeared during the attempted import. It was accompanied by the statement "Bad License" in the Rational License Key Administrator and by "Invalid license key" in the FLEXlm control panel.
The second occured after a successful import of new TLA licenses when checking the Status in the FLexLM Control Panel.
The error was circumvented by manually adding the license information instead of simply invoking the .upd file. Start the Rational License Key Administrator. Enter the information in License -> Enter a License. Restart the FlexLM daemon when prompted.

Back to the INDEX.
!%$ Failed to insert package queries and report formats into user database
AdMetadataMgr: The Project AdEntityDef cannot be gotten because it does not exist
Location ClearQuest Core:admetadatamgr.cpp: 1069
08/05/00, CQ 2000
This error occurred when attempting to upgrade a CQ database. However, it only appeared when one manually did an upgrade or attempted to create a new database and not during "Test Work", which does an upgrade as well.
This is a non-fatal error simply warning you that some data is missing in your schema. The datbase gets upgraded anyway. Inspect your schema for any oddities or create a new database that is associated with a previous version of the schema.

Back to the INDEX.
Can't get server: Cannot find license file -1,359:2 (No such file or directory)
08/05/00, CQ 2000
This error indicates that the license file on the license server is actually missing. A reenter of the license information via the Rational License Key Administrator solved the issue.

Back to the INDEX.
An error occurred associating the request CQ-record-id
AdEntity: The "cc_change_set" AdField cannot be gotten because it does not exist.
Location: ClearQuest Core:adentity.cpp:575
08/05/00, CQ 2.0 P2, NT 4.0 SP6a, CC P9,10
These errors occurred when attempting a checkout in a VOB with a non-UCM integration to CQ. The CQ schema must have the ClearCase package added to it. Also be sure to add any ClearCase package updates, such as "Upgrade 1.0". If you've already added the CC package to the schema, is it checked in? Have the associated databases been upgraded with the latest schema changes?x

Back to the INDEX.
ERROR! AdActionDef: The AdActionUserDef cannot be unbuilt becasue it does not exist. Location: ClearQuest Core:adactiondef.cpp:835
CQ 2000 patch 2
This error occurred when moving an action's Access Control from one group to another. More specifically, if one creates a group such as "test2" and then a group called "test", if in the schema's Actions matrix you set Access Control for an action to User Groups and then choose "test", CQ will set it to "test2" anyway. That is, "test2" appeared first in the groups list and CQ chose the first group that contained the string "test". So, when you attempt to move the check from the "test2" box to the "test" box (to set it the way you intended), it will generate the error message. This appears to be a bug and has been reported to Rational.

Back to the INDEX.
Failed to checkout a key for ClearQuest: FLEXlm Error -18, License server does not support this feature
CQ 2000 patch 2. This error occured after rearranging licenses and installing new TLA floating licenses. It was simply pointing to the incorrect license file. That is, even the import of the new licenses went ok and showed up in green in the Rational License Key Administrator, the FLEXlm Control Panel was still pointing to the _temp.dat license file. In the FLEXlm Control Panel, go to the Licenses tab and ensure the correct one is listed. Use the Show License file button to verify.

Back to the INDEX.
Invalid login name "logon" specified or user "logon" is not subscribed to any database
Unable to logon to the MS_ACCESS database "\\path\mdb".
These errors occur when attempting to connect to login to CQ when there is no network connection, or a Microsoft Loopback Adapter LAN connection is not employed on Win2k. On NT 4 it wasn't nesessary to be connected to a network or have a loopback apapter in place.
The first error occured using Flexlm 6.1. It prompts for a logon, but then errors out stating that the logon was invalid. Inspection of the Details box reveals the second "real" error about not being able to connect to the database properly.
In either case, simply connecting the computer to a LAN solves the problem. If unable to connect to a LAN with the Win2k CQ server, a loopback adapter will have to be created:
Start -> Settings -> Control Panel -> Add/Remove Hardware Next>
Add/Troubleshoot a device; Next>
Add a new device; Next>
No, I want to select the hardware from a list; Next>
Network adapters; Next>
Manufacturers: Microsoft; Network Adapter: Microsoft Loopback Adapter; Next>
Next>
Finish
The TCP/IP Propertied of the Loopback Adapter do not have to be configured in any way.
Now, when offline, "dialup" the Microsoft Loopback Adapter network connection before accessing CQ.

Back to the INDEX.
Failed to checkout a key for ClearQuest: FLEXlm Error -42, Invalid parameter
This error occurred when attempting to start CQ for the first time after installing it on a new server using FLEXlm 7.0f and CQ2001 on Win2k.
If you are sure the imported licenses are valid, open the Rational License Key Administrator and go to Settings -> Servie Configuration. Ensure the License Key Source in the middle of the page is pointing to the correct server name.

Back to the INDEX.
Error in determining upgrade information. Possibly invalid database.
CQ2001: This error occurred in the Rational ClearQuest Maintenance Tool when attempting to connect to an existing, previously working, Oracle schema respository. The administrative login to the Oracle instance was invalid, not the database.

Back to the INDEX.
A user information entry in the database user-database is newer than the corresponding entry in the master database.
CQ2001: This error occurs when attempting to update user information via the User Administration tool in the Designer. If the designer is open when a user changes their own information, such as their password, from the client or web interface, they will get an error message that states the database was not upgraded and their password was not changed. However, it really was changed in the user database they are logged into, but not in the master database. Now, when you attempt to push new user information to the user databases from the Designer, it gives the above error message. There is no choice but to log out of the Designer and log back in so that both master and user databases will be in sync.

Back to the INDEX.
Unable to connect to database server; unable to start specified database.
This error occurred when attempting to connect a CQ2001A client to a SQL Anywhere server schema repository when the two machines were in different subnets. Normally, all that is needed to connect to a schema repository is to enter the correct paramters in the CQ Maintenance Tool. Those parameters are normally kept in a cqprofile.ini file on the server. However, as of CQ2001A, if SQL Anywhere is chosen as the vendor, there is no way in the Maintenance Tool to specify any special connect options.
To connect to a SQL Anywhere schema repository across subnets, the following system environment variable must be defined on the client: 
  CQ_SA_OPTIONS = "-x tcpip{dobroadcast=no;host=server-ip-address}"
Back to the INDEX.
ERROR! Unable to login to the database using the following connection information: ... Could not find file '(unknown)'.
This error occurred while attempting to delete a database from the CQ2001A Desginer. The reason for error is that the physical database was deleted from the system first. You'll need to following the procedure for logically deleting the db if the physical db is gone.

Back to the INDEX.
Cannot display the page.
This error occurred when attempting to log into CQ in the web interface using CQ 2001A and SQL Anywhere on Windows. This is a registry permission problem.
1) Open regedt32.
2) Go to the key HKEY_LOCAL_MACHINE\Software\Sybase\SQL Anywhere\Sybase SQL Anywhere 5.0.
3) Give the Anonymous user Full Control of this key. Select Allow Inheritable Permissions.
4) Go the HKEY_USER\.Default\Software\Rational Software\ClearQuest and perform step (3).
5) Reboot the machine.

Back to the INDEX.
[State =01000][Error=1326][Microsoft][ODBC SQL Server Driver][SQL Server]"Logon failure: unknown user name or bad password.
This error occurred when attempting to login into CQ via the web. The login error occurred because the IUSR_machine account was not defined on the server where the SQL database resided. To rectify this, the IUSR_machine account must be a domain account or defined locally on the SQL database server machine.
Details:
Error 1326 means "Logon failure: unknown user name or bad password." This error is raised because the IIS Service does not have any rights to use the named pipe.
In order for a client to gain access to a Windows NT named pipe, the client needs to be validated by the Windows NT server. This is normally accomplished through a Workgroups-style validation method where identical usernames and passwords are created on the client and the server, or the domain method where both the client and server are domain members.
The Internet Information Server (IIS) setup process creates a Windows NT ID called IUSR_machinename (where machinename is the name of the Windows NT server), and adds that user to the Guest local group. The IIS service runs under this Windows NT account name.
If the connection to IIS is anonymous, IIS uses the Windows NT account IUSR_machinename and so any network activity performed by IIS is done under this account ID. If the SQL server resides on the same server as IIS, then named pipes connections work and validation is successful. If the SQL server resides on a separate server from IIS, then the IUSR_machinename account needs to be validated on the Windows NT server that SQL resides on.

Back to the INDEX.
Unable to obtain a ClearQuest web license.
Unable to obtain a CQ web license when CQ Web and CQ Client are running on the same machine. One possible cause could be the permissions required for the FlexLM License Manager key in the registry.
By default, the FlexLM License Manager key in HKEY_LOCAL_MACHINE\SOFTWARE has default permissions for the "Everyone" group (Windows NT) or the "Users" group (Windows 2000). The account that is used as the Anonymous User for the website accesses this key using those rights.
If those rights are modifed or the group restircted from that key, the web will not be able to access the site, while the licenses will still be served to other workstations from the OS so the ClearQuest client functions normally.
To correct this, add either the approriate Anonymous user or the "Everone/Users" group with the appropriate special permissions.
1) Using Regedt32 navigate to the key HKEY_LOCAL_MACHINE\Software\FlexLM License Manager.
2) Choose Security and Permissions. Add the Anonymous user or the IUSR or the group as appropriate. Be sure to add the selection to cascade changes to the subkeys.
The default permissions are:
Windows NT: Query Value Set Value Create SubKey Enumerate Subkey Notify Delete Read Control
For Windows 2000: Query Value Enumerate Subkeys Notify Read Control

Back to the INDEX.
User database "dbname" upgrade failed. The dbname database has not been upgraded to the current revision of ClearQuest.
The error occurred using CQ 2002 when attempting to push new user information out to a user database.
At one point, the underlying schema of CQ was upgraded. The database in question had not been upgraded when CQ was. Run the following command to upgrade the user database. This example is for an Access database. Contact Rational Tech Support if working with a different db vendor. The upgrade will create a new, separate database that must be given a name different than the original. 
  # installutil upgradeuserdbsystemversion -dbset dbsetname admin-login admin-passwd logicl-dbname MS_ACCESS "" "path-to-upgraded-db" admin admin admin admin
Back to the INDEX.
!%$ ===== Caught a (PaMsgException *) exception =====
Updated: 12-15-08
!%$ The database "MASTR" belonging to master database "dbset" is an invalid name. Enter the correct name of a ClearQuest user database.
This error occurred on a Windows system while attempting install a new package into the schema repository using CQ 2002. The command being executed was: [packageutil installpackage -dbset 2002.05.00-slqserver admin "" DefectTrackingSetup 1.0]. The packageutil subcommand called "installpackage" is, according to the documentation, synonymous with the subcommand "installintoschemarepo". However, the use of installpackage generated the error. The subcommand was switched to installintoschemarepo and the package was installed correctly.
This error can also occur if the dbset name has non-word characters in it and has not been double-quoted. For example, if your dbset name is my-dbset, put it in double quotes: "my-dbset".

Back to the INDEX.
***error: Cannot save document: This is not a valid file name.
This error occurred when attempting to a run a report from within the CQ Client 2003.06.00 using the SoDA for Word.
Open a SoDA template from the Windows Explorer (C:\Program Files\Rational\SoDAWord\template\ClearQuest) and go to SoDA->Options. A bug in the install of 2003.06.00 didn't create the directory listed in "Tight integration report directory". After simply creating that directory, SoDA reports could be run from within CQ.

Back to the INDEX.
ERROR! The database name for fieldname can't be renamed.
This error occurred in the Designer when attempting to rename a field. Normally when you rename a field, the "Field Name" gets changed, which is what the user sees, and the "DB Column Name" does not. However, in this case, the "Field Name" gets changed, you get the error, but the user still sees the old name.
I don't if there's better answer, but I got around the error by checking the schema in, and then checking it back out again.

Back to the INDEX.
The record "" could not be found. It may have been deleted.
This error occurred when running a query against a set of stateless records. It is unknown what record it is looking for and why.
The query cannot complete, even though there are known good records. Fix unknown.

Back to the INDEX.
New schema repository doesn't show up in the web interface pulldown list. Updated: 08/16/06
When you create or link to a new schema repository, when logging in to CQ, it will prompt you for which schema repo to user. However, note that the list of schema repositories is personal to the user that imported the .ini file or created the link. This means, that only the user who originally installed and set up the web interface can make modifications to the .ini for the schema repos that show up when logging into the web. It is unknown if there is a way to have a "system" list of schema repos that all users of that server can see.

Back to the INDEX.
The database that you are trying to open or convert is currently in use, or you do not have permission to open it exclusively.
You attempted to open a database that is already opened exclusively by user 'username' on machine 'machinename'. Updated: 08/31/06
These errors occurred when attempting to upgrade an MSAccess database. Ensure all users are out of the database. If this is the schema repository, all schemas must be checked in.
If you still get the error, there's a possibility that the lock file is corrupt. In the directory where the database is, there is a corresponding .ldb file. Delete it. If you get the error "Can't delete database-file-name: It is being used by another person or program.", check to see if there are any hung "clearquest.exe" or "cqdesign.exe" processes. If there are, kill them. If not, you'll most likely have to reboot the computer and then delete the .ldb file.

Back to the INDEX.
These fields have invalid values: Updated: 03/28/07
This error occurs when saving a record. If a field is listed, simply go to that field and fill in a value. If the error message doesn't list any fields, it probably means that it is a hidden field. It is the assigned "Title" of a field and not its name that appears in the error message. If there is no field listed, the schema probably has a bug in it, as there is no way for a user to fill in the value.

Back to the INDEX.
The database dbname claims to be using schema schemaname revision # version # but the latest version of that schema revision is #. Updated: 06/08/07
This error can occur when logging into the schema repository or user database, or when attempting to push changes out to the user database from the Designer.
The reason for the version mismatch is unknown. If the version in the user database is higher than the version claimed by the schema repository, the schema repository version can be modified to match. In the schema repository, modify the value in the MASTER_SCHEMAREVS table to match the user database. In the error message, "revision" refers to the schema level, whereas "version" refers to how many times you have pushed the schema out to the schema repository during the current checkout of the schema.

Back to the INDEX.
cqstreambuf::underflow: Conversion error.
Updated: 12/15/08
CQ version: 7.0.1
This error occurred while attempting to import a schema on the CLI using cqload.
A schema dump file has special end-of-line formatting. If that file is opened in an editor, such as Wordpad, and then saved, the end-of-line characters can get changed. If the schema file must be edited in some way, try editing it in Word instead.

Back to the INDEX.
The name UCM_CQActBeforeChact is already in use.
Updated: 12/15/08
CQ version: 7.0.1
Received this error when attempting to upgrade package versions.
For unknown reasons, the schema was actually at UnifiedChangeManagement package version 5.0, while the database thought is was at 4.0. So, the upgrade was attempting to apply the 5.0 changes and couldn't.
Note that the only way to determine the actual schema package level was to examine the schema and look at the changes applied by the various package revisions. Eventually you'll be able to see that a given change wasn't applied yet, therefore the previous version is the actual version of the schema.
The fix is to update the database with statements similar to the following. Note that you must quit the SQL editor to see the changes. 
	> update packagerev_usage

	set packagerev_dbid =
	(select master_dbid from packagerevs_1 where package_dbid =
	(select master_dbid from packages_1 where name = 'PACKAGE') and rev_string = 'NEWREV')

	where package_dbid =
	(select master_dbid from packages_1 where name = 'PACKAGE') and packagerev_dbid =
	(select master_dbid from packagerevs_1 where package_dbid =
	(select master_dbid from packages_1 where name = 'PACKAGE') and rev_string = 'OLDREV') and

	schema_name = 'SCHEMANAME';

Back to the INDEX.


Return to the home page .

This page last modified: 12/15/2008