Skip to Content
Information
Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

One or more CIs are not related to any software license certificates

The following table lists possible causes why one or more CIs would not be related to any software license certificates, along with the diagnostic method to determine the cause:

Tips for troubleshooting one or more CIs are not related to a software license certificate

Possible cause

Diagnostic method

No software license certificates are applicable for the CI.

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

View the license certificate, as described in Reviewing-a-software-license-certificate. If no other CIs appear on the Software Assets tab, continue to diagnose the cause, as described in No-CIs-are-related-to-a-software-license-certificate. If the Software Assets tab lists incorrectly related CIs, continue to diagnose the cause, as described in Incorrect-CIs-are-related-to-a-software-license-certificate.

A CI could be related to multiple certificates. Because the License Engine cannot determine the appropriate certificate, the CI is not related to any software license certificate.

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

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

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

Remedy Asset Management 9.0