Symptoms

While checking out licenses from a Cloud License Server (CLS), the error Features are not available due to a rule rejection is observed.

Diagnosis

This error is possibly due to the mismatch on the parameter on which the request sent to the CLS to check out licenses than the already available rules/model/feature selectors at the CLS. This means if the request does not contain the feature selectors that are already available at CLS, then you may receive this error.

One can verify the current existing rules against a CLS instance by sending the GET calls against the endpoint.

For example: https://flexXXXX.compliance.flexnetoperations/api/1.0/instances/<CLS_ID>/rules

Solution

You need to update the rules first on the CLS, on which the license checkout is expected. The rule update can be done by sending a model update POST call against the /rule endpoint. The following is a sample request body which defines rules to check out licenses only on specific hosts.

model "test" { on hostid("Test1223+","gkasgfkA2124") { use "default" accept } on any() { deny } }

For more information on /rules POST call, see the FlexNet Embedded License Server Producer Guide.

NOTE: Feature selectors and feature partitions should not be used at the same time, as it may produce unexpected errors. This is noted in the FlexNet Embedded License Server Producer Guide under the section Limitations of Partitions.