This documentation supports the 21.05 version of BMC Helix ITSM: Asset Management. To view an earlier version, select the version from the product version menu.

CIs are not related to a software license certificate

When the License Engine runs, the CIs are not related to a software license certificate.

Issue symptoms

  • No CIs are related to a software license certificate.
  • One or more CIs are not related to any software license certificate.

The following table lists the issue scope and resolution for the above issues: 

Issue scope

Resolution

The categorization specified on the license certificate does not match the categorization of the discovered CIs.

Review the software license certificate. For more information on reviewing the software license certificate, see Reviewing-upgrading-and-updating-software-license-certificates.

Make the following changes to the categorization in the software license certificate:

  • Make it similar to the categorization in the CI.
  • Make it blank.

No job has been run to connect the CIs to the certificate.

Open the Manage License Jobs console, as described in Working-with-a-software-license-certificate, and check the history. View the jobs to determine whether any jobs apply to the license type.

The license type is not correctly configured. When creating a license type, an administrator specifies how the connection question and answers map to CIs in BMC Atrium CMDB. An error in this mapping can result in no CIs being related to the certificate.

An administrator can examine the license type, and also check the connection question as described in Overview of software License Management

To check for issues with rules, open the AST:ConfigRuleSet form. This is an intermediate form between the Configure License Type wizard and the License Engine.

The License Engine did not complete its run.

Check the following forms:

  • RLE:RunHistory — Provides information about each License Engine run, including status (Pending, Running, Aborted, Completed, Completed with Warning, Completed with Errors)
  • RLE:EngineExceptions — Lists Java exceptions, RLE exceptions, and the ruleset ID
  • SWLMFilter.log — This log file is typically located in the C:/Program Files/BMC Software/ARSystem/ARServer/Db/SWLMFilter.log directory of the server. If you turn on logging, this log file provides details of the License Engine job run. Logging is configured from the Application Administration console, as described in Configuring-the-license-engine.

The Company attribute (or another attribute used to connect the CI to the license certificate) is not set on the CIs.

Search for and open the appropriate CI, as described in Searching for records in the application consoles. The Company and Manufacturer attributes are always used to connect a CI to a license certificate.

Whether other attributes are required for a connection depends on the license type. For example, for a site license, the Site attribute must be specified on the computer system on which the product is installed.

No software license certificates are applicable for the CI.

On the Software Asset Management console, check the Unrelated CIs section. This section lists the CIs that could not be matched to the license certificates by a job.

View the license certificate as described in Working-with-a-software-license-certificate. If no other CIs are displayed on the Software Assets tab, check if any of the issue scope mentioned in this table are applicable and implement the related resolution. If the Software Assets tab lists incorrectly related CIs, check if any of the issue scope mentioned in Incorrect-CIs-are-related-to-a-software-license-certificate are applicable and implement the related resolution.

A CI is related to multiple certificates, because the License Engine cannot determine the appropriate certificate.

On the Software Asset Management console, check the Unrelated CIs section. This section lists CIs that could not be matched to license certificates by a job.

Review the inbox for a message with additional details. From the inbox message, you can relate the CI to the appropriate certificate.