3 Set up your license server. See “Licensing ClearQuest” on page 89. 4 Optionally, customize your installation. See the Administering Rational ClearQuest guide for details on customizing ClearQuest. 5 Install ClearQuest on the client machines and provide users with the information they need to connect to ClearQuest. A system administrator must install the FLEXlm License Server software on a server to set up floating licenses. Use the Rational License Key Administrator to set up floating licenses for your system. See “FLEXlm License Server Installation” on page 35.
For each and every project, as per the Client’s requirement and ease, various tools are recommended and used.
For example, few projects prefer ‘Quality Center’ for managing the project’s data whereas few others prefer Rational ClearQuest tool.
Rational ClearQuest is a defect management and workflow automation software from IBM Rational software division.
The main purpose and use of this IBM ClearQuest tool is a Bug and Change Request tracking tool for testing related projects. With this tool, you can track the present stage and situation of a project development at any point.
Here is a quick intro to Rational ClearQuest (CQ) tool.
What You Will Learn:
Few uses and points about IBM ClearQuest:
1) Defects details and CRs (Change Request) of a project are maintained and managed with ClearQuest.
2) The CQ tool works in a Client- Server environment (Group of computers termed as clients contact a server through the internet).
3) With CQ, you can view the project’s current status and analytics through running queries (Queries – Used to view the project’s reports and charts).
4) The important terminology used in CQ is Schema and Schema Repository.
Schema – Structure for a database which helps model or organize the data, processes etc., of a project. The schema includes the structure of data, record type definitions, states of a record, actions to modify the state of a record, forms to submit a record etc.
Schema Repository – A database with one or more Schemas is termed as Schema Repository.
Generally, CQ has several predefined schemas which you can use as they are or can modify it as per your requirement.
Few examples of predefined schemas are ‘Defect Tracking Schema’ – contains the fields required to start tracking the defects, ‘Blank Schema’ – contains the system fields- you can use this to create a new schema from scratch.
5) A project’s daily activities can be managed through ClearQuest tool.
6) The CQ tool makes everyone’s work easier and simpler as it unites developers, testers, project leaders, project managers, Clients etc.,
7) Based on your process in the project you can customize CQ as per your needs.
How to Install IBM ClearQuest:
IBM Rational ClearQuest can be downloaded from here.
Note: If you want to download CQ software from the above link first you need to create an IBM id. Then can proceed with the download process. The product installation files also include IBM Installation Manager and there is no need to download it separately.
To install CQ you need to install IBM installation Manager on your computer first.
‘Installation manager’ is a program used for installing and updating the IBM applications. It keeps track of all the IBM apps that are installed on your computer.
(Note: Click on any image for enlarged view)
Step #1)Installation Manager can be installed from Launchpad program.
Launchpad is a web application. Launchpad is located in the DVD of the software. If the DVD is inserted then launchpad starts automatically. We should run the ‘launchpad.exe’ file as administrator.
A sample of Launchpad application is shown in the below screenshot.
Once the launchpad program starts, the installation manager starts too. And, the product installation starts automatically.
Step #2)We can also get the Installation manager from the folder of product installation files by running the ‘install.exe’ file.
Manually installing the Installation Manager,
To install Rational CQ you need to follow the below steps,
Note: A CQ installation generally has one Schema Repository with one or more user databases. Each project has separate user database.
How to open ClearQuest:
To open CQ, click on Start Menu -> Rational ClearQuest
To login into CQ, a unique login ID is required. For every team member, a CQ unique login ID will be created by the required authorities (Like Administrator).
Note: Default username to login into CQ is ‘admin’ and do not require any password for this admin login.
A project manager or the CQ administrator will create the Databases required for the project and configures the same as per the project requirements.
To connect to any desired schema repository of your project then follow the below steps:
From the File menu of the above ClearQuest Window select Database -> Connect -> New Connection
How To Install Rational Rose License Server Id Card
After selecting the New Connection a Schema Repository dialog box gets opened. On that box select your desired Database Set and Click Next
Now another dialog box ‘Additional Connection Information’ gets opened. Enter ‘Admin’ as the User ID and click Finish.
Finally, on Connect dialog box click OK. This Completes the CQ Connection with your desired database.
Now the main screen of CQ will be displayed.
Main Window of CQ has Workspace, Query Builder, and record form.
Let's see the significance of each:
#1) Work Space: Workspace contains the list of queries both ‘Personal and public’, defects, charts, and reports.
Personal Queries are restricted to a specific project and cannot be accessed by other projects members until they have the permissions to access them.
Public Queries make it to the default queries list. They also include queries & reports of other projects that have made them public. One can copy the same to their respective folder and can modify them as per their project’s requirement.
#2) Query Builder: This displays the results of a query. If we click on any record then its corresponding data will be displayed in a Record Form. We can modify and view the data in the records.
#3) Record Form: Through this, you can modify and view the records.
How to create a Change Request:
Before proceeding with the development and testing activities of a project, its corresponding Change Request (CR) needs to be created in IBM ClearQuest. Mainly the Change Request will be created for an issue in the software or for a defect or can be for an enhancement in any software. This CR can be created by the administrator or the project manager. The layout or format of a Change Request is termed as ‘record type’.
This CR can be created by the administrator or the project manager. The layout or format of a Change Request is termed as ‘record type’.
https://entrancementtrack927.weebly.com/mac-for-visual-studio.html. To create a Change Request, click on ‘New Defect’ button from the toolbar.
By filling the necessary data in all mandatory and required fields we can submit a CR. We can even attach any documents to a CR so that anyone can view the same for further information regarding the CR.
If the respective configurations have been set by the administrator then the team members can receive the email notification regarding any CR submission or modification.
By default, a CR will be in ‘Submitted’ state. We need to assign (Actions -> Assign) the same to an engineer who is going to work on it. Then the CR state changes to ‘Assigned’.
If any data in CR needs to be modified then go to Actions -> Modify and then update or change any information of CR. During this process, the state of the CR remains the same.
Before starting work, the engineer assigned with the CR has to change the record state to ‘Open’ (Actions -> Open) so that everyone will come to know that he is working on it. Once his work gets completed then he needs to update the state of CR to ‘Resolved’ (Actions -> Resolve).
Once the developer or the engineer changes the CR state to Resolved then a mail gets triggered to the tester or quality assurance team. Then, they will test and verify whether the CR is working properly and fixed correctly by the engineer. If so the CR state is changed to ‘Closed’ (Actions -> Close).
How to Create a New Defect:
Generally, a defect is a flaw in the software that is going to be developed or that has been delivered. A Defect may also be an imperfection in the software. Mainly it means a deviation from the expected outcome of the software.
The main purpose and intention of logging a Defect is to communicate the details of the issue or problem to the concerned team or department.
General details of a defect include Name or ID, description, project, project release, detected by, status or state, assigned to etc. Please note that the different tools have different terminology.
To create a New Defect in ClearQuest follow the below steps,
Step #1)Click on the menu File -> New -> Defect
Step #2) ‘Create Defect’ window gets displayed. Red fields in that window are mandatory fields.
Step #3)Enter data in all the fields as needed. Attachments can also be added in the ‘Attachments’ Tab.
Step #4)Fill in all the required data in the respective fields and click on OK. The defect record gets created.
Step #5)To view the defect that you have created you can run a query which returns the defect record into the result-set pane or you can also use the list of recently submitted records in IBM CQ. For this, expand the ‘Recently Submitted’ folder and double click on the record you want to view.
How to use Queries:
On your first CQ launch, you may not have any predefined queries. With more and more exposure to the tool, you will become familiar with this client and will have few queries, reports, and charts executed automatically for your login.
The Queries feature of ClearQuest is used to view and track the records that include the changes made to the CR.
In CQ, there is a folder named ‘Public Queries’ in the workspace. It contains the default queries that can be used by every CQ user.
From the list of queries in the Public folder select (double-click) the query required and run the same to get the data as desired. Then the query results will get displayed on the right-hand part of the screen.
Editing a Query:
If an existing query does not satisfy your requirement then copy the same query to your project folder in Personal Queries folder. Then go to ‘Query Editor’ and edit the query as per your requirement and run the query.
You can use the existing query to build a new query. To do this, on the Create New Query window select the ‘Copy the design from an existing query’ checkbox option and then select your required query from the list. You can also select the filters and display layout of the query results.
Writing a new Query:
To write a new query go to ‘Query’ menu and select ‘New Query’ and then proceed further with the steps for creating a new query.
To create a query we need to follow few steps, such as:
Step-by-step procedure of creating New Query with an example & snapshots:
Step #1)Open the menu File -> New Query, enter any name for Query, select the Record Type as Defect and click ‘Next’.
Step #2)Query Wizard window opens. From that select the filters that you want to apply to the query. Select and move your desired filters from Fields Pane to Filters Pane.
Step #3)You can also select the desired values for your filters as shown in the below screen.
Step #4)For the display of your Query, you can select the result-set display fields as shown below and Click on Finish.
Step #5)Now your Query is ready in the left pane under Personal Queries folder.
Example: Query to get the details of defects based on their state or severity.
Import DATA from an EXCEL:
We can import the data into ClearQuest from an Excel.
For this, open the Excel from which you want to import the data. Go to the menu Data -> Import External Data -> New Web Query. Now select the data that you want to import into CQ and click on Import. Also, mention the location where you want to save the data and click on OK.
Exporting DATA from CQ:
With this export feature, you can get the result set of a query into a file so that you can use this for offline access. For this, click on the arrow next to the Export icon on result set toolbar and select the option for exporting the data into a file as Export as .txt or Export as a .xls format.
You can mention the path for the export file to be saved on your PC.
How to use Charts in CQ:
In ClearQuest, you can find existing charts which can be used for your project by making few modifications to them as per your project’s requirement.
Charts show the graphical view of the records data of CQ. There are two types of charts, Distribution charts, and Aging charts.
Distribution charts are used to view the present status of the data.
Aging charts are used to view the historical data of the project.
To modify the predefined charts from the public folder, open your desired chart and go to menu Edit -> Properties. Now you can change the data display format of the chart and also change the fields or parameters that you want to include for the graphical view.
The second way to modify the charts is to go to the Query Editor and then modify your required records and data.
How to create Reports in CQ:
By default, CQ does not have the feature to create new reports or edit them. To enable this one’s CQ needs a licensed version of Crystal Reports Designer.
How To Install Rational Rose License Server Identification
The project data available in CQ can be viewed in the form of Report and you can export the same to other formats of the document and can use them.
A report mainly consists of two things, the result set of records that are returned when a query is run and the report format file used to set the layout of the report.
At first, run the query for which you want to create a report. Then click on Create Report button in the toolbar (a button with book symbol on it). Create Report dialog box gets opened. From that box, choose the report format, select it and click on OK.
This will create your report in the selected report format with the data of the query which you have executed. You can even export this report in your desired format and can use it further.
Note: You can even create a new report that can be used repeatedly by saving it in the Personal Queries folder.
For this, go to the menu Query -> New Report. Then a dialog box gets opened to select a record type. Select a record type you need and click on OK.
Then another dialog box opens and prompts for report format and a query.
Click on browse and select a report format that you need for your report layout. Next, browse and select the query that you want to associate with the selected report format and click on OK. This will create your desired report which you can save in your Personal Queries folder and can reuse it later.
Another way to execute the existing Reports is as follows,
Expand the Reports folder in the left pane of CQ. Select your desired report to be executed and right-click on it and select Run. The report gets displayed.
For example:From the Reports folder, select the ‘Defect Detail (All)’ right-click on it and select Run.
ClearQuest Favorites:
To set your favorites in CQ, first, you need to select the particular record type like query, chart, report etc.
Then Right-Click on that record type, a pop-up menu will be displayed. Select the option ‘Add to ClearQuest Favorites’. Now the item gets added to the CQ Favorites and can be viewed in the left pane.
ClearQuest Web Client:
The CQ works in two different ways, one is as Desktop Application and the other is as Web Client. The CQ desktop application means the client is installed on the system whereas the CQ web client means the browser-based interface to CQ. With CQ web, you can access the Change Requests, track the defects etc., same as CQ desktop application.
If CQ desktop client is not installed on your system then CQ Web client is used by default. And, when CQ Web is unavailable to you, CQ desktop client is used by default.
Tips on IBM CQ Usage:
1) To get any additional information on any feature of CQ you can navigate to Help -> Contents and search for the same.
For example, if you want to get any information on queries then you can go to Help -> Contents -> Working with queries.
![]()
2) Rational Clear Quest tool is a customizable tool. With this feature, you can customize the look and feel of the display format of the result set data. For example, you can change the look of the columns to be displayed in the query list.
3) Another interesting feature of CQ is that you can set any query or report or chart to run immediately when you login to CQ. For this, right-click on the record in the left-hand pane that you want to run on your start-up and choose ‘Run at Startup’.
4) For any information regarding administering CQ, you can go through the Administering Rational ClearQuest guide that comes with your CQ product.
Conclusion:
With the knowledge you gained through this Rational ClearQuest tutorial you can have a smooth hands-on guide to work on IBM Rational ClearQuest tool for testing or development activities in your project. Once you get familiar with this tool you can write complex queries with multiple filters and conditions to get the specified data on any particular record.
Once you get familiar with this tool you can write complex queries with multiple filters and conditions to get the specified data on any particular record.
It can be the best change request management tool for tracking and managing change requests and defects on any development project including enterprise level projects.
About the author: This is a guest post by Laxmi. She is having 7+ years of Software testing experience mainly in BFSI domain.
Share your comments and questions below.
Happy testing :)
Recommended Reading
Applies to:DS-5, RealView Development Suite (RVDS), Tool Licensing (License Management)
Answer
The aim of this guide is to make it easier for you to diagnose and solve floating licensing problems with the ARM tools. The guide is intended to help you identify an error, and navigate the product documentation and Knowledge Article database to solve it.
Before proceeding further with the guide it is recommended you review the steps for setting up a floating license server, and its client workstations, in theARM FLEXnet License Management Guide.
https://brownbackup653.weebly.com/garageband-60-download-mac.html. The guide makes number a number of assumptions:
For a Windows install of RVDS, the installer will by default add the FLEX binaries to the
PATH . For Linux installs, you will need to source the configuration script generated by the installer (e.g. RVDS40Env.posh ).
If after following the steps in this FAQ you are still unable to use your tools, please contact [email protected].
Part 1: Client Or Server?
The first step in the diagnostic is to determine whether the client machine is able to successfully communicate with the server. To do this, run two quick tests:
|
On the Client | On the Server | See section on.. |
NA | FAIL | Server Problems |
FAIL | SUCCEED | Client or Connection Problems |
SUCCEED | SUCCEED | Client Problems |
Part 2: Connection/Client Problems
If the server software (
lmgrd
) is running correctly, then the next step is to determine why the client is unable to check-out a license.
On the client, open a terminal and enter the command:
armcc --vsn
The command tells the compiler to attempt a license check-out. The output will look something like this:
The error message gives much useful information. For now it is the FLEXnet Licensing error (-XXX,XXX) and the License path lines which are of most interest.
The license path is where the tools are looking for licenses. It can contain a number of entries, each will either be
<port>@<server>
(e.g. 8224@my_lic_server
or [email protected]
) or the path to a license file. In the case of license files, these should be a copy of the license file on the server (this gives the server's hostname/IP address and port). It is recommended that you use the <port>@<host>
syntax.
The error code gives the reason for the failure, the most common codes are listed below:
NOTE: It is possible that there is more than one reason the tools are unable to connect to the server. The error message from the tools will only give the first error. So once you have resolved this issue, you should re-run the command to check for further errors!
The following gives a list of common error codes:
FLEX error -4: Licensed number of users already reached
FLEX error -12: Invalid data returned from server system
FLEX error -15: Cannot connect to license server system
FLEX error -18: License server system does not support this feature
FLEX error -25: License server system does not support this version of the feature
FLEX error -38: User host on EXCLUDE list for feature
FLEX error -39: User host not on INCLUDE list for feature
FLEX error -68: License BORROW support not enabled
FLEX error -96: License server machine is down or not responding
FLEX error -97: The desired vendor daemon is down
FLEX error -114: SIGN= keyword required, but is missing from license certificate
FLEX error -9990: Invalid error code
FLEX error -12: Invalid data returned from server system
FLEX error -15: Cannot connect to license server system
FLEX error -18: License server system does not support this feature
FLEX error -25: License server system does not support this version of the feature
FLEX error -38: User host on EXCLUDE list for feature
FLEX error -39: User host not on INCLUDE list for feature
FLEX error -68: License BORROW support not enabled
FLEX error -96: License server machine is down or not responding
FLEX error -97: The desired vendor daemon is down
FLEX error -114: SIGN= keyword required, but is missing from license certificate
FLEX error -9990: Invalid error code
NOTE: This test uses
armcc
to check-out a license. It may be that this check-out succeeds, but the check-out for other tools fail. If this is the case for you, run the tool that is failing and see what error code it reports. The codes are common across ARM development tools.
Part 3: Server Problems
If the lmutil command failed on the server, it is likely that the FLEXnet server software (lmgrd and/or armlmd) is not running. You should confirm, using Task Manager on Windows or the ps command on Linux.
If the processes are listed, these may be stale processes left over from a crash. Usually you will have to manually kill these stale processes before attempting to re-start the server software. BEWARE - it is possible to run multiple lmgrd servers (but not
armlmd
) on the same physical machine - refer to here.
Once you have killed any stale processes try manually re-starting the lmgrd software. The command is as follows:
lmgrd -c /path/to/license.dat -z
Replacing '
/path/to/license.dat
' as appropriate. The -z
flag causes the server to print all log and diagnostic information to the console. This is not usually desirable, but useful for trouble shooting. Alternatively, you can replace -z
with -l <filename>
, which directs the messages to a file.
If the server starts up correctly, you will see something similar to this:
C:>lmgrd -c license.dat -z
(lmgrd) -----------------------------------------------
(lmgrd) Please Note:
(lmgrd)
(lmgrd) This log is intended for debug purposes only.
(lmgrd) In order to capture accurate license
(lmgrd) usage data into an organized repository,
(lmgrd) please enable report logging. Use Macrovision's
(lmgrd) software license administration solution,
(lmgrd) FLEXnet Manager, to readily gain visibility
(lmgrd) into license usage data and to create
(lmgrd) insightful reports on critical information like
(lmgrd) license availability and usage. FLEXnet Manager
(lmgrd) can be fully automated to run these reports on
(lmgrd) schedule and can be used to track license
(lmgrd) servers and usage across a heterogeneous
(lmgrd) network of servers including Windows NT, Linux
(lmgrd) and UNIX. Contact Macrovision at
(lmgrd) www.macrovision.com for more details on how to
(lmgrd) obtain an evaluation copy of FLEXnet Manager
(lmgrd) for your enterprise.
(lmgrd)
(lmgrd) -----------------------------------------------
(lmgrd)
(lmgrd)
(lmgrd) pid 524
(lmgrd) Done rereading
(lmgrd) FLEXnet Licensing (v10.8.5.0 build 31891 i86_n3) started on my_lic_server (IBM PC) (2/5/2009)
(lmgrd) Copyright (c) 1988-2006 Macrovision Europe Ltd. and/or Macrovision Corporation. All Rights Reserved.
(lmgrd) US Patents 5,390,297 and 5,671,412.
(lmgrd) World Wide Web: http://www.macrovision.com
(lmgrd) License file(s): license.dat
(lmgrd) lmgrd tcp-port 8224
(lmgrd) Starting vendor daemons ..
(lmgrd) Started armlmd (pid 132)
(armlmd) FLEXnet Licensing version v10.8.5.0 build 31891 i86_n3
(armlmd) Server started on my_lic_server for: compiler
(armlmd) EXTERNAL FILTERS are OFF
(lmgrd) armlmd using TCP-port 1142
If the server appears to have started correctly, re-run '
lmutil lmstat -a
' to check that you are able to query it successfully. If this also succeeds, then monitor the server as the problem may come during operation rather than start up.
Otherwise, you will see an error message at some point after the notice. How far through the start up sequence it got before the error gives an indication of where the issue lies. Below are common messages to see in the output:
Part 4: Error Code Descriptions
-4: Licensed number of users already reached
A license file provides a fixed number of seats for each component. If all the seats are in use, further requests will not be satisfied. Normally, the server will queue a request until a seat becomes available - so that the client does not see a failure. On the client you would see something like this:
C:>armcc --vsn
Waiting for license..
There are cases where this queuing mechanism fails, and this is when you would see this error message on the client. Please see the following Knowledge Article for more information:
-12: Invalid data returned from server system
This message is normally only seen with older tools, such as ADS 1.2. It means that the something is interfering with the communication between the server and client. This is covered in more detail in the following FAQ:
-15: Cannot connect to license server system
The hostname or IP address specified in the license path is valid. However, the tools were unable to open a connection to a FLEX license server on the specified port. Possible causes include:
-
The FLEX server software (lmgrd) has not been started.
If 'lmutil lmstat -a
' succeeded on the server then the server software is be running. -
On the client, you have specified the wrong port on
ARMLMD_LICENSE_FILE
/LM_LICENSE_FILE
.
Check the port listed in the server's lmutil output, does it match the setting on the client? -
A firewall is blocking the connection.
It is possible that something is blocking communication, typically a firewall. This is covered in more detail in the following FAQ:
-18: License server system does not support this feature
The tools were able to connect to the license server successfully. However, the server does not host the feature that the client was trying to check-out. This can happen for a number of reasons. For example, RVDS is sold as Professional and Standard editions. The Professional edition includes additional features. If you were to try using the Professional edition with a Standard license, you could see this error.
Another explanation could be that you have multiple license servers. How do i add spotify to alexa app. For example, one server for ARM licenses and another third party licenses. In which case this could indicate that you are specifying the wrong server on the search path. Check the value of
ARMLMD_LICENSE_FILE
on the client, and that this matches the ARM license server.
NOTE: Remember that you can specify multiple license sources on the search path!
-25: License server system does not support this version of the feature
The tools were able to connect to the license server successfully. The server hosts the feature that was requested - but not the correct version. This usually indicates that you are trying to use an older license with a more recent tool. For example, using the RVDS 4.0 tools with an RVDS 3.1 license.
NOTE: You may see this message in license server logs, even when the check-out succeeded. This is due how the server operates internally when it hosts a mix of licenses, and can be ignored. For further information please seeFAQ: 'Why am I getting DENIED messages in my server log?'
-38: User host on EXCLUDE list for feature
-39: User host not on INCLUDE list for feature
The FLEX server allow licenses to be reserved for certain users, or groups of users. This is done using an options file.
These messages can be seen when a user attempts to check out a license reserved another user/group. For more information on option files, please see the following FAQ:
ARM's tool licenses do not support the FLEX borrow feature. Attempting to user borrow will result in this error. For further information, please see the following FAQ:
-96: License server machine is down or not responding
There are several variants of this message:
-96,7 '
This message is a networking fault being flagged by the host operating system (in this case Windows). It shows that the OS failed to translate the hostname into an IP address. Check that the correct name is being specified, and that your network's name resolution is working correctly. If these are correct, try using the '
WinSock: Host not found (HOST_NOT_FOUND)
'This message is a networking fault being flagged by the host operating system (in this case Windows). It shows that the OS failed to translate the hostname into an IP address. Check that the correct name is being specified, and that your network's name resolution is working correctly. If these are correct, try using the '
ping
' command to check that the client can see the server on the network.
Alternatively, try using the server's IP address instead of the hostname.
-96,491
This usually indicates the port being used by armlmd is being blocked, possibly by a firewall. Check on the server which port is being used by the daemon and that it is open on the server's firewall.
This usually indicates the port being used by armlmd is being blocked, possibly by a firewall. Check on the server which port is being used by the daemon and that it is open on the server's firewall.
By default, the armlmd port number is not specified. It is assigned by the host operating system at server start. If the server has a firewall it is advisable to set the port manually. In the license file change:
VENDOR armlmd
To:
VENDOR armlmd port=XXXX
Where
XXXX
is the port number you wish to use.
-97: The desired vendor daemon is down
In this case the tools were able to contact the license server (
lmgrd
), but the vendor daemon (armlmd
) did not respond. This usually indicates that armlmd has crashed. Check the server's debug log, you should see a message indicating that lmgrd
lost its connection to armlmd. Shut down lmgrd
, and check that there are no stale lmgrd
or armlmd
processes. Then re-start lmgrd
.
-114: SIGN= keyword required, but is missing from license certificate
This message is displayed when the server attempts to issue an old format license to a more recent tool. For example, trying to issue an ADS license to RVDS. Normally this will not happen, however there are cases where it can. Please see this FAQ for further information.
NOTE: You may see this message in license server logs, even when the check-out succeeded. This is due how the server operates internally when it hosts a mix of licenses, and can be ignored. For further information please see this FAQ.
The license file is missing the
SERVER
line. This could be because it has been edited, or accidently commented out. Try re-downloading the license file from ARM's website. Alternatively, you may be passing a node-locked license file, which can not be hosted in this way.
lmgrd
has launched and parsed the license. It has tried to launch the ARM vendor daemon (armlmd
), but was unable to locate the executable. lmgrd
will have searched on the PATH
, and within the same directory as itself. Check the location of armlmd
(armlmd.exe
Coh homecoming download mac august 22. on Windows) and ensure that it is on the search path. Alternatively you can specify the location in the license file. The file from ARM will have this line:
VENDOR armlmd
Change to:
VENDOR /path/to/armlmd
![Rational rose cost Rational rose cost](/uploads/1/3/3/2/133296530/231954396.png)
The port specified on the
SERVER
line of the license file is in use. This is usually caused by having a lmgrd process already running, for example a stale process.
Alternatively, if
lmgrd
has previously crashed the OS may not yet had released the port.
It is possible, but rare, that the port is being used by another application.
(armlmd) Invalid license key (inconsistent authentication code)
There are two common causes for this error:
-
The hostid in the license file does not match the machine. You will need to rehost the license to use this machine.
-
The license file has been edited. Only a few sections of the license file can be editted, editing any other section will result in this error. Re-download the license file from the ARM web licensing portal.
Rational Rose Online
The feature specified has expired. If all the features in the license file have expired the server will fail to start.
(lmgrd) MULTIPLE 'armlmd' license server systems running.
You can run multiple FLEXnet license servers on the same machine - if they are for different vendors' licenses. However, only one instance of
You can run multiple FLEXnet license servers on the same machine - if they are for different vendors' licenses. However, only one instance of
armlmd
(the ARM vendor deamon) can be running on the machine. If armlmd is already running when the server software starts it fail with this error:
There are two common causes of this error. You be trying to run two instances of the license server on the same machine - both hosting ARM licenses. This is not supported. You will need to merge the license files, and host them from a single instance of the server software. Merging license file is covered here.
Alternatively, if
lmgrd
has previously exited uncleanly it is possible that armlmd
did not close down. You should check for stale instances of armlmd
, and terminate them. On Linux this can be done with the 'ps -ax | grep armlmd
' command. On Windows you can use Task Manager.
Unfortunately this error message is not very informative. It is usually caused when the server is passed a node-locked license. This configuration is not supported, and leads to this error message. The message is only seen at the point a client attempts to use the license, not when the license it initially parsed. You confirm whether this is the cause by running 'lmutil lmstat -a' on the either the server or a client. If a node-locked license is present on the server, the lmstat output will include one or more lines similar to this:
Users of <feature>: (Uncounted, node-locked)
To resolve this issue you must remove all the node-locked licenses from the license file.
This error can be seen when using Microsoft Windows for the license server. The armlmd daemon requires libraries from Microsoft Visual Studio, if they not present this error is seen. Refer to:
If you see this when starting the license server:
This shows that your license file does not contain a SERVER line. The SERVER line in a license file should be near the top of the file, and the format is:
Possible causes include:
- Passing the wrong file to lmgrd. Check the command used to start the server, and verify the file path.
- Passing a node-locked license to lmgrd. This is not supported, only license files containing floating licenses should be passed to lmgrd.
- You have edited the license file, and removed the SERVER line.
How To Install Rational Rose
Article last edited on: 2016-01-11 17:49:23
How To Install Rational Rose Software
Rate this article
Comments are closed.
Author
Write something about yourself. No need to be fancy, just an overview.