Troubleshooting Common Licensing Issues

Overview

Troubleshooting Common licensing issues is simple and you can troubleshoot many problems on your own. In this article, we will discuss common licensing issues and how to troubleshoot the root cause of it

Information

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

  • On UNIX, use one of the following commands: lmstat or ps -a.
  • On Windows, navigate to Start > All Programs > Auto-trol > Attc License
    Management 5.1 > lmtools > Server Status tab.
  • On Windows, check the Task Manager - both lmgrd and attclmd
    should be in the process list.
  • Look at the license log file to verify that daemons have connected
    properly.
    It is located in the folder where you installed the license. By default, it is:
    C:\Users\<username>\AppData\Roaming\Auto-trol
  • Verify that TCP/IP communication exists between server nodes and client
    nodes.
    • Use ping to verify that TCP/IP communication exists.
    • Use ping on the server node to ping itself.
  • Examine the license log file and any error messages for more information.

 

Licensing error messages can be divided into several categories:

  • Initialization errors - Occur when a product is initializing licenses.
  • Checkout errors - Occur when the product can’t check out a feature’s
    license.
  • Checkin errors - Occur when the product has trouble checking in a
    feature’s license.


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

• ATTClm errors take the form -5XX (for example, -506 ).
• FLEXnet Publisher errors take the form -X (for example, -8 ).
• System errors take the form X (for example, 23 ).

 

Initialization Error Format

The initialization error message syntax is:

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

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


Check-Out Error Format

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

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

where:
< feature > Is the feature name.
< error number > Is the error number. This number indicates a FLEXnet
Publisher, ATTClm, or system error, depending on its value.
<error message > Is the error message.

 

Check-In Error Format

Check-in errors occur when ATTClm can’t check-in, or release, a license. Take action based on the error message.
The check-in error syntax is:

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


where:
< feature > Is the feature name.
< error_number > Is the error number. This number indicates a FLEXnet
Publisher, ATTClm, or system error, depending on its value.
< error_message > Is the error message.

 

 Back to top

Comments

0 comments

Please sign in to leave a comment.