Revenera Community Knowledge Base

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Knowledge Base Articles
The license rights do not need to be defined in a license file. They can be specified as a literal string anywhere a license file name can be used (such as in a license search path). The actual text of the license file is specified with START_LICENSE\n as a prefix, and \nEND_LICENSE as suffix, where the embedded new lines are required. In the following license search path, the third component is a literal text string containing the actual feature definition line. ---------------------------------------------------------------------------------- setenv VENDOR_LICENSE_FILE file1: file2: START_LICENSE\n\ FEATURE f1 demo 1.0 permanent uncounted HOSTID=ANY \ VENDOR_STRING=\"Acme Inc\" SIGN=50A35101C0F3\n\ END_LICENSE ---------------------------------------------------------------------------------- The following example shows this usage in a call to the lc_set_attr function inside the application: ---------------------------------------------------------------------------------- lc_set_attr(job, LM_A_LICENSE_DEFAULT, (LM_A_VAL_TYPE) "START_LICENSE\n\ FEATURE f1 demo 1.0 permanent \ uncounted HOSTID=ANY \ VENDOR_STRING=\”Acme Inc\" SIGN=50A35101C0F3\n\ END_LICENSE”); ---------------------------------------------------------------------------------- If all users for a particular software publisher have the same license file, it is convenient to store it in a character buffer in the program, rather than in a license file, which would require the publisher to distribute an extra file that might get misplaced. For example, a library may be used to read a particular format file. If the file includes the name of the company that generated the data, a license can guarantee that only files generated by this company can be read by the library, by matching the name in the VENDOR_STRING=“...” field, (in conjunction with using lc_auth_data or LM_A_CHECKOUTFILTER).
View full article
Summary How do you limit a license server to only listen via a specific network card on a system with multiple NICs? Question Is there any way to tie a license server to a specific network card in terms of what the vendor daemon actually listens for license requests? For example, when running license servers that are multi-homed (e.g. multiple network cards) on a Linux system, you can see by running lsof -ni :port that lmgrd and the vendor daemon are both listening on all networks. Can FNP be configured to be only listening on the network card they are bound to by hostid? Answer By design, the license server is listening on IP address 0.0.0.0, meaning it listens for network traffic from all NICs. Listening on 0.0.0.0 is normal for server applications. These needs can be met by adding rules to disable traffic from specific NIC/Subnet in your firewall, or by adding some exclude IP/hostname via FNP's Options file to reject checkout request from part of your IP addresses or hostnames. There is no way in FNP to select a particular network card. I.e., it is not possible to have license server (lmgrd) to listen on a specific IP address instead of the 0.0.0.0. While you can?t bind the scope to the network card, what you're trying to do should work based on which interface the DHCP traffic is received on; as long as you have a scope defined that is correct for each interface. DHCP servers take into account the IP address of the interface on which the incoming request was received. In the case of relays the IP of the interface the relay received the request is included as part of the forward request. So if a computer receives a request on the interface 10.90.63.1/24 then it will assign an address from the 10.90.63.0/24 scope. So all you have to do is make sure the VLAN card associated with the license server has a static address assigned that is valid for that network, and then activate the scope.
View full article
Symptoms: The Flexnet Connect reports no longer produce an "Interactive graph" option.  Diagnosis: This is down to Adobe Flash Player being EOL from 31-Dec-2020, and is no longer supported in web browsers. Solution: The only option is generating data using XML (on Firefox ONLY). Other browsers do not seem to generate the XML data.    This can be done by selecting "Data (XML)" as the Output Type, as shown below...  
View full article
We have had customer inputs of 2 different types of format for VM_UUID being reported on EC2 instances.  This seems to be related to the decision taken by Amazon, where AWS was transitioning instance IDs and reservation IDs to a longer format. Link: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/resource-ids.html Prior to January 2016, the IDs assigned to newly created resources of certain resource types used 8 characters after the hyphen (for example, i-1a2b3c4d). From January 2016 to June 2018, we changed the IDs of these resource types to use 17 characters after the hyphen (for example, i-1234567890abcdef0). Only newly created resources receive longer IDs; existing resources are unaffected.
View full article
 To open a case, select "Get Support" and "Open New Case."    Open Case Form  You'll be directed to an online form with several fields. Please add as much detail as available to get the most out of the case. COMMUNITY   Our online community has two branches: Flexera Community and Revenera Community. Each host discussions, blogs and knowledge base articles for a different set of products. The selection defaults to the community you were on before opening a case so, in the majority of cases, you will be on the correct community selection. The below list details which products relate to which community. If you don't see your product in the picklist, please select the alternative option in the Community drop-down.  Flexera Community Revenera Community AdminStudio AdminStudio Inventory and Rationalization App Broker Brainware Cloud Management Columbus Data Platform Analyze Asset Inventory Cloud Asset Insights Discvoer Normalize Technopedia Flexera SaaS Manager Flexera Software App Portal FlexNet Manager Suite Cloud FlexNet Manager Suite On-Premises FlexNet Normalized Inventory Cloud FlexNet Normalized Inventory On-Premises Foundation/CloudScape Governance HealthCheck Optima  Self-Service Software Vulnerability Manager Software Vulnerability Research Spider Workflow Manager Workflow Manager for ELO FlexNet Manager Suite FlexNet Manager for Engineering Applications Saas Manager Compliance Intelligence Code Insight FlexNet Connect FlexNet Embedded FlexNet Operations FlexNet Operations Cloud FlexNet Publisher InstallAnywhere InstallShield Usage Intelligence   PRODUCT To optimize case routing, please select your product in this dropdown. If you don't see your product listed, please try changing the Community dropbox selection.   VERSION Version options will populate based upon which product you selected.   DESCRIPTION We recommend each description includes: What: What is specifically happening within the system. Please try to be as specific as possible with the exact area of the system, links you've clicked, etc. Who: The specific user or users first and last name who have reported this problem and/or who you have noticed this experiencing this problem. When: When the request/problem happens. For instance, did it start at a certain time of day or geographic location? What was being done prior to it occurring? How: Detail the steps to reproduce the error. When possible, include attachment videos or screenshots of the journey. Urgency & Business Impact: Help us understand the impact this issue is having on your business, including any pending deadlines. SEVERITY There are 4 severity levels used to classify a case: Severity 1 - Critical: Production use of the software is stopped or so severely impacted that authorized end users cannot reasonably use it. You must call-in by phone to notify our team, in addition to submitting the case. Severity 2 - High: Use of the software can continue; however, productivity is significantly decreased. Severity 3 - Medium: Major software documented features are unavailable, but a workaround is available, or less significant software documented features are unavailable with no reasonable workaround. Severity 4 - Low: An issue that involves an inquiry regarding a routine technical issue; information requested on application capabilities, navigation, installation or configuration. For Critical and High severity cases, an additional field will appear to collect details about the reason for the case urgency and its impact to your business. This information will help the Support team better prioritize your case. END CUSTOMER This is an optional text field our Partner users can use to track their affected client accounts.  ATTACHMENTS Attachments help expedite troubleshooting when they are available. Attached via drag and drop or browse files. You can always upload attachments after the case is submitted if needed.
