Troubleshooting Common Licensing Issues

Overview

 

This article provides information about common licensing issues and serves as a guide on how to troubleshoot their root causes. 

 


Information

 

Verify that the license daemons/services (lmgrd, attclmd) are running on the server:

  1. On UNIX, use one of the following commands: lmstat or ps -a.

  2. On Windows, navigate to Start > All Programs > Auto-trol > Attc License Management 5.1 > lmtools > Server Status tab.

  3. On Windows, check the Task Manager. Both lmgrdand attclmdshould be in the process list.

  4. Look at the license log file to verify that daemons have connected properly. It is located in the folder where you installed the license. The default path is:

    C:\Users\<username>\AppData\Roaming\Auto-trol

  5. Verify that TCP/IP communication exists between server nodes and client nodes:

    1. Use ping to verify that TCP/IP communication exists.

    2. Use ping on the server node to ping itself.

  6. Examine the license log file and any error messages for more information.

 

Licensing error messages can be divided into several categories:

Category

Description/Format

Initialization errors

Initialization errors occur when a product is initializing licenses.

 

Format/Syntax:

<code reference number>:
<daemon name>(<error number>): <error message>

 

Where:

<code reference number> The troubleshooting reference number.
<daemon name> The name of the daemon process that is controlling licensing.
< error number > The error number, which indicates a FLEXnet
Publisher, ATTClm, or system error, depending on its value.
<error message > The error message.

Checkout errors

Check-out errors occur when a client can’t check out a license for the specified feature. Take action based on the error message.

 

Format/Syntax:

 

<feature name> (<error number>): <feature> not found:
<error message>

 

Where:

<feature> The feature name.
<error number> The error number, which indicates a FLEXnet Publisher, ATTClm, or system error, depending on its value.
<error message > The error message.

Checkin errors

Check-in errors occur when the product has trouble checking in a feature’s license. These happen when ATTClm can’t check-in, or release a license. Take action based on the error message. 

 

Format/Syntax:

 <feature name> (<error number>): <error message>

 

Where:

<feature> The feature name
<error number> The error number, which indicates a FLEXnet Publisher, ATTClm, or system error, depending on its value.
<error message > The error message.

 

Initialization, checkout, and check-in errors can be caused by FLEXnet Publisher, the system, or ATTClm:

Error Form
ATTClm errors -5XX (i.e, -506 )
FLEXnet Publisher errors -X (i.e, -8 ).
System errors X (i.e, 23 ).

 

 Back to top

Comments

0 comments

Please sign in to leave a comment.