Flexera Software Community Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 
Knowledge Base Categories
We have an expert team of professionals available to answer questions and to assist you with technical issues with Flexera products. To contact Support for technical issues, using our case portal, in the top menu click Get Support -> Open New Case. NOTE: The online case portal requires the user to be logged into the community and the login to be associated with an account that has active maintenance. If you do not see this option, please use our phone support. You can contact Support by phone using the toll and toll-free options below: North America +1 630-332-2513 (toll) +1 877-279-2853 (toll-free) Europe +44 1925 944367 (toll) +44 800 047 8642 (toll-free) India +61 1800 560 603 (toll) 000 800 040 2367 (toll-free) Japan +81 3-4540-5335 (select option 2)  
View full article
Summary This article provides information on how to prevent the Software Manager Update utility from automatically searching for product updates. Instead, you'll be able to manually launch the utility to check for updates at your discretion Synopsis This article provides information on how to prevent the Software Manager Update utility from automatically searching for product updates. Instead, you'll be able to manually launch the utility to check for updates at your discretion. Discussion 1. Click Start -> All Programs and then click Software Manager or Software Updates. 2. Click the Settings option. 3. Click one of the existing product hyperlinks from the list displayed. 4. Select the option "Manually". 5. Click the Apply to all products button. 6. Close the window.
View full article
Symptoms: When upgrading from an earlier FNO On-Premise version to the latest FNO version (e.g. 12.10 to 2018 R1) the following error may be thrown: Error: [ADMN] Cannot find entitlement id generator class com.flexnet.operations.generator.OpsEsnGenerator Diagnosis: The path for license generator is incorrect in the configuration setting for FNO. Solution: 1. Navigate to 'System > Configure > Flexnet Operations' in your FNO admin portal. 2. In the 'ID Generator Classname' and 'Fulfillment ID Generator Classname' remove 'macrovision' from the path,  and replace it with 'flexnet', (if it's not already present), 3. Now log out and back into FNO.
View full article
Description of Flexera Support maintenance plans
View full article
Symptoms: It had been noted that due to some OS dependencies, post a reboot the FNLS (Flexnet Licensing Service) is unable to start automatically and which leads to a failure of multiple kinds on virtualization platform based licensing. Diagnosis: /var/run/FNP directory is getting deleted after restarting the machine and FNPLicensingService is not able to create the /var/run/FNP/FNPLicensingService64.pid file. Solution: Following is the work around script. (Kindly put your native paths of toolkit directory) [Unit] Description=This Service re-install's FNPLicensingService on Boot After=network.target remote-fs.target [Service] Type=forking RemainAfterExit=yes User=root WorkingDirectory=/home/fnpauto/abhay/leiyang/it1/32/i86_lsb/publisher ExecStart=/usr/bin/sh /home/fnpauto/abhay/leiyang/it1/32/i86_lsb/publisher/install_fnp.sh [Install] WantedBy=multi-user.target 1.save above script in fnls.service and put it under /etc/systemd/system 2.sudo systemctl daemon-reload 3.sudo systemctl enable fnls.service 4.sudo systemctl start fnls.service. 5.Reboot the server.
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 No workaround is available at this time. The Flexera team is actively working with Akamai to identify workaround options.   Resolution No resolution is available at this time. Customers impacted by this issue should reach out to Flexera Support, if they have not already done so, to be notified of any changes in the situation. Until a workaround or resolution is available, we recommend customers comply with the file size limitation.
View full article
This article provides a Hotfix for InstallAnywhere 2018 SP1.
View full article
Question: How  FNP fetches username and hostname through native source code Answer: Below is the way FNP fetches username and hostname through native source code.                                  Windows                             Linux                                     OSX Host name          gethostname()                  gethostname()                  gethostname() User name          GetUserNameW()            getuid                                   getuid
View full article
Environment The issue occurs in this environment: The operating system on which FlexNet Code Insight and its associated database is installed is CentOS 7 or RHEL 7. The Code Insight database is MySQL version 8. Symptoms When you use the FlexNet Code Insight installer to install the latest version of Code Insight on a Linux machine, an error related to the database connection can occur even though the database log-in credentials provided during installation are valid. To view the error description in a Code Insight installer log, open the attached file. Diagnosis MySQL 8 uses a set of time zone values that are different from values used by CentOS and RHEL. For example, MySQL8 uses time zone values that include “PDT”, “CST”, and so forth, whereas Centos and RHEL use named time zones such as “America/Chicago” and “Europe/Lisbon”. Solution The MySQL time-zone tables must be populated with named time-zone values from the publicly available “zoneinfo” (or “tzinfo”) database used by computers and operating systems internationally. Once these tables are populated, you can configure MySQL with the named time zone appropriate for your location. To populate MySQL time-zone tables and reconfigure the MySQL time zone, do the following: From the machine on which the MySQL resides, run the following command to populate the MySQL time zone tables: mysql_tzinfo_to_sql /usr/share/zoneinfo/|mysql -u root mysql -p To reconfigure the MySQL time zone, open the my.cnf file in your MySQL installation, and edit the "default_time_zone" line to reflect the named time zone appropriate for your location: default_time_zone="America/Los_Angeles"  This example uses the America/Los_Angeles named time zone. To help you locate the appropriate time zone for your MySQL installation, click here: https://en.wikipedia.org/wiki/List_of_tz_database_time_zones Save my.cnf. Restart MySQL to apply the changes.  
View full article
Perforce not Installed
View full article
Building the 32bit FNP toolkit for certificate use: First, you’ll need to build the FNP toolkit (11.16.4.0_v6) via the command line using a Visual Studio Command Prompt. 1: Add your vendor keys and vendor name to the lm_code.h, then set your seed values and signature strength – this file can be found in the ‘..\i86_n3-11.16.4.0_v6\machind’ directory: e.g. #define VENDOR_KEY1 0x8e3d842c #define VENDOR_KEY2 0x15ec254d #define VENDOR_KEY3 0x2c8769d8 #define VENDOR_KEY4 0x85f62e41 #define VENDOR_KEY5 0x89f5ec54   #define VENDOR_NAME "demo"   #define LM_SEED1 0x65413216 #define LM_SEED2 0x45313165 #define LM_SEED3 0x32313315   #define LM_STRENGTH LM_STRENGTH_239BIT 2: Edit the makefile and add your vendor name to the ‘VENDORNAME’ field - this file can be found in the ‘…\i86_n3-11.16.4.0_v6\i86_n3’ directory: e.g. VENDORNAME = demo DAEMON = $(VENDORNAME).exe 3: in the ‘…\i86_n3-11.16.4.0_v6\i86_n3’ directory change ‘demo.rc’ to the name of your vendor daemon: e.g. demo.rc > Flexera.rc 4: In the VS command prompt run the following: …\i86_n3-11.16.4.0_v6\i86_n3> nmake -f makefile Now your FNP toolkit is built to use certificate-based licensing. Follow the steps below to build lmflex using Visual Studio.    Steps to build lmflex using Visual Studio 2015: 1: Create a Win32 Console Project called 'lmflex'. 2: Copy the lmflex.c code from the toolkit, found in the following location “..\i86_n3-11.16.4.0_v6\machind” and comment out the Trusted Storage code as shown below. Or you can copy the code below for just certificate only licensing: /************************************************************************************************** * Copyright (c) 1997-2018 Flexera. All Rights Reserved. **************************************************************************************************/ /*  *  *            Description:        This is a sample application program, to illustrate  *                                            the use of the Flexible License Manager.  *  */   #include "lmclient.h" #include <stdio.h> #include <stdlib.h> #include <string.h> #include <time.h> #include "lm_attr.h" #include "lm_redir_std.h"   #ifdef PC #define LICPATH "@localhost" #else #define LICPATH "@localhost:license.dat:." #endif /* PC */   #define FEATURE "f1" VENDORCODE code; LM_HANDLE *lm_job;   //JoeMC: Uncomment to use TS //static void init(struct flexinit_property_handle **); //static void cleanup(struct flexinit_property_handle *);   int main(int argc, char * argv[]) {                 char feature[MAX_FEATURE_LEN * 2] = {'\0'};                 struct flexinit_property_handle *initHandle = NULL;                 int nlic = 1;                   //JoeMC: Uncomment to use TS                 //init(&initHandle);                   if (argc > 1)                 {                                 nlic = atoi(argv[1]);                 }                   if (lc_new_job(0, lc_new_job_arg2, &code, &lm_job))                 {                                 lc_perror(lm_job, "lc_new_job failed");                                 //JoeMC: Uncomment to use TS                                 //cleanup(initHandle);                                 exit(lc_get_errno(lm_job));                 }                   printf("Enter \"f1\" to demo floating functionality\n");                 printf("Enter \"f2\" to demo node-locked functionality\n");                 printf("Enter feature to checkout [default: \"%s\"]: ", FEATURE);                     fgets(feature, MAX_FEATURE_LEN + 2, lm_flex_stdin()); /*           add 2 for \n and \0          */                 feature[strlen(feature) - 1] = '\0';                 if(!*feature)                                 strcpy(feature, FEATURE);                   (void)lc_set_attr(lm_job, LM_A_LICENSE_DEFAULT, (LM_A_VAL_TYPE)LICPATH);                   if(lc_checkout(lm_job, feature, "1.0", nlic, LM_CO_NOWAIT, &code, LM_DUP_NONE))                 {                                 lc_perror(lm_job, "checkout failed");                                 //JoeMC: Uncomment to use TS                                 //cleanup(initHandle);                                 exit (lc_get_errno(lm_job));                 }                 printf("%s checked out...", feature);                 printf("press return to exit...");                   /*                 *             Wait till user hits return                 */                 getchar();                 lc_checkin(lm_job, feature, 0);                 lc_free_job(lm_job);                 //JoeMC: Uncomment to use TS                 //cleanup(initHandle);                 return 0; }   //JoeMC: Uncomment to use TS /* static void init(struct flexinit_property_handle **handle) { #ifndef NO_ACTIVATION_SUPPORT                 struct flexinit_property_handle *ourHandle = NULL;                 int stat;                   if ((stat = lc_flexinit_property_handle_create(&ourHandle)))                 {                                 fprintf(lm_flex_stderr(), "lc_flexinit_property_handle_create() failed: %d\n", stat);                                 exit(1);                 }                 if ((stat = lc_flexinit_property_handle_set(ourHandle,                                                 (FLEXINIT_PROPERTY_TYPE)FLEXINIT_PROPERTY_USE_TRUSTED_STORAGE,                                                 (FLEXINIT_VALUE_TYPE)1)))                 {                                 fprintf(lm_flex_stderr(), "lc_flexinit_property_handle_set failed: %d\n", stat);                     exit(1);                 }                 if ((stat = lc_flexinit(ourHandle)))                 {                                 fprintf(lm_flex_stderr(), "lc_flexinit failed: %d\n", stat);                     exit(1);                 }                 *handle = ourHandle; #endif // NO_ACTIVATION_SUPPORT }   static void cleanup(struct flexinit_property_handle *initHandle) { #ifndef NO_ACTIVATION_SUPPORT                 int stat;                   if ((stat = lc_flexinit_cleanup(initHandle)))                 {                                 fprintf(lm_flex_stderr(), "lc_flexinit_cleanup failed: %d\n", stat);                 }                 if ((stat = lc_flexinit_property_handle_free(initHandle)))                 {                                 fprintf(lm_flex_stderr(), "lc_flexinit_property_handle_free failed: %d\n", stat);                 } #endif // NO_ACTIVATION_SUPPORT } */ 3: Right click on the lmflex project and open “Properties”. 4: In the “General” settings change the ‘Character Set’ to ‘Use Multi-Byte Character Set’. 5: In the “C/C++” settings under the ‘General’ section add the following to the ‘Additional Include Directories: …\i86_n3-11.16.4.0_v6\machind and …\i86_n3-11.16.4.0_v6\machind\activation\include 6: In the “C/C++” settings under the ‘Preprocessors’ section add the following to the ‘Preprocessors Definitions’: _CRT_SECURE_NO_WARNINGS 7: In the “Linker” settings under the ‘General’ section add the following to the ‘Additional Library Directories: …\i86_n3-11.16.4.0_v6\i86_n3 and …\i86_n3-11.16.4.0_v6\i86_n3\activation\lib 8: In the “Linker” settings under the ‘Input’ section add the following libraries to the ‘Additional Dependencies’: lm_new.obj lmgr_trl.lib libsb.lib libcrvs.lib .\activation\lib\libnoact.lib libredir_std.lib oldnames.lib kernel32.lib user32.lib netapi32.lib gdi32.lib comdlg32.lib comctl32.lib wsock32.lib shell32.lib Rpcrt4.lib oleaut32.lib Ole32.lib Wbemuuid.lib wintrust.lib crypt32.lib Ws2_32.lib iphlpapi.lib Psapi.lib advapi32.lib Shlwapi.lib userenv.lib lmgr_dongle_stub.lib msvcrt.lib vcruntime.lib legacy_stdio_definitions.lib legacy_stdio_wide_specifiers.lib ucrt.lib Dhcpcsvc.lib libvcruntime.lib 9: In the “Linker” settings under the ‘Ignore All Default Libraries’ set this to ‘Yes (/NODEFAULTLIB)’. 10: In your project change the lmflex.cpp filename to lmflex.c and the stdafx.cpp to stdafx.c then build lmflex. Now, you should be able to run lmflex and perform a checkout from a license server. Steps to set up a license server to serve a certificate license: 1: Edit ‘counted.lic’ from the ‘…\i86_n3-11.16.4.0_v6\i86_n3’ directory and change the vendor name ‘demo’ to your vendor name. e.g. SERVER this_host ANY VENDOR demo USE_SERVER #a counted license FEATURE f1 demo 1.0 permanent 4 SIGN="003D B062 54D1 47E3 1FF6 145F \                 59CE 0200 8002 FE69 0FBC F4FF AA10 FFB3 6EB3" To SERVER this_host ANY VENDOR flexera USE_SERVER #a counted license FEATURE f1 flexera 1.0 permanent 4 SIGN="003D B062 54D1 47E3 1FF6 145F \                 59CE 0200 8002 FE69 0FBC F4FF AA10 FFB3 6EB3"   2: encrypt ‘counted.lic’ license file using the VS command prompt: e.g. …\i86_n3-11.16.4.0_v6\i86_n3> lmcrypt.exe counted.lic 3: Start the license server by running the following in the command prompt: e.g. …\i86_n3-11.16.4.0_v6\i86_n3> lmgrd.exe -z -c counted.lic 4: Perform a checkout using the lmflex you built previously: e.g. …\i86_n3-11.16.4.0_v6\i86_n3> lmflex.exe  Enter "f1" to demo floating functionality Enter "f2" to demo node-locked functionality Enter feature to checkout [default: "f1"]: f1                      
View full article
If your account is tied to a company with a maintenance contract, you have permissions to view cases you submitted.  To Filter by Status Go to the  "My Cases" screen. Click on the "Filter" button Check the "All Company Cases" checkbox Click on the "Apply Filters >" button 
View full article
Updated 3 June 2019 If your account is tied to a company with a maintenance contract, you have permissions to view cases you submitted.  To Filter by Status Go to the  "My Cases" screen. Click on the "Filter" button Click on the Status menu to open a drop-down menu with status options. Select the option you desire Click on the "Apply Filters >" button 
View full article
In order to have access to our Support Case Portal, Product and License Center and customer-only resources like the Learning Center, community users must have their individual community account login tied to their organization's account that has active maintenance.  There are two ways to do this connection: 1. At the time of registration When creating your individual community login, specify your organization's account ID and product ID on the registration screen. These sources of data may be found in your order confirmation email. 2. Post-registration If you've already registered for our community and didn't provide your account and product IDs, or if you had an account prior to becoming a customer, you will need Flexera Technical Support to assist you with linking your login to the appropriate company account. Please email support@flexera.com and include your full name and organization's name and request to connect your community account with your organization. More Information How to tell what organization your login is associated with? Sign into the community using your login Click on your avatar in the upper right-hand corner Select My Account to see the Organization field What to do when moving to another company? Please contact support@flexera.com to help with updating the company account your login is associated with.
View full article
Users creating and updating cases may add Case Watchers. These individuals will receive a Case Watcher notification email if there are any changes to a specific Case to which the Watcher has been applied. To Add a Case Watcher: Create a case In the case view, add their email and press "Save Member". Note: If the user is not yet in the system, have them  register  and then add them. The case watcher field will update with your case watchers. To Delete a Case Watcher Press the trash can icon in the Action column for the Case Watchers you wish to remove.
View full article
You may find you need help beyond community forums, our documentation and learning opportunities. Read on for case best practices.  Submitting a detailed case helps everyone act more quickly toward a resolution. So be as thorough as possible when filling out case information. Our support cases have five key areas to complete. An optional sixth area is detailed at the end. Case Summary: This serves as your support case title and will appear in your email subject lines. Write titles detailing the action needed. This helps narrow the scope, so our support team can quickly triage and identify tickets.  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 problem affecting. 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. Why: What is the expected outcome versus what actually happens. Product: Please select the appropriate product to quickly route your case. Failing to select the proper product will add to the response time. Version: The drop-down menu will adjust based on the product you select. Please choose the version to quickly route the case. Severity levels:   There are 4 severity levels used to classify a case: Severity 1 – Critical:   Production use of the cloud software is stopped or so severely impacted that authorized end users cannot reasonably use it. Flexera will work continuously to resolve the support request until it is closed. Severity Level 1 issues must be reported by telephone. Severity 2 – High:   Major cloud software documented features are unavailable with no workaround. Use of the cloud software can continue; however, productivity is significantly decreased. Flexera will work continuously to resolve the support request until it is closed. Severity Level 2 issues must be reported by telephone. Severity 3 – Medium:   Major cloud software documented features are unavailable, but a workaround is available, or less significant cloud software documented features are unavailable with no reasonable workaround. Severity 4 – Low:   Authorized end-user requests information about the cloud software or an enhancement to the existing cloud software specifications. Use of the cloud software is available without being materially and adversely impeded. Optional: end customer:   Our partners use this field to detail their clients affected by the case issue.   BONUS: Case Watchers After you create your case, you can add case watchers to the field. Case watchers receive email updates on case progress so adding key staff help keep your team apprised of progress. Details on adding case watchers are   here.
View full article
Description The help contents packaged with lmadmin 11.6.4.0 are incorrect. This was reported as known issue FNP-21453.  Replication Scenario No replication steps required. Workaround No workaround available.  Version Fix Target FlexNet Publisher lmadmin 2019 R2 SP1 (11.16.4.1)  Resolution Please upgrade the lmadmin to 11.16.4.1. From this version, the correct help contents will display in the lmadmin server UI.  
View full article
Summary How To generate the InstallAnywhere Log for Install, Uninstall, and Build in InstallAnywhere 2011 and later. Synopsis This article discusses how to generate an install/uninstall/build log to capture what is occurring during an installation/uninstallation/build, primarily for troubleshooting purposes.   Discussion Generating an InstallAnywhere Standard Installation Log: Follow these steps in the InstallAnywhere IDE with your project open: Navigate to the Project > General Settings > Log Settings Section. For InstallAnywhere versions earlier than 2013, navigate to Project > Log Settings. Under Log Settings section, set Enable Logging to Yes. For InstallAnywhere versions earlier than 2013, check the Enable Logging checkbox Check the Install checkbox. Under Log Format, select the Plain text format option. Build the project. Run the installer. Note 1: Plain text format is selected by default, not XML format. Note 2: These steps will create an installation log in plain text or XML format. The installation log file is created in the installation directory, under a Logs subdirectory, with the default filename $PRODUCT_NAME$_InstallLog.log or $PRODUCT_NAME$_InstallLog.xml.   Generating an InstallAnywhere Standard Installation Log That Includes the Verbose Installation Debug Output: Follow these steps in the InstallAnywhere IDE with your project open: Navigate to the Project > JVM Settings > Installer Settings View > Optional Installer Arguments Section. Specify the following value in the Additional Arguments field: -Dlax.debug.level=4 -Dlax.debug.all=true Navigate to the Project > General Settings > Log Settings Section. For InstallAnywhere versions earlier than 2013, navigate to Project > Log Settings. Under Log Settings section, set Enable Logging to Yes. For InstallAnywhere versions earlier than 2013, check the Enable Logging checkbox. Check the Install checkbox. Under Log Format, select the Plain text format option. Set Include debug output (stderr and stdout) to Yes. For InstallAnywhere versions earlier than 2013, check the Include Debug Output (stderr and stdout) checkbox. Build the project. Run the installer. Note 1: Verbose debug output refers to more detailed debug output that can be generated by an installer. Note 2: Plain text format is selected by default, not XML format. Note 3: These steps will create an installation log in plain text or XML format. The installation log file is created in the installation directory, under a Logs subdirectory, with the default filename $PRODUCT_NAME$_InstallLog.log or $PRODUCT_NAME$_InstallLog.xml.   Generating an InstallAnywhere Standard Uninstallation Log: Follow these steps in the InstallAnywhere IDE with your project open: Navigate to the Project > General Settings > Log Settings Section. For InstallAnywhere versions earlier than 2013, navigate to Project > Log Settings. Under Log Settings section, set Enable Logging to Yes. For InstallAnywhere versions earlier than 2013, check the Enable Logging checkbox Check the Uninstall checkbox. Under Log Format, select the Plain text format option. Build the project. Run the installer. Run the uninstaller. Note 1: Plain text format is selected by default, not XML format. Note 2: These steps will create an uninstallation log in plain text or XML format. The uninstallation log file is created in the installation directory, under a Logs subdirectory, with the default filename $PRODUCT_NAME$_UninstallLog.log or $PRODUCT_NAME$_UninstallLog.xml.   Generating an InstallAnywhere Standard Uninstallation Log That Includes the Verbose Uninstallation Debug Output: Follow these steps in the InstallAnywhere IDE with your project open: Navigate to the Project > JVM Settings > Installer Settings View > Optional Installer Arguments Section. Specify the following value in the Additional Arguments field: -Dlax.debug.level=4 -Dlax.debug.all=true Navigate to the Project > General Settings > Log Settings Section. For InstallAnywhere versions earlier than 2013, navigate to Project > Log Settings. Under Log Settings section, set Enable Logging to Yes. For InstallAnywhere versions earlier than 2013, check the Enable Logging checkbox Check the Uninstall checkbox. Under Log Format, select the Plain text format option. Set Include debug output (stderr and stdout) to Yes. For InstallAnywhere versions earlier than 2013, check the Include Debug Output (stderr and stdout) checkbox. Build the project. Run the installer. Run the uninstaller. Note 1: Verbose debug output refers to more detailed debug output that can be generated by an uninstaller. Note 2: Plain text format is selected by default, not XML format. Note 3: These steps will create an uninstallation log in plain text or XML format. The uninstallation log file is created in the installation directory, under a Logs subdirectory, with the default filename $PRODUCT_NAME$_UninstallLog.log or $PRODUCT_NAME$_UninstallLog.xml.   Generating a Build Log: Command Line Build Log The build output when running a command line build can be redirected by setting the following two properties in the build.lax file. The build.lax file is found in the InstallAnywhere HOME where InstallAnywhere is installed. lax.stderr.redirect=\\tmp\\buildconsole.txt lax.stdout.redirect=\\tmp\\buildconsole.txt Setting the properties as shown above will generate a file named buildconsole.txt in the specified directory (C:\\tmp) in Windows. If only a filename is specified as shown below, then the file will be created in the same directory containing the build.lax file. lax.stderr.redirect=buildconsole.txt lax.stdout.redirect=buildconsole.txt GUI Build Log The build output when running a GUI build, through the InstallAnywhere Advance Designer, can similarly be redirected to a file by setting the lax.stdout.redirect and lax.stderr.redirect properties (mentioned above) in the InstallAnywhere.lax file. This file is found in the InstallAnywhere installation directory, where InstallAnywhere is installed. Note: You will need to restart the InstallAnywhere IDE after making the changes in the InstallAnywhere.lax file.
View full article
Summary Generating InstallAnywhere Build Log specifically for Windows and Linux. Synopsis This article outlines the steps necessary to generate a verbose build-time debug log, specifically for Windows and Linux.   Discussion An InstallAnywhere verbose build-time debug log can be generated through a number of ways: From the Advanced Designer: When running a GUI build through the InstallAnywhere Advanced Designer, the build output can be redirected to a text file by setting the following two properties in the InstallAnywhere.lax file. lax.stderr.redirect=buildconsole.txt lax.stdout.redirect=buildconsole.txt The InstallAnywhere.lax file is found in the location where InstallAnywhere is installed. Setting the above two properties to a text file will generate the text file in the same directory as the InstallAnywhere.lax file is located. A path can also be specified, so that the log will be created in that specific location. Write permissions to the directory where a file is being created are necessary. Note: You will need to restart the InstallAnywhere IDE after making the change in the InstallAnywhere.lax file. To generate a verbose GUI build-time debug log (in InstallAnywhere versions prior to 2011), add the following line to the top of the InstallAnywhere.lax file: lax.nl.java.option.additional=-Dlax.debug.all=true -Dlax.debug.level=4 In InstallAnywhere 2011 and later, this property is already included in the InstallAnywhere.lax file. Therefore, if the property already exists in the InstallAnywhere.lax file, append "-Dlax.debug.level=4 -Dlax.debug.all=true" (without quotes) at the end of the existing property (like shown below) lax.nl.java.option.additional=ExistingValue -Dlax.debug.level=4 -Dlax.debug.all=true where, ExistingValue is the value that is already present and assigned to the property. Note: Ensure that there is only one entry for the lax.nl.java.option.additional property, otherwise the build-time log with not be verbose. The Build Log tab in the Build section of the InstallAnywhere Advanced Designer displays a build log in XML format once a build is complete (only applicable to the Premier Edition). From the Command-Line: If you are building from the command line using the application launcher named "build.exe" then, use the following approach: build.exe "C:\MyProduct.iap_xml" You can use the build output displayed in the console window as a build-time log. To save the log information in a file, copy the output of the build from the console window to a text file. When running a command line build, the build output can also be redirected to a text file by setting the following two properties in the build.lax file located in IA HOME where InstallAnywhere is installed. lax.stderr.redirect=buildconsole.txt lax.stdout.redirect=buildconsole.txt Setting, the properties as shown above will generate a file named buildconsole.txt in IA HOME, in the same directory containing the build.lax file. You can also specify a path to a text file if you want to create the text file in another location. To generate a verbose command line build log (in InstallAnywhere versions prior to 2011), add the following line to the top of the build.lax file: lax.nl.java.option.additional=-Dlax.debug.all=true -Dlax.debug.level=4 Note: For InstallAnywhere 2011 and later, append "-Dlax.debug.level=4 -Dlax.debug.all=true" (without quotes) at the end of the existing property in the build.lax file as explained in the From the Advanced Designer section above. Note: Ensure that there is only one entry for the lax.nl.java.option.additional property, otherwise the build-time log with not be verbose.   Additional Information For instructions on generating an installation/uninstallation log with InstallAnywhere 2010 and previous InstallAnywhere versions: Generating InstallAnywhere Log for Install and Uninstall with InstallAnywhere For instructions on generating an installation/uninstallation log with InstallAnywhere 2011 and later InstallAnywhere versions: Generating a Log for Install, Uninstall, and Build in InstallAnywhere.
View full article
Summary This article provides information on configuring a three server redundancy using lmadmin. Synopsis This article provides information on configuring a three server redundancy using lmadmin. Discussion Here are the Steps to Configure a Triad License Server:   Install the FlexNet Licensing Server from the Product and License Center: https://flexerasoftware.subscribenet.com Open the command prompt as Administrator and cd to the directory that contains lmadmin.exe ( cd C:\Program Files (x86)\Flexera Software\FlexNet\Licensing Server). If you installed the license server as a service this file will be named lmadmin_svc.exe Force Import the license file into lmadmin (l madmin.exe -force -import <PATH TO LICENSE FILE>). The License file is generated in the Product and License Center (see related KB Q214185) Repeat steps 1-3 for the other 2 license servers machines Start lmadmin on all 3 machines in the same order specified in the license file: primary, secondary and tertiary The system configuration would show the status of the license servers connecting to the other 2 servers as shown in the below screenshot. If lmadmin is unable to establish a quorum in fifteen minutes, stop the servers on all 3 machines and restart the servers in the correct order.     Related KB Articles Required Fields For A Concurrent Triad License Generated Through The Product And Licensing Center Create a Login ID for Accessing the Product and License Center
View full article