- Revenera Community
- :
- FlexNet Embedded
- :
- FlexNet Embedded Forum
- :
- Re: Info messages versus Capability Request Report
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Info messages versus Capability Request Report
We are (were) using info messages to "send usage info" from a device to FNE.
However, according to "FlexNet Embedded 2020 R3 License Server Migration Guide" info messages are no longer supported.
So I'm trying to use Capability Request with operation REPORT for the same task.
When reported count is greater then the amount on FNE (overage mode), I get the following error :
"Unable to handle request for feature (..) due to insufficient count"
Is there any way we could make that work ? (It worked with info messages)
We do not use metered licenses.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @lkrecioch ,
Sorry, yes, infomessage have been deprecated for awhile now, yet it does provide insight that you are a long time user 🙂
Unsure of the specific kit (Porting, Device or XT) you're using and language, but can you try using the "partial" configuraiton?
Also, is the license model configured metered and using any overdraft?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Thank you @ejohnson1 !
We are using C Porting Kit.
We were using info messages but now (finally) the time has come to upgrade our FNE.
We never used any metered licenses and we would very much have it stay that way (for backwards compatibility)
As for the partial usage: I found this in the Reference Guide :
“The partial feature setting is not compatible with undo(FLX_CAPABILITY_REQUEST_-
OPERATION_UNDO) and report (FLX_CAPABILITY_REQUEST_OPERATION_REPORT) request
operations.”
If this correct, we cannot use this for reporting ?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi @lkrecioch ,
Undo and Report both are associated to metered license models (like the screenshot in my initial reply).
My understanding of your example scenario is:
1. LLS has a count of 10 licenses for F1
2. 9 of F1 are already checked out
3. Alice wants to check out F1 also, yet it the count required = 2
4. Alice is denied "Insufficient feature count"
If this is the scenario, setting the partial flag within the capability request means Alice will not be denied; instead the LLS will fulfill to her the last count = 1
Let me know if that make sense 🙃