Revenera Community Knowledge Base

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Knowledge Base Articles
Dashboard Reports By default, reports use the Client ID property as an identifier for an installation / user. This may be changed in some reports to use a different property as the identifier. When doing so, multiple installations sharing the same value of the selected property will be grouped as a single installation. For example, if I choose to group by the License Key property, two installations using the same license key will be counted as one installation in the reports. To change the identifier property, click on the “Group By” tab in the report toolbar, and select a property from the list.  The properties available for grouping are: Client ID (default) Machine ID License Key Custom properties of type 3 If an installation does not have a value set for the selected identifier property, that installation will not be included in the report.  NOTE: The Machine ID property was introduced in version 5 of the Usage Intelligence SDK. When grouping by Machine ID, clients using an older version of the SDK will therefore not be included in the report. The following is a list of reports that support the 'Group By' functionality: Distribution Reports Product Metrics OS & Platform Hardware Architecture Java Environment Geography Lifetime Event Usage Custom Report Builder Custom Timeline Builder Revenera Web API The following is a list of reports that support the 'Group By' option. More information on the request and response format is available in the Web API online documentation. Generic Current Report Generic Date-Range Report Lifetime Event Tracking Reports Related Articles How does Usage Intelligence identify unique users/installations? What type of data can I store in Custom Properties?
View full article
Error Trusted config procesing failed : 'publisher\VendornameTrustedConfigOut.xml : PublisherId in trusted config does not match that in activation setting. XML FATAL ERROR: parsing aborted at line 4 XML parse of configuration file failed. NMAKE : fatal error U1077: '.\preptool.exe' : return code '0x1' Stop. Description This error could occur while building the Toolkit for Trusted Storage when there is a mismatch in the Publisher ID . Solution 1.Go inside the platform_directory/publisher/VendornameTrustedConfigOut.xml Edit the publisher ID as per the vendor being used ,each vendor has their unique publisher ID while building for Trusted Storage. 2.Go inside platform_directory/ActivationSettings/publisher.xml ,compare the publisher ID with the publisher ID in Step 1. Both the ID's should be same. 3.Save the file and build the toolkit again by using nmake -f makefile.act clean 
View full article
In Producer Portal, the attribute Download Package Availability is determined by the Effective Date defined for the download package. - If the effective date is within the current date, for example, today's date and any date in the past, then the download package is available. This setting can be used for any current versions of the Product that the customer want their end users to download. - If the effective date is in the future, for example, tomorrow, or next month (in PDT), then the download package is not "yet" available.  This setting can be used for any future versions of a Product (that are not yet released or made available for end users) Once this date passes, the download package will become available. - If the expiration date is in the past, then the download package is Archived. This is for previous versions of a Product. This setting can be used to archive previous versions of the Product. Users can still access all these download packages in the Producer Portal and view the files associated with the download packages. The attribute is more to determine what will be displayed in the end user portal, if each of these different download packages have a valid entitlement. -->Download Packages that are available will be displayed in the New Versions tab in the end user portal. -->Download Packages that are archived will be displayed in the Previous Versions tab in the end user portal. -->Download Packages that are not yet available will not be displayed in the end user portal, even with a valid entitlement.
View full article
Overview of Transfer Split functionality in LLM can found in this article . Property to be set for the below mentioned scenario 1: i)TransferSplitEnabled = True ii)TransferSplitEnabled.TransferOrderActivationCodeToTarget = false   1)Entitlement Details: Entitle the Source Account (View Account -> Entitle -> Entitle Account). Create order line in PP as shown below.     2)Allocation before Transfer: Check for the Activation Code under Allocations (View Entitlement -> View Allocations). We see that the Allocation is on account YT_SA7 for all the line items.       3) Create Target Account :     4) Create new Device and map full quantity from line 1 and partial quantity from line 2, generate the response.     5) Create new Server and map full qty from line 3 and partial qty from line 4, don't generate the response     6)Transfer the Order: We see that allocations are moved from YT_SA7 to YT_TA7. Activation Code changes due to the property mentioned in ii)     7) After Transfer of Entitlements, we see that the Device which was under YT_SA7 is under YT_TA7(Target Account) The device should be moved to the target account The device should have the licenses with different Activation Codes due to property ii) on it after the transfer       8 ) After Transfer of Entitlements, we see that the Server which was under YT_SA7 is under YT_TA7(Target Account) The Server should be moved to the target account The Server should have the licenses with different Activation Codes due to property ii) on it after the transfer             9) To confirm the certificates are right generate the license on the server after the transfer order, and make sure the license gets generated.     Scenario 2 is mentioned here  .      
View full article
Overview of Transfer Split functionality in LLM can found in this article . Scenario One is mentioned here .   Property to be set for the below mentioned scenario 2: i)TransferSplitEnabled = True ii)TransferSplitEnabled.TransferOrderActivationCodeToTarget = True   1)Entitlement Details: Entitle the Source Account (View Account -> Entitle -> Entitle Account). Create order lines in PP as shown below.     2)Allocation before Transfer: Check for the Activation Code under Allocations (View Entitlement -> View Allocations). We see that the Allocation is on account YT_SA7 for all the line items.     3) Create Target Account:   4) Create new Device and map full quantity from line 1 and partial quantity from line 2, generate the response.     5) Create new Server and map full qty from line 3 and partial qty from line 4, don't generate the response   6)Transfer the Order: We see that allocations are moved from YT_SA7 to YT_TA7. Activation Code remains the same due to the property mentioned in ii)     7) After Transfer of Entitlements, we see that the Device which was under YT_SA7 is under YT_TA7(Target Account) The device should be moved to the target account The device should still have the same licenses on it after the transfer       😎 After Transfer of Entitlements, we see that the Server which was under YT_SA7 is under YT_TA7(Target Account) The Server should be moved to the target account The Server should still have the same licenses on it after the transfer           9) To confirm the certificates are right generate the license on the server after the transfer order, and make sure the license gets generated.        
View full article
Seen below is a sample of  modified lsvendor.c that contains a server side checkout filter. It uses a flag that will detect if the license that is being checked out is from the Server Trusted Storage or a License file and will deny/allow accordingly.   int TS_License_out() { char* feature; CONFIG * conf; ls_get_attr(LS_ATTR_FEATURE, &feature); ls_log_asc_printf("outfilter check out for lic file\n"); conf = lc_get_config(lm_job, feature); printf("license type is %d\n", conf->nTSFeatFlag); //Check if license is TS or Lic file if (conf->nTSFeatFlag > 0) { ls_log_asc_printf("Allow Checkout"); // Allow if > 0(TS) return (1); } else { ls_log_asc_printf("Deny Checkout"); // Deny if 0 (Lic File) lc_set_errno(lm_job, -53); return(0); } }
View full article
Latest Update: The planned enhancement has been implemented and all issues have been resolved. This scheduled maintenance is now complete. Thank you for your patience while we worked to improve our customer support experience.  Update Post ( Oct 19, 2020   02:19 PM 😞 We are scheduling another maintenance to address the original case portal issues encountered during the maintenance that occurred on October 13th. The new maintenance is scheduled for Tuesday, October 20th at 6AM PDT. In addition to fixing the enhancement that adds case severity notes, we are also addressing the case portal flooding issue.  We appreciate your continued patience as we work to restore stability to our case portal. Update Post ( Oct 15, 2020   02:19 PM) :  We've encountered an issue as part of this maintenance, and efforts to fix the issue are on-going. There is no impact to existing community functionality. We will provide another update once the maintenance is complete. We appreciate your continued patience. Original Post ( Oct 13, 2020   03:23 PM) A maintenance event is scheduled for October 15th at 6AM PDT and is expected to take approximately 30 minutes. No outage is required, and all community functionality will remain operable during the maintenance. This maintenance adds a new field to the 'Open New Case' form when 'Critical' or 'High' severity levels are selected. The new field enables customers to provide additional information about their severity level selection, and assists our Technical Support team to make insightful case handling decisions. This information will be included in the case comments for reference. If you encounter issues with your ability to submit cases after this maintenance, please notify our Support team by   phone for assistance. Thank you, Your Revenera Community Team  
View full article
  This article covers how to build the InstallShield projects in Azure DevOps pipelines by using the InstallShield Azure DevOps Build Extension. Prerequisite Add and install the InstallShield Build Extension to your Azure DevOps organization where you are going to build the InstallShield projects as part of the Azure Build Pipeline. Add InstallShield tasks to your Azure DevOps Pipeline. Once you have installed the Extension to your organization, Install InstallShield SAB and InstallShield Build tasks will be available to your Build Pipeline tasks, to configure and build the InstallShield projects stored in the repository. InstallShield Build Extension Tasks: 1. Install InstallShield SAB Task The Install InstallShield SAB task installs the InstallShield Standalone Build setup on the Microsoft hosted machine, based on the InstallShield version configured in the task, and configures the license server with the license server details provided in the task. Provide the InstallShield License server details in the server:port format, where, server is the IP address or the fully qualified domain name on which an InstallShield License Server is running. port is the InstallShield License server port configured during the License server installation. Ensure the License server machine is configured to communicate from the Microsoft Hosted Agent, by exempting the License server ports from the firewall. The License server and Vendor daemon ports need to be configured to communicate from the Microsoft Hosted Agent via Firewall. If multiple ‘Install InstallShield SAB’ tasks are configured for a particular InstallShield version in the same pipeline, only the first task downloads and installs the Install InstallShield SAB and the second task checks if it is already installed or not and skips the download and install if it is already installed. ‘Install InstallShield SAB’ task is intended to install on Microsoft Hosted Agents. If configured on Self Hosted agents, then it installs but it is more appropriate to configure the existing on-premises InstallShield machine as Self Hosted agent. The Install InstallShield SAB task can be added to the Pipeline with one of the following editors: YAML Pipeline Editor Classic Pipeline Editor   1.    Adding Install InstallShield SAB Task in the YAML Pipeline Editor   - task: InstallShieldInstall@1   inputs:     ISVersion: '2020'     ISLicenseServerPort: '102.203.205.198:27000'   ISLicenseServerPort: Provide in the server:port format, where the server is server is the IP address or the fully qualified domain name on which an InstallShield License Server is running, and the port is the License server port configured during the License server installation. License server and Vendor daemon ports need to be configured to communicate from the Microsoft Hosted Agent via Firewall. ISVersion: Specify the InstallShield version that needs to be installed on the hosted agent. Example: '2020' to install InstallShield 2020 SAB setup.   2.    Adding Install InstallShield SAB Task in the Classic Pipeline Editor   Provide the InstallShield Version from the drop down, and License Server and Port in the server:port format as described in the previous section.     2. InstallShield Build Task InstallShield Build task can be configured to build the InstallShield projects as part of the Azure DevOps build pipeline. This task checks if the InstallShield SAB is installed on the agent, and installs the InstallShield SAB if not already installed before triggering the InstallShield project build. Choose ‘Hosted Agent’ or ‘Private Agent’ depending on where your pipeline is running. “Hosted Agent” option in the InstallShield Build Task configuration to build the InstallShield project in the Microsoft Hosted Agent. “Private Agent” option in the InstallShield Build Task configuration to build the InstallShield project in the Self Hosted Agent.   InstallShield Build task requires following inputs for its execution: InstallShield project path from the root of the repository location. Command line parameters, if any. Agent Location, ‘Hosted Agent’ or ‘Private Agent’ depending on where your pipeline is running. InstallShield installed location on the Local Agent if the build configured with Self Hosted Private Agent. License Server details in the server:port format, in case of Microsoft Hosted Agents. InstallShield versions in case of Microsoft Hosted Agents. Building with Microsoft Hosted Agents: To build the InstallShield project on the Microsoft Hosted Agents, you need to configure the Agent Location to “Hosted Agent” option, InstallShield version and the License server details in the InstallShield Build task. So, during the task execution, InstallShield SAB build is downloaded, installed and configured with the license server specified Provide the InstallShield License server details in the server:port format, where, server is the IP address or the fully qualified domain name on which an InstallShield License Server is running. port is the InstallShield License server port configured during the License server installation. Ensure the License server machine is configured to communicate from the Microsoft Hosted Agent, by exempting the License server ports from the firewall. The License server and Vendor daemon ports need to be configured to communicate from the Microsoft Hosted Agent via Firewall. Once after configuring the InstallShield Standalone setup on the Microsoft Hosted Agent, InstallShield Build task starts building the InstallShield project and the build progress will be updated in the agent job log. In case the Build pipeline requires to build multiple InstallShield projects, then multiple InstallShield Build tasks can be configured with the corresponding InstallShield project details. However, the download and install the InstallShield setup on the agent has been performed at the first task, after that it starts building the project directly.   The InstallShield Build task can be added to the build Pipeline with one of the following Pipeline editors: YAML Pipeline Editor Classic Pipeline Editor 1.    InstallShield Build Task in the YAML Pipeline to build in Microsoft Hosted Agent:   - task: InstallShieldBuild@1   inputs:     Prjname: 'TestMSI.ism'     Parameters: '-v'     AgentLoc: 'HostedAgent'     ISLicenseServerPort: '105.211.241.103:2700'     ISVersion: '2020'   Prjname: It is the path of the InstallShield project from the repository root. Parameters: Add the detail, if any additional command line parameters need to be passed during the build. It is optional. AgentLoc: Specify the type of Agent where the Azure Build is configured. The ‘HostedAgent’ for Microsoft Hosted Agent, and ‘PrivateAgent’ for Self-Hosted Agent. ISLicenseServerPort: Provide in the server:port format, where the server is server is the IP address or the fully qualified domain name on which an InstallShield License Server is running, and the port is the License server port configured during the License server installation. License server and Vendor daemon ports need to be configured to communicate from the Microsoft Hosted Agent via Firewall. ISVersion: Specify the InstallShield version that is to be installed on the hosted agent. Example: '2020' to install InstallShield 2020 SAB setup. 2.    InstallShield Build Task in the Classic Pipeline to build in Microsoft Hosted Agent   Provide the InstallShield Project Path, Parameters (if any), Agent Location, InstallShield Version, and License Server and Port in the server:port format.     Building InstallShield Project with Self Hosted Agent To build InstallShield projects on the Self Hosted Agents, we/you need to configure the Agent Location to “Private Agent” option, and the absolute location where the InstallShield is installed on the agent. We/you provide the full absolute path of InstallShield installed Location on the local agent. Ex: C:\Program Files (x86)\InstallShield\2020 or C:\Program Files (x86)\InstallShield\2020 SAB. Ensure the local agent is preconfigured with InstallShield and the license activated for the successful builds from the Azure pipeline. InstallShield Build task builds the InstallShield project with InstallShield installed on the local agent, and the build progress will be updated in the agent job log. The InstallShield task can be added to the build Pipeline with one of the following editors: YAML Pipeline Editor Classic Pipeline Editor 1.    InstallShield Build Task in the YAML Pipeline Editor to build in the Self Hosted Agent:   - task: InstallShieldBuild@1   inputs:     Prjname: 'TestMSI.ism'     Parameters: '-v'     AgentLoc: 'PrivateAgent'     SABPath: 'C:\Program Files (x86)\InstallShield\2020 SAB' Prjname: It is the path of the InstallShield project from the repository root. Parameters: Add the details, if any additional command line parameters need to be passed during the build. It is optional. AgentLoc: Specify the type of Agent where the Azure Build is configured. ‘HostedAgent’ for Microsoft Hosted Agent, and ‘PrivateAgent’ for Self -Hosted Agent. SABPath: Provide the full absolute path of InstallShield installed Location on the local agent. For example, C:\Program Files (x86)\InstallShield\2020 or C:\Program Files (x86)\InstallShield\2020 SAB. 2.    InstallShield Build Task in the Classic Pipeline Editor to build in the Self Hosted Agent:   Provide the Project Path, Parameters (if any), Agent Location, and Path to InstallShield installed Location on the local agent.            
View full article
The following error message has been reported by customers running the FlexNet Publisher licensing service and Malwarebytes: This error has been identified as a false positive and has been resolved by Malwarebytes. A Malwarebytes forum thread confirms the error is no longer observed after a Malwarebyte database update. For more information or additional assistance related to this error, please contact Malwarebytes.
View full article
Step by Step Procedure to get the FNO Report or fulfillment History   1.Login to FNO UI. 2.Click on Entitlement->List Entitlements by Order   3.Select  the Entitlement ID or appropriate Activation ID to fetch the report.     4.Click on Fulfill history  
View full article
Problem: ALM On-Prem Installation of 2020 R1 fails to install if Open JDK 8 is installed with the following error      Windows: After InstallAnywhere extracts the content it fails with a java message: Could not find a valid Java virtual machine to load. You may need to reinstall a supported Java virtual machine.      Linux: [fno@fnorhel] $ sudo ./FlexNetOperations_2020-R1_installer.bin Preparing to install Extracting the installation resources from the installer archive... Configuring the installer for this system's environment... No Java virtual machine could be found from your PATH environment variable. You must install a VM prior to running this program. Solution:  The java version should be automatically picked by the installer. For Oracle JDK if java is installed using a JDK installer then FNO installer will pick that JDK. If oracle JDK is a zip distributable then JAVA_HOME needs to be set. In the case of open-JDK JAVA_HOME must be set for the installer to pick For Windows: 1. Downloaded the OpenJDK zip file. 2. extracted it to C:\Program Files\Java\ 3. set the system environment variable JAVA_HOME as "C:\Program Files\Java\jdk1.8.0_211" 4. set the system path variable as "C:\Program Files\Java\jdk1.8.0_211\bin" 5. Go to directory "C:\Program Files\Java\jdk1.8.0_211\bin" and executed "java -version" to see if Java is fine. 6. Go to the home directory and again executed "java -version" to see JAVA_HOME variable picked up by the system. 7. Go ahead with the installation of FNO and it worked fine. For Linux:  Make sure you set the JDK path in /etc/profile too for eg : add the below line in /etc/profile -> export PATH=$PATH:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.242.b08-0.el7_7.x86_64/bin If we Have multiple JDK( jdk 8 and 11) and verify which one installer picks The installer should only pick JDK 8 if using oracle JDK. Note: If using open JDK 8 specify java while installing using LAX_VM. For open-JDK installer won't pick by default since open-JDK doesn't come as an installer so there won't be any registry entry for that. If LAX VM is not passed then the installer would pick from JAVA_HOME For Windows: FlexNetOperations_2020-R1_installer.exe LAX_VM "C:\Program Files\Java\java-1.8.0-openjdk-1.8.0.232-3.b09.redhat.windows.x86_64\bin\java.exe" For Linux: ./FlexNetOperations_2020-R1_installer.bin LAX_VM "/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.242.b08-0.el7_7.x86_64/jre/bin/java".   Note: Officially tested only with RedHat Open JDK.
View full article
Currently, Windows compatible FNO On-premises does archive of logs in .gz format. This makes an administrator difficult to see the archive logs without installing any 3rd party software in the same windows server/machine. This article describes steps to change the archiving of logs into .zip format so that an administrator can use windows navigation to go through the logs without installing any third-party software.   Please follow the below steps to change the FNO logger: Log in to the FNO setup and stop the FNO server and then do un-deploy of FNO. Replace .gz with .zip for all 8 occurrences in below three files. This file location may vary based on your installation directory. C:\Program Files\FlexNet Operations\release\jbossConfig\flexnet\log4j\main\flexnet-log4j.xml C:\Program Files\FlexNet Operations\release\flexnet.ear\flexnet.war\WEB-INF\classes\flexnet-log4j.xml C:\Program Files\FlexNet Operations\webapp\WEB-INF\classes\flexnet-log4j.xml Login-back to FNO setup and Deploy the FNO. Verify the changes made in step 2 updated the file present in the below location of the FNO.   C:\Program Files\FlexNet Operations\components\wildfly\modules\system\layers\base\com\flexnet\log4j\main\flexnet-log4j.xml Start the FNO server from the FNO setup.   NOTE:  Please take a backup of all files before doing any changes, so that in case of any issues, the changes can be reverted back.  Also please make sure to first test the changes in a test environment before moving to production. A sample screenshot of  one of the loggers in the file which needs be changed is below:  
View full article
Summary Receiving FLEXlm Error -88,309: System Clock Has Been Set Back Synopsis When attempting to checkout a license, the following FLEXlm Error is received: -88,309: System clock has been set back. How do can this be resolved? Alternative terminology baddate, windback   Discussion NOTE: For security reasons, the following information is not to be shared with Enduser customers. The way our method works is to examine file dates in certain directories, and if dates are found > 24 hours in the future, then to deny usage. This is to prevent system clock tampering to allow extended usage of licenses. You will need to change all the files with dates in the future back to the current date. The directories which you need to check for these files are: For Windows (windows or winnt) ------------------ C:\ C:\windows C:\windows\system C:\windows\system32 C:\flexlm the directory where the app is located For UNIX ------------ v6+ checks these directories /etc /tmp /var It is recommended to write a batch file or binary to do this that looks like it does something else as providing this information to your end user could enable them to get round the licensing on your software. The ls_a_check_baddate behavior is as mentioned below:   During the initial handshake between the license server and the client, the system of the client is compared with the system time of the server.   If it is a permanent license, no error is thrown on time differences or bad date checks. If it is an expiring license, then: - If bad date on the server is detected, then the error “LM_BADSYSDATE” (-88, minor error 335) is thrown - If the difference between the client time and server time is more than 24 hrs, then “LM_CLOCKBAD” (-34, minor error 336) is thrown - If both of the above errors are present, only the first one (LM_BADSYSDATE) is thrown.   A bad date is detected if one of the system files has a last modification time stamp that is greater than the current system time (adjusting for some tolerance)."   Another possibility would be a discrepancy in the time/date between the various machines involved ( server / client / mapped drive's machine).  
View full article
If your account is tied to a company with a maintenance contract, you have permissions to open new support cases and view your previously submitted support cases. To Open a Case Sign in Go to the "Get Support" menu - it will be near the middle of the screen. Select "Open new case"   To View Existing Cases Sign in Go to the "Get Support" menu - it will be near the middle of the screen. Select "Case Portal"   For more information, please watch our How to Open a Support Case on the Case Portal video.
View full article
From 2020 R3 FlexNet Operations administrators now have permission to enable and reset the Cloud Licensing Server (CLS) producer user password for both existing and future Cloud License Server (CLS) instances. (A producer user password is used to obtain Authorization tokens for all instances.) for ALM and LLM FlexNet Operations LLM can now access the REST APIs provided in Cloud License Server (CLS) instances and in Local License Servers (LLS) to achieve administrative control of the license servers and to use the Cloud Monetization APIs for checking out licenses. The following are some aspects of the CLS interface: • Producers can use a UI to configure user credentials, which are then used to set up security and other administrative aspects of CLS configuration. • REST-driven licensing can be built into device software using the Cloud Monetization APIs. • Secure access to the Cloud Monetization APIs can be achieved by means of JWT authentication.  
View full article
Overview of Transfer Split functionality in LLM can found in this article . Property to be set for the below mentioned scenario 1: i)TransferSplitEnabled = True ii)TransferSplitEnabled.TransferOrderActivationCodeToTarget = false   1)Entitlement Details: Entitle the Source Account (View Account -> Entitle -> Entitle Account). Create order line in PP as shown below.     2)Allocation before Transfer: Check for the Activation Code under Allocations (View Entitlement -> View Allocations). We see that the Allocation is on account YT_S1 for both the line items.       3) Create Target Account :     4) Create Device, Map Add-ons from the order created above and Generate the File:     5)Transfer the Order: We see that allocations are moved from YT_S1 to YT_T1. Activation Code changes due to the property mentioned in ii)     6) After Transfer of Entitlements, we see that the Device which was under YT_S1 is under YT_T1(Target Account) The device should be moved to the target account The device should still have the same licenses on it after the transfer       7) Remove Add-ons from the Device. The removal of the add-ons should put the available count back on the right order. Removed add-ons with units 5 under Activation Code 2994-5452-0145-88D9 and 7 under CB45-4D8C-6D2E-519D. Remaining 3 under Activation Code CB45-4D8C-6D2E-519D is still mapped to the device. The remaining quantity 17 are available back on the right line item when we try to re-map the add-ons.                     Property to be set for the below mentioned scenario 2: i)TransferSplitEnabled = True ii)TransferSplitEnabled.TransferOrderActivationCodeToTarget = True   1)Entitlement Details: Entitle the Source Account (View Account -> Entitle -> Entitle Account). Create two order lines in PP as shown below.     2)Allocation before Transfer: Check for the Activation Code under Allocations (View Entitlement -> View Allocations). We see that the Allocation is on account YT_S1 for both the line items.     3) Create Target Account:   4) Create Device, Map Add-ons from the order created above and Generate the File:       5)Transfer the Order: We see that allocations are moved from YT_S1 to YT_T1. Activation Code remains same due to the property mentioned in ii)       6) After Transfer of Entitlements, we see that the Device which was under YT_S1 is under YT_T1(Target Account) The device should be moved to the target account The device should still have the same licenses on it after the transfer     7) Remove Add-ons from the Device. The removal of the add-ons should put the available count back on the right order. Removed add-ons with units 5 under Activation Code 21A5-376D-59EA-08F0and 7 under 9B4D-E517-D6AC-04C1 Remaining 3 under Activation Code 9B4D-E517-D6AC-04C1 is still mapped to the device. The remaining quantity 17 are available back on the right line item when we try to re-map the add-ons.        
View full article
Below is an example of the code that can be added to get the below details Checked out date and time User who made the checkout Number of licenses checked out Name of the feature Count of available license Count of used license Type of the feature   (void)lc_set_attr(lm_job, LM_A_LICENSE_DEFAULT, (LM_A_VAL_TYPE)LICPATH); for (feats = lc_feat_list(lm_job, LM_FLIST_ALL_FILES | LM_FILTERLIST_ALL_FILES, NULL); feats && *feats; feats++) { confi = lc_get_config(lm_job, *feats); if(confi->idptr && confi->idptr->id.data) printf(" This feature is node-locked \n\n"); else printf(" The feature is floating \n\n"); if (confi->users) { c = (CONFIG *)0; for (conf = lc_next_conf(lm_job, *feats, &c); conf; conf=lc_next_conf(lm_job, *feats, &c)) { fi.feat = conf; if (lc_get_attr(lm_job, LM_A_VD_FEATURE_INFO, (short *)&fi)) { lc_perror(lm_job, "LM_A_VD_FEATURE_INFO"); } else { total_lic = fi.num_lic; used_lic = fi.tot_lic_in_use; aval_lic = total_lic - used_lic; printf("Total number of licenses are %s = %d \n",feature, total_lic); printf("Available Count of licenses are %s = %d \n",feature, aval_lic); } } } else printf(" This feature is uncounted \n"); printf("##############################\n"); printf ("List of Users for Feature: %s\n",*feats); printf("##############################\n"); LM_USERS * pUserList = lc_userlist(lm_job, *feats); while (pUserList) { time_t currTime, difftime; char *sTime = malloc(50 * sizeof(char)); struct tm *localtime(), *currt, *t; if (strlen(pUserList->name) > 0) { int day = 0, hour = 0, minute = 0, second = 0; currTime = time(0); printf("User: %s Node: %s Licenses: %d \r\n", pUserList->name, pUserList->node, pUserList->nlic); t = localtime(&pUserList->time); printf("Checkout Done At - %02d/%02d %2d:%02d:%02d\n", t->tm_mon + 1, t->tm_mday, t->tm_hour, t->tm_min, t->tm_sec); difftime = (currTime - (pUserList->time)); printf("Checked out from last - %02d days", ((difftime / 86400))); difftime %= 86400; printf("% 02d hours", (difftime / 3600)); difftime %= 3600; printf("% 02d minutes", (difftime / 60)); difftime %= 60; printf("% 02d seconds\n\n", difftime); } pUserList = pUserList->next; if (pUserList && (!pUserList->name || strlen(pUserList->name) == 0)) pUserList = NULL; } } printf("##############################\n"); printf("press return to exit...");  
View full article
This article lists the current year's past releases for FlexNet Operations Cloud. For upcoming releases, please see the Software Monetization Release Schedule. NOTE: This requires you to log into the community as a Revenera customer.  2020 Releases -  FlexNet Operations Cloud ALM Release Production Copy Service (PCS) Data Refresh Date PCS / UAT Date Production Date Production Outage? 2020 R1 Wednesday, Jan 8, 2020 Thursday, Jan 9, 2020 Thursday, Feb 6, 2020 No 2020 R1 SP1   Monday, Feb 24, 2020 Monday, Mar 09, 2020 No 2020 R1 SP2   Thursday, Mar 26, 2020 Thursday, Apr 09, 2020 No 2020 R2 Wednesday, Apr 13, 2020 Tuesday, Apr 14, 2020 Wednesday, May 20, 2020 No 2020 R2 SP1   Thursday, Jun 4, 2020 Thursday, Jul 2, 2020 No 2020 R3 Friday, Jul 10, 2020 PCS:   Wednesday, Jul 15, 2020 UAT: Monday, Jul 27, 2020 Thursday, Aug 13, 2020 No 2020 R3 (CLS)     Saturday, Aug 15, 2020 Yes   FlexNet Operations Cloud LLM Release Production Copy Service (PCS) Data Refresh Date PCS / UAT Date Production Date Production Outage? 2020 R1 Wednesday, Jan 8, 2020 Thursday, Jan 9, 2020 Thursday, Feb 6, 2020 No 2020 R1 SP1   Monday, Feb 24, 2020 Monday, Mar 09, 2020 No 2020 R1 SP2   Thursday, Mar 26, 2020 Thursday, Apr 09, 2020 No 2020 R2 Wednesday, Apr 13, 2020 Tuesday, Apr 14, 2020 Wednesday, May 20, 2020 No 2020 R2 SP1   Thursday, Jun 4, 2020 Thursday, Jun 18, 2020 No 2020 R3 Friday, Jul 10, 2020 PCS:   Wednesday, Jul 15, 2020 UAT: Monday, Jul 27, 2020 Monday, Aug 10, 2020 No 2020 R3 (CLS)     Saturday, Aug 15, 2020 Yes  
View full article
Summary FLEXnet Connect is a solution that Flexera Software sells to software vendors that is designed to help you stay connected with your customers after they install your applications. Synopsis FLEXnet Connect is a solution that Flexera Software sells to software vendors that is designed to help you stay connected with your customers after they install your applications. Keeping software updated is one of the many benefits of FLEXnet Connect, but Flexera Software also recommends that software vendors build in an option to disable automatic update checking. If you are using an application that uses FLEXnet Connect, your application may have a configuration option to disable update checking. Please check your application?s menu options. If your application does not have this option, Flexera Software has created a tool called the Software Manager that can disable automatic update checking. The Software Manager utility lists all applications currently using FLEXnet Connect on your computer and the FLEXnet Connect's status with that application. Discussion You may already have the Software Manager installed. If the Software Updates or Program Updates shortcut is listed in your Start menu, then the Software Manager is installed. If you do not have the Software Manager installed, follow these instructions to download and install it: Download and install the Software Manager: Download the latest FLEXnet Connect 6.1 Software Manager and save it to your Desktop. The latest FLEXnet Connect Software Manager can be downloaded here. 2. Double click on the FLEXnet connect executable and follow the instructions to install the Software Manager. Once installed, you can run the Software Updatesshortcut to start the Software Manager. Download and install the uninstall for Software Manager: Download the Update Manager uninstaller and save it to your Desktop. 2. Double click SoftwareManagerUninstall.exe and follow the instructions to uninstall the Software Manager. Note: The SoftwareManagerUninstall.exe only removes entries from the Windows registry which are responsible for starting the common software manager after a reboot. No files are actually removed.
View full article
Summary This error message is a system-specific error and can be caused by a system-specific setting. This article attempts to list all the possible steps that have known to resolve this error. Symptoms When running an installation created with an InstallShield product, the following error occurs at the beginning of the installation: Error -1607: Unable to Install InstallShield Scripting Runtime This error message is a system-specific error and can be caused by a system-specific setting. This article attempts to list all the possible steps that have known to resolve this error. Depending on your system, you may need to try some or all of the listed solutions. Cause This does not occur with InstallShield 12 and later. The architecture in InstallShield 12 and later has several advantages over the earlier architecture. End users no longer encounter error 1607, error 1608, or other COM/DCOM run-time errors that are related to finding the running IDriver.exe file. When these errors occurred under the earlier model, they were difficult to resolve, often requiring changes to DCOM settings. Also, the reliance on the running object table made the model brittle across the spectrum of usage scenarios, including Fast User Switching and Windows Terminal Services. Resolution Update the ISScript engine on your computer by downloading the latest one. For more information, see Setup Is Unable To Find or Update ISScript.msi. Make sure that the Installer folder in the Windows directory has full access privileges. The Installer folder may be hidden on your computer, so you will have to set your computer to see hidden files and folders and then set the proper permissions to the <WINDOWSFOLDER>\Installer folder: A. Show Hidden Files and Folder Launch Windows Explorer by pressing the Windows key + E or select Start > Run and typeexplorer. Select Tools > Folder in the Windows Explorer window. Select the View tab. In the Advanced Settings pane, select Show hidden files and folder. B. Set the Installer folder attributes Locate the folder <WINDOWSFOLDER>\Installer: Windows NT and 2000: C:\WINNT\Installer Windows 95/98/Me/ XP: C:\Windows\Installer Note: In some instances this directory doesn't appear on Windows XP machines. Follow these steps to view the folder: a. In Windows Explorer select View > Toolbars and select Address Bar if there isn't a check box next to it. b. In the Address Bar type in the full path: C:\WINDOWS\Installer. 2. Right-click on the Installer folder and choose Properties. 3. Select the Security tab. 4. Make sure the System, Administrators and the specific user have Full Control of this folder. C. Repeat the instructions in Step B for the Temp directory. To locate the Temp directory on your machine, refer to the article Clean the Temp Directory. 3. Make sure that the InstallShield registry key in the Windows registry has full access privileges. Select Start > Run and type regedt32. Browse to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\InstallShield Check the permissions of this key: Windows XP users can right click and select Permissions. Windows 2000 and NT users navigate to the Security menu and select Permissions. 4. Assign both the Administrators and System group Full Control if they don't already have it. For an idea of what the permissions property dialog will look like, see step 2B-4. 4. If the installation is located on a network drive, copy all of the files to the local hard drive (i.e., Desktop or Temp directory) and attempt to run the installation again. 5. Install the Windows Installer engine on your computer to make sure that it is not corrupt and that it is properly registered on your computer. For more information, see How Do I Install the Windows Installer Engine on My Computer Using InstallShield. 6. Make sure you have full administrative privileges on your computer. This does not apply to Windows 95, 98, and ME. 7. Make sure no other applications, installations, or processes are running in the background. For more information, see Manually Detect and End Previously Running Installation Process and Close Applications Running in the Background . 8. Make sure to check the location from where the installation is being run. If the downloaded installation files are stored in a directory path that contains special characters, such as "&", "-", ".", etc, change the path to something that does not contain these characters. Bad path: C:\downloads\Palm\palm desktop & hotsync\x\setup.exe Good path: C:\downloads\Palm\palm desktop hotsync\x\setup.exe Does Your Issue Still Exist? If after following these instructions your product failed to install, you'll need to contact your vendor. See the Who to Contact page for more information. Related KB Articles Q108353 Q108373 Q108351 Q108345 Q108213 Q111114
View full article