View full article
If you'd like to see your order, product, and maintenance information navigate to the following pages on the community. Please note you will need to log into the community to access the pages mentioned below. Your order information is located under Get Support -> Recent Orders Your products appear under Get Support -> Registered Products Your maintenance details can be found under Get Support -> My Support Plans (Note: Maintenance information will no longer appear in the Product and License Center) If you'd like to see your licenses and the hosts or devices where you licenses are activated, please visit the Product and License Center. 
View full article
To access our content in the Learning Center: Sign-in Click on "Learning Center," located in the top navigation menu option "Other Resources" Click on the appropriate product tile Select the appropriate course tile Click the "Register" button For more information please visit the Access Product Training on the Revenera Learning Center video.
View full article
Here you will find some notable releases that appear in your Usage Intelligence reports.  January 2021 Core Analytics Added Cross-Product Reporting. Cross-Product Report provides insight into how many unique machines have installed products for a given date range that are part of product groups that you create. Up to three groups of products can be utilized in the creation of the report. Read More.  November 2020 General Under Product Management, the menu Item Event Tracking Whitelist Management was renamed to Event Tracking Management Under Event Tracking Management the selectable field Auto-Whitelist was renamed to Auto-Approve Client IP Blacklist was renamed to Blocked Client IPs Updated all nomenclature for Whitelist and Blacklist across the dashboard to use Approve/Block terminology. These changes affect Event Tracking Management, Licensing, Blocked Client IPs, and Delete & Block Clients. Core Analytics Added Data Retention Months and License Key Registry statistics to the Quota Usage Page. Added ability to view aggregate quota usage for products that are part of a quota pool. Added new functionality for string-based properties in report filtering: Support for filtering by regular expression Added ability to load filter values from a file Added ability to copy selected filter value to clipboard October 2020 General Updated user interface with the rebranding to Revenera Core Analytics  Added Group By functionality in distribution and Lifetime Event Usage reports, which gives you the ability to change the property used to identify an installation. Read More  September 2020 Core Analytics Added ability to switch data between installation count and % of active installations in distribution reports. Added cross-product data export, to be able to see the number of users making use of multiple products. August 2020 ReachOut Added Lifetime Event Count variables in ReachOut campaigns, to be able to send event usage counts to client installations. Updated automatic ReachOut campaigns delivery chart to show statistics for messages delivered vs messages that were clicked and interacted with by users. April 2019 Core Analytics User Flow Reporting The User Flow report provides you with a picture of the journey your users take when interacting with your product. By specifying a hotspot event, you can analyze everything that happens around it, how users reach that event, and which steps they take following it. Read More December 2018 Core Analytics Export Property Values Users can select any property (as visible in the filters list), including Custom Properties and it will generate a full list of metadata for a particular property. Available as a JSON or plain text file. Read More Support for multiple billing email addresses Users can now add multiple email addresses as their billing contacts, who would each receive a copy of any invoices or billing notifications. Data table export for Lifetime Event Tracking and Churn Lifetime Event usage Users can now export a JSON file with all the data in the Event Usage tables. IP Blacklist Users can add a list of IPs or IP ranges that will be blocked from the server. These can be used to block internal users from submitting data to the RUI server (say during QA) or to block any unwanted users or domains. Read More ReachOut ReachOut Archiving Users can move any ReachOut campaign from the “Active” tab to an archive. This is especially useful for users having a large list of ReachOut messages that they do not want to permanently delete. All archived campaigns are accessible from the “Archived” tab inside the ReachOut page. An archived campaign is automatically disabled but stored for historical or reporting purposes. It can be made “Active” again at any point or can still be used to clone new campaigns from it. Read More ReachOut ID display Users can see the unique ReachOut Campaign ID displayed in each of the ReachOut tables. This helps for reporting purposes and referencing with raw data exports or Client Profile data, all of which show the ReachOut IDs that a client has been delivered. November 2018 Core Analytics Client Profile Report Users have the ability to drill down into product usage data for a particular client, look at data for sets of ClientIDs that match specific criteria, and do full exports of the data by ClientID for further analysis, joining with third-party data sets, or historical archiving of all your usage data. Capabilities include: Export data for further analysis in third-party analytics systems View all ReachOut in-application campaigns that any client has received Identify specific ClientIDs of user segments by properties and usage Manage GDPR requests for data access Download data for archiving Use JSON format of data exports for maximum portability Read More Raw Data Export Users can collect, upon request, all the raw data from their application in addition to the standard data collected and processed by Usage Intelligence. This needs to be configured with an account manager to be enabled and collect the data specific to each user case. Read More August 2018 Helpdesk Knowledgebase and ticketing system updated for enhanced searchability, ticket tracking and user experience. View Support Center June 2018 Core Analytics Virtual Machine Architecture Report Users can now report and analyze installations running on Virtual Machines across Windows, Mac, and Linux platforms. It also allows other reports to be filtered by usage on specific Virtual Machines only with installations running for deeper analytics. Read More Sunburst Visualizations in Usage Intelligence The new Sunburst diagram lets you illustrate and analyze hierarchical or segmented data through an interactive Sunburst chart with drilldown functionality. You can visualize three properties and click on any segment to drill down into it and explore the relationships. March 2018 Core Analytics Support for Facebook login discontinued Due to the lack of usage, account creation, and login via Facebook is no longer supported by Usage Intelligence. Null Value Reporting Reports now support <NULL> values (where no information is collected) and users can choose to include or not include these values in their reporting and visualizations. This distinction provides greater insight into total usage numbers. Read More Export Data to CSV In addition to image formats, table data and timeline data can now be exported by users in a CSV format for any report in Usage Intelligence. ReachOut Clone ReachOut Campaigns Users can now create copies or clones of their existing campaigns to repurpose in launching new campaigns to different audiences or with other modifications. Filter ReachOut Recipients by Previous Campaigns In-application messages can now be targeted to users based on whether or not they have received other messages previously via ReachOut. This allows for a message series to be created via sequenced messages. February 2018 Core Analytics Regular Expressions (“Regex”) Added All filters for reporting and ReachOut now take advantage of regular expressions to provide greater flexibility and time savings. From the Filters UI you can choose “Exact Match,” “Starts with” or “Contains” to filter any string property. Like other filters, Regex-based filters can also be saved as templates and shared with your team. Lifetime Event Usage Filter This powerful addition allows you to ask and get answers to more complicated questions by filtering any report or ReachOut campaign based on the user’s actual usage of the product functionality. For example, how many users have launched the configuration wizard at least once, but never finished the wizard completely? Or, how many users used the product for at least 10 hours but have not yet discovered Feature X? Or, how many users who have used heavily Feature X but made little to no use of Feature Y. Date Installed Filter This new filter enables you to report on usage by people who installed during a specific time period (for example, during a campaign or following an event). You can easily see how many users who installed during the Q4 promo that are still active today and what are they doing with the software. You can also run churn analysis reports only on those users who installed before a specific time period. Date Last Seen Filter This enhancement allows you to filter in/out users that were last seen before or after a specific date. For example, you might want to run a report of how many users abandoned a specific version/edition of your software in the days after you announced that you will be terminating its support. When used in combination with the Date Installed Filter, you can get more accurate data on product and feature usage by filtering out anyone who was not fully active during the whole reporting period (e.g., the average runtime and feature usage metrics will not include users who installed or uninstalled the product in the middle of that reported date range). Reachout ReachOut Delivery Caps If you want to send a promotion to a limited number of users, send upgrade notifications in batches, or run A/B testing with a random user sample, you can now easily achieve this by setting a Maximum Delivery Cap on any ReachOut campaign to limit the number of messages delivered. December 2017 Core Analytics Java SDK Released Usage Intelligence adds a software usage analytics solution designed for distributed native Java applications on Windows, Macintosh, and Linux. Read More Reporting Filters Added Filtering for specific Usage Intelligence Client ID and Machine ID for customers also using Revenera Compliance Intelligence, providing deeper insight into feature usage within unlicensed software to accelerate settlement and conversion discussions Opt-In/Opt-Out Status, making it easier to calculate sample size and measure the effectiveness of software usage analytics programs Lifetime Product & Feature Usage, providing deeper insight into specific user groups and their engagement with various product functionality October 2017 Core Analytics Updates to User Permission Controls Users can now easily manage user permissions for their entire team. Admins can grant Full, Read-Only, or Deny access for different aspects of Usage Intelligence from User Management, Reporting, ReachOut, Developer, License Key Management or Filtering, Quota Usage, Billing and Subscription, or Reporting API access. For each user, you can quickly preview all their access levels, edit their permissions, clone them for other users that have the same organizational role or revoke their permissions.    
View full article
This is a known design limitation for Flexnet Publisher where the connecting clients checkout a new set of licenses. Conventionally, for a client to establish connection with Server over TCP IP, a socket is created at server and client for further communication. Now, once client detects that it has been disconnected from server/the connection signature changes (bad network OR change in network), client will close the existing connection (due to security reasons) and establish a new one. This new socket connection will lead to checkout another set of license, if DUP_GROUP is not the conventional implementation in producer's environment. To avoid a license deadlock/shortage scenarios, the licensing administrator can always take help of options file keyword, TIMEOUT, which will automatically check-in the licenses after certain period (same as defined in options file) and help avoiding license shortage scenarios. Please be advised that in future releases some redesiginning (post FNP_11.18) is in consideration with engineering, but we have no visibility on how this behaviour can be mitigated, except the above proposed workaround - at this point of time. Additional KB on this: https://community.flexera.com/t5/FlexNet-Publisher-Knowledge-Base/Additional-license-consumed-on-client-reconnection-post/ta-p/133491  
View full article
Symptoms: Files are not showing under downloads in the End User Portal although there are valid files, download packages, and entitlements. Diagnosis: When a user clicks on Downloads in End User Portal he gets a message "There are currently no files defined for your account" as per the below screenshot. On investigation of entitlement, files, and Download packages it was found that all of them were fine. But there was a problem with the account ID which had German umlaut character ä, á  in it, and because of that, the account ID was not getting parsed at ESD. This bug is currently being looked into by our internal teams.   Solution: Please make sure to avoid keeping characters like  ä, á to avoid this type of issue until we fix the bug from our end.
View full article
Starting FNP-11.17.2, Windows 8.1 is no more a tested and supported platform. After careful consideration this decision was taken. That's the reason, Windows 8.1 has also not been mentioned under the testing platform in release notes of V11.17.2 to convey the same.
View full article
In the last article of this 3 part series, we will look at the license key management capabilities offered by Usage Intelligence. In addition to Software Analytics, Usage Intelligence provides a License Key Usage Tracking and Piracy Monitoring Service. This functionality is embedded as part of the Analytics SDK and allows you to validate keys on the client, track which license keys are in use as well as to detect and report abused keys. Please check out this blog post for a high-level overview of what is included with this service. SDK Integration - Getting Started with Usage Intelligence - Part 1 Event Tracking - Getting Started with Usage Intelligence - Part 2 Software License Usage Tracking - Getting Started with Usage Intelligence - Part 3 There are two modes of licensing management available, Client or Server managed (both explained later).  Each mode can be configured from the License Key Registry page as follows: Log in to the Usage Intelligence Dashboard, go to the Administration page, and under Product Settings click on License Key Registry Click on the Settings tab   Select the licensing management mode for each flag and click Save. By default, the licensing management is set to Client Managed. You may choose to have a mix of Client and Server managed for the license flags, for example, you might want to handle activation on the client-side while managing the rest on the server. Read on for more information on the different modes and when to use them. 1. Client Managed In this mode, your application notifies the server when the license status has changed, and the licensing mechanism is used for reporting purposes only. It is generally used when you already have a licensing management system in place that can identify whether a license key is valid, expired, blocked, etc. In the example below, we are notifying Usage Intelligence of a new license status when the user changes the license key in the application by using the SetLicenseData method. Note that the license key is not collected when using this method, but only the status flags are registered for reporting. Open the class where you handle the licensing key change At the top of the file add the directive using RUISDK_<x_x_x>; where x_x_x is the SDK version you downloaded, e.g. 5_0_0 Add the following code when the user enters a new key. In this example we are using the Click event of the Save button: private void btnSave_Click( object sender, EventArgs e) { //rui is your RUISDK instance rui.SetLicenseData(keyType: ( int ) RUILicenseKeyType .purchased, keyExpired: 0, keyActivated: 1, keyBlocked: 0, keyAllowed: 0); //The rest of your code… } The SetLicenseData() function has 5 required parameters: Key Type – A value from the RUILicenseKeyType enum representing the type of key Key Expired – An integer representing whether the license key is expired (1), not expired (0) or unchanged (-1) Key Activated - An integer representing whether the license key is activated (1), not activated (0) or unchanged (-1) Key Blocked – An integer representing whether the license key is blocked (1), not blocked (0) or unchanged (-1) Key Allowed – An integer representing whether the license key is allowed (1), not allowed (0) or unchanged (-1) Any license flags which do not apply to your license model can be set to -1. This function also accepts an optional string parameter for the session ID. In our example, we did not specify this value since our calculator application does not manage sessions itself. Build your solution, run the application, set the license data, and close the application From the Usage Intelligence Product Dashboard go to Product Metrics > Licenses in Use and License Status to view the licensing reports.   2. Server Managed In this mode, license keys are collected/stored on the Revulytics server and you can use the SDK to check the real-time status of a license key from within your application. In this mode, the Usage Intelligence server also keeps a count of the number of installations that are sharing each license key. This will enable you to sync with your CRM or licensing service to detect piracy or license key abuse. This mode is also ideal if you do not have a license key verification system in place already. Uploading keys from your CRM: To use Server Managed licensing you will need to submit your license keys and any information about these keys to the License Key Registry. You can do this by entering/editing license keys manually or through the Web API.  More info on using the Web API can be found in the documentation. You can view or manage the license keys that are available on the server by going to the dashboard, navigating to the Administration page and under Product Settings click on License Key Registry.     Once the license keys are in the registry, you are now ready to register and validate keys from your application. Validating a Key from the Client The following example uses the CheckLicenseKey method to retrieve the license key information from the server. Open the class where you handle the licensing key check At the top of the file add the directive using RUISDK_<x_x_x>; where x_x_x is the SDK version you downloaded, e.g. 5_6_0 Add the following code when the user enters a new key. In this example we are using the Click event of the Submit button: private void btnSubmit_Click( object sender, EventArgs e) { List < int > licenseResult; //rui is your RUISDK instance RUIResult result = rui.CheckLicenseKey(txtKey.Text, out licenseResult); //The rest of your code… } The CheckLicenseKey() function has 2 required parameters, a string which is the license key you would like to validate, and a List<int> which will be filled with the returned result and will contain the following properties: Key Type – A value from the RUILicenseKeyType enum representing the key type (Evaluation, Purchased, Freeware, etc..) The license key flags with a value of 0 if false, 1 if true, and -1 if unknown: License Expired License Activated License Blocked License Allowed If the key does not exist on the server, all the status flags will be returned with a value of -1 If a status flag is set to Client managed, the returned value for that specific flag will always be -1 Registering a Key from the Client Registering a key is similar to validating a key, however, you need to use the SetLicenseKey method. Open the class where you handle the licensing key change At the top of the file add the directive using RUISDK_<x_x_x>; where x_x_x is the SDK version you downloaded, e.g. 5_0_0 Add the following code when the user enters a new key. In this example we are using the Click event of the Save button: private void btnSubmit_Click( object sender, EventArgs e) { List< int > licenseResult; //rui is your RUISDK instance RUIResult result = rui.SetLicenseKey(txtKey.Text, out licenseResult); //The rest of your code… } When a status flag is set to Client Managed, the returned value for that specific flag will always be -1. If the key does not exist on the server, it will return the license type as Unknown while the rest of the status flags will have a value of 0. The key will also be added to the License Key Registry and this makes it easy for you to track illegitimate keys by searching for Auto Collected keys with an Unknown type. To do this go to the Usage Intelligence Product Dashboard, navigate to Manage Product > License Key Registry and click on the Show Advanced Key Search. Once on the License Key Registry page click on the Filters tab, add your filters and click on the Apply Filter button.   This brings the Getting Started series of posts to an end. We recommend you review the full documentation available in the Developer Zone to benefit from the advanced features provided by the Usage Intelligence SDK. If you require any further assistance, contact us at our helpdesk and we would be happy to help!
View full article
Symptoms: After turning on HTTPS connection in FlexNet License Server Manager(FLSM) and trying to access the Devices or Reservations tab from the menu, the screen shows error : "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException".   Diagnosis: The given error suggests that Java does not trust the certificate hence FLSM fails to connect to the server application (Local License Server).   Solution:  To resolve this, add the server side certificate to the Java truststore on the system where FLSM application is running. Below is the sample command that will help to add the required certificate to Java truststore: =>Export alias certificate from the keystore keytool -export -alias [alias_name] -keystore keystore.jks -rfc -file server_cert.certs =>Import certificate to the java trust store on which application is running. keytool -import -trustcacerts -keystore [java_path]/lib/security/cacerts -storepass [password] -alias [alias_name] -import -file server_cert.certs   Once the required certificate is imported to the Java truststore, https connection should be successful to the Local License Server from FLSM application.    
View full article
Symptoms: Webservice example of how to disassociate a User who is part of multiple Accounts   Diagnosis: How to programmatically disassociate a User from an Account   Solution: Use the UserAcctHierarchyService?wsdl  Import the UserAcctHierarchyService?wsdl to ie. SmartBear SoapUI or Postman Depending on your tenant, here would be an example of the endpoint: https://tenant.flexnetoperations.com/flexnet/services/v3/UserAcctHierarchyService?wsdl Recommend using the latest version of the wsdl that is available To see what versions are available use the base url endpoint: https://tenant.flexnetoperations.com/flexnet/services Execute the updateUser method Sample Request: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:v3.webservices.operations.flexnet.com"> <soapenv:Header/> <soapenv:Body> <urn:updateUserRequest> <!--1 or more repetitions:--> <urn:userData> <urn:user> <urn:primaryKeys> <urn:firstName>FirstName</urn:firstName> <urn:lastName>LastName</urn:lastName> <urn:emailAddress>EmailAddress</urn:emailAddress> </urn:primaryKeys> </urn:user> <urn:primaryKeys> <urn:id>Account</urn:id> </urn:primaryKeys> </urn:account> </urn:acctRoles> <urn:opType>DELETE</urn:opType> </urn:acctRolesList> </urn:userData> </urn:updateUserRequest> </soapenv:Body> </soapenv:Envelope>   Sample Response: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soapenv:Body> <updateUserResponse xmlns="urn:v3.webservices.operations.flexnet.com"> <statusInfo> <status>SUCCESS</status> </statusInfo> </updateUserResponse> </soapenv:Body> </soapenv:Envelope>      
View full article
Symptoms:  How to change the default location of trusted storage via the CapabilityRequest.c example for the Windows Platform and the Linux-Based Platform   Diagnosis:  Here is the original Default location example:   if (!FlcLicensingCreate( &licensing, identity_data, sizeof(identity_data), GetStoragePath(tsPath, sizeof(tsPath)) ? tsPath : NULL, "1234567890", error))   Solution: Adjustments based on the OS platform   Windows:  if (!FlcLicensingCreate( &licensing, identity_data, sizeof(identity_data), "C:\\temp\\", "1234567890", error))   Linux-Based:  if (!FlcLicensingCreate( &licensing, identity_data, sizeof(identity_data), "/var/opt/flexnetls/ClientTrustedStorage/", "1234567890", error))
View full article
Description A small number of customers have observed issues where files are not available for download. A possible cause of this is FlexNet Operations’ use of the Akamai NetStorage to facilitate the Electronic Software Delivery (ESD) functionality. In the newer version of Akamai NetStorage, a hard file size limit of 150GB is being enforced and prevents files greater than this size from being available for download. If the file fails to be available for download, please check that the file does not exceed the file size limit.  Workaround There is no workaround that will allow supporting a single file greater than 150 GBs. Users can instead break up the file into multiple files that do not exceed the file size limit. Resolution This is expected behavior for the Akamai solution. Revenera is looking into new options to add non-Akamai files storage but retaining their Content Delivery framework. 
View full article
The Cross-Product Report provides insight into how many unique machines have installed products for a given date range that are part of product groups that you create.
View full article
The binding elements for the trusted storage based licensing (for one's implementation) can be gathered from "<vendor>TrustedConfigIn.xml" file. This is a publisher side file, that can be located under platform Dir\publisher\<vendor_name>TrustedConfigIn.xml It looks like this: </TransactionKeyInfo> <Server> <Anchoring> </Anchoring> <Binding> <Platform> <Type>DEFAULT</Type> </Platform> </Binding> </Server> <Client> <Anchoring> </Anchoring> <Binding> <Platform> <Type>DEFAULT</Type> In regards of the Deal breaker scenarios for TS breakage, there is a detailed Table (A-24) explained in the "FlexNet Publisher Programming Reference for Trusted Storage–Based Licensing", under Appendix A.       The default for FLEXIBLE binding is to use all the built-in bindings that are available on an operating system. The list of those binding elements can be referred from the same document location (chapter/Appendix) as in my previous communication. However, users who are not using FlexNet Operations can specify the <Disable> or <Enable> element along with <HID> to identify explicitly which binding identities to use or not to use for a given operating system. Also, FlexNet Publisher automatically uses the appropriate binding elements when running in a virtual environment, if they are available. Binding is to differentiate between physical and virtual environments and the legacy bind-to-VMID policy is deprecated. The binding elements are (for virtualization based environment): • MAC address—used on physical environments is now used in virtual environments as well and is a deal breaker. • UUID (universally unique ID)—A binding identity used to configure trusted storage on the virtual machine, previously the only binding identity used in virtual environments; this is now a deal breaker. • Generation ID—A property of a virtual machine available in some environments. Where it is available it is used as a binding identity; it is a deal breaker. A binding item is a deal breaker if/when it changes, trust should be lost regardless of the number of binding items that still match. Since all binding identities used in virtual environments are deal breakers, trust will always be lost if any of them changes.  
View full article
Cause: The below record (with Assembly name) is missing for "RemoveSSLBinding" custom action in ISClWrap table. All other custom actions have this record. The record mentioned above for that particular custom action was deleted accidentally by editing the table or by performing some other action in the UI. Solution: Change 'Run 64-bit PowerShell script' value to No and again back to Yes to get the missing record back. This will fix the warning during the build. The logic behind embedding required resources\assemblies for managed custom actions is based on Assembly attribute. In order to optimize the space, InstallShield collects and groups the required assemblies for all custom actions and embeds the required assembly only once. In this case, Assembly attribute is missing for this particular custom action, hence the empty value was assumed and the warning was shown.
View full article
Issue Description Remaining linger time in lmstat displays wrong value whenever license server is restarted. After license server restarts, remaining linger time is reset to total linger time . Example 1. Start the license server. 2. Set borrow period e.g. for next 10 mins. lmborrow qavend8 1-apr-2015 11:50 3. Check out license "abcd" and observe feature "abcd" is in linger state. 4. Observe remaining linger duration and total linger time (linger: 476 / 480) in lmstat. Users of abcd: (Total of 4 licenses issued; Total of 1 license in use) "abcd" v1.0, vendor: qavend8, expiry: 1-jan-0 floating license P7106943 BLR-P7106943 BLR-P7106943 (v1.0) (BLR-P7106943/27008 101), start Wed 4/1 11:41 (linger: 476 / 480) 5. Wait for 1 or 2 mins 6. Again Observe remaining linger duration and total linger time (linger: 402 / 480) in lmstat. After few seconds of borrowing, remaining linger duration is reduced to 402 seconds. Users of abcd: (Total of 4 licenses issued; Total of 1 license in use) "abcd" v1.0, vendor: qavend8, expiry: 1-jan-0 floating license P7106943 BLR-P7106943 BLR-P7106943 (v1.0) (BLR-P7106943/27008 101), start Wed 4/1 11:41 (linger: 402 / 480) 7. Shutdown the license server with force option lmdown -c counted.lic -force 8. Restart the license server. 9. Observe remaining linger duration and total linger time in lmstat. Observed result: Remaining linger duration is reset to total linger time (linger: 474 / 480)as shown below. Users of abcd: (Total of 4 licenses issued; Total of 1 license in use) "abcd" v1.0, vendor: qavend8, expiry: 1-jan-0 floating license P7106943 BLR-P7106943 BLR-P7106943 (v1.0) (BLR-P7106943/27008 101), start Wed 4/1 11:43 (linger: 474 / 480) Expected result Remaining linger duration in lmstat should show correct remaining time whenever lmgrd is restarted. It should not be reset to total linger time.    Note: This issue is part of the roadmap with no planned release date yet.(FNP-24333)
View full article