Flexera Software Community Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 
Knowledge Base Categories
Question: Has older HASP (HASP4) dongle support removed from latest version of FNP toolkits? Answer: Starting 11.14.0 we have to enable support for the HASP4 dongles in the daemon configuration file ls_vendor.c (unsigned int ls_flexid9_hasp4_support = 1;) .  After doing that and ensuring that we build the toolkit with additional argument as DONGLE=1, with a clean build, we should be able to start the vendor daemon. 
View full article
Question: Can a Publisher attach Flexera Product Documents in its distribution? Answer: The answer is that it is permissible to re-distribute the documentation in its original form, unmodified in any way. The means of distribution can include: Bundling it into their software, and distributing it by a physical medium such as DVD Bundling it into their software and delivering it by electronic means from a server (as long as access to the server is protected by an account with adequately secure user name and password): By some mechanism that pushes the software out to customers By allowing customers to download the software Make the document available on its own, by the same mechanisms as above.
View full article
Question: Clarification of what files can be re-distributed to end users? Answer: As far as sharing the toolkit executable or libraries are concerned, we have a detailed section about it in latest version of FNP product document. To be precise Chapter-8 of fnp_devenv.pdf (Development Environment Guide)*(Distributing the FlexEnabled Application for License File–Based Licensing). Similarly for trusted storage based licensing the details is available in Chapter 6(Distributing the FlexEnabled Application for Trusted Storage–Based Licensing). I am attaching a copy of it for your reference.  In general, there are four categories of executables that can be considered for redistribution.  1.) Executables generated from building makefile and makefile.act, minus lmcrypt, preptool and tsreset can be shared  2.) executables that must be redistributed in order for licensing to work (lmgrd or lmadmin, VD and client application, plus lmstat. For TS applications additionally: FNP_Act_Installer.dll (from which FlexNet Licensing Service is installed), activation applications for server and client TS and the libFNP.dll that is the output of prepping.  3.) executables that are generated from example source code provided in the kit. Any of these can be redistributed - if the example is sufficient for producers requirements. Producers are of course fully entitled to modify example source code, then rebuild and produce their own versions of example utilities. Executables in this category include installs.exe and activation applications like app/servercomptranutil.  4.) executables that are typically only redistributed in support scenarios (tsactdiags, tsreset).  Note: installs.exe is a command-line tool used for installing lmgrd as a Windows service, including setting up a dependency on the FlexNet Licensing Service if TS licensing is involved. Alternatives to installs.exe include  lmtools - a windows GUI app - Can be Shared.   
View full article
Question: Over the years, our customers have had  issues with LSB-loader as described in FNP release documentations. Moreover,  on some recent Linux updates, such as SUSE Enterprise Linux 12, the LSB component is not offered as part of the supported distribution. Components in FlexNet Publisher, such as lmgrd, require the LSB-loader. If this is not present, lmgrd will fail to run with a 'file not found' error (FNP-11338, FNP- 11353) Answer: Starting FNP-11.14 tookit, The   install_fnp.sh   will now issue a warning if it detects LSB is not installed on the host: $ sudo ./install_fnp.sh ... Checking LSB compatibility... *** WARNING: 64-bit LSB packages not installed LSB compatibility checks complete ... FNP utilities will continue to give the   File not found   error. Supplying the   --nolsb   flag to the command will cause fake symlinks to be created to mimic the missing LSB installation: $ sudo ./install_fnp.sh --nolsb ... Checking LSB compatibility... *** WARNING: 64-bit LSB packages not installed Fix attempted by creating symlink for /lib64/ld-lsb-x86-64.so.3 LSB compatibility checks complete ... After which FNP utilities should run ok.
View full article
JIRA ISSUE: FNP-11299, FNP-11300, FNP-20479 Issue:  1.) Reservation line is not displaying in server log when RESERVE and MAX are both in options file. 2.) License exceeds count message is coming instead of MAX line in serverlog when both MAX and RESERVE is kept in options file. Workaround: We must place MAX statement before RESERVE in options file for it to work correctly.
View full article
Summary Build Warning -7235 Synopsis When building an InstallShield Express project, the following warning may occur: ISEXP : warning -7235: InstallShield could not create the software identification tag because the Tag Creator ID setting in the General Information view is empty. Discussion By default, software identification tagging is enabled in all Express projects. This applies to new projects created with InstallShield Express, as well as projects that were upgraded from earlier versions of the InstallShield Express Edition.   If you build a release in an Express project without entering data in the required software identification tag setting (the Unique ID, Tag Creator, and Tag Creator ID settings in the General Information view), and you leave software tagging enabled in the project, the build warning -7235 occurs. This build warning explains that the software identification tag could not be created and included in the installation because a specific required setting was left blank. To resolve this warning, enter an appropriate value in each specific setting, or set the 'Use Software Identification Tag' setting in the General Information view to 'No'.   Related Documents Including a Software Identification Tag for Your Product http://helpnet.flexerasoftware.com/isxhelp23/isxhelp23.htm#helplibrary/SWIDOverview.htm
View full article
Summary Error 9510 occurs while building the Windows Installer package. Symptoms Building a release is when you are building Windows Installer package. Cause This build error may be caused if a latest image in the Patch Design view does not have at least one previous image. Workaround To workaround the issue at this point, A latest image must have at least one previous image to create a patch.
View full article
Summary Error 9512 occurs while building the MSIX package. Symptoms Building a release is when you are unable to add file [File Name] to package. Cause This build error may be caused while adding the specified file to the MSIX package. Workaround To workaround the issue at this point, The specified file should exist on the system and there is enough disk space available.
View full article
Summary Error 9552 occurs while building the MSIX package. Symptoms Building a release is when an unexpected error displays MSIX App file entry. Cause This build error may be caused while adding payload file/folder to the MSIX package. Workaround To workaround the issue at this point, Check whether the source files exist in the system during the build.
View full article
Summary Error 9553 occurs when while building the MSIX app package. Symptoms Building a release is when the file type association for extension [extension] does not contain any 'open' verbs but does contain other verbs. Cause This build error may be caused by an open verb that is included as MSIX app packages force at least open to be supported. Workaround To workaround the issue at this point, Add and 'open' verb in the File Association.
View full article
Summary Error 9556 occurs while building the package. Symptoms Building a release is when you are unable to locate the Windows 10 SDK. Cause This build error may be caused by unavailability of Windows 10 SDK. Workaround To workaround the issue at this point, Check whether Windows 10 SDK is installed in the system, if not, install Window 10 SDK.
View full article
Summary Error 9557 occurs while creating resources.pri. Symptoms Building a release is when you are unable to create resources.pri. Without resources.pri, the scaled logos cannot be used. Cause This build error may be caused by unavailability of Windows 10 SDK. Workaround To workaround the issue at this point, Check whether Windows 10 SDK is installed in the system, if not, install Window 10 SDK.
View full article
Summary Error 9558 occurs when the Server Extension is not included while building the UWP app package. Symptoms Building a release is when this MSI includes [Count of service] NT services. But, the built UWP app package will not include them as the package does not include the Server target. Cause This build error may be caused is when the MSI has NT services enabled, but the UWP app package doesn't have the server target support enabled. Workaround To workaround the issue at this point, Enable the server extensions and further update to its version details in Releases->Release-Name->APPX/MSIX->Include Server Extension
View full article
Summary Error 9559 occurs while setting the NT Service Name. Symptoms Building a release is when the NT service [Service Name] uses an unsupported startup account [Account], skips this service since no appropriate default account is available. Cause This build error may be caused when the added service doesn't have a startup account which may come as any one of the below: LocalSystem NetworkService LocalService Workaround To workaround the issue at this point, check the service you added. Any service should always have the proper properties like Path, Startup Account, Type, Error Control, Start Type, etc.
View full article
Summary Error 9560 occurs while setting the NT Service Name. Symptoms Building a release when the NT service [Service Name] uses an unsupported startup user action error control option (SERVICE_ERROR_CRITICAL) Cause This build error may be caused is when the added service doesn't have proper error control which can be either NORMAL or IGNORE type. Workaround To workaround the issue at this point, check the service you added. Any service should always have the proper properties like Path, Startup Account, Type, Error Control, Start Type, etc.
View full article
Summary Error 9561 occurs while setting the NT Service Name. Symptoms Building a release is when the NT Service [Service Name] is set to start in an unsupported way. Cause This build error may be caused when the added service doesn't have valid start type. Workaround To workaround the issue at this point, check the service you added. Any service should always have the proper properties like Path, Startup Account, Type, Error Control, Start Type, etc.
View full article
Summary Error 9568 occurs while setting the Web Account Provider declaration. Symptoms Building a release is managed URL ‘%1’ specified is a duplicate of the base URL specified for the Web Account Provider Declaration. Cause This build error may be caused by one of the Managed URL which is a duplicate with the base URL specified for the Web Account Provider Declaration. Workaround To workaround the issue at this point, Specify a unique Managed URL in the Web Account Provider Declaration.
View full article
Summary Error 9569 occurs while setting the Shared Target declaration. Symptoms Building a release requires at least one supported File type or Data format. Cause This build error may be caused by Share Target Declaration which requires to specify at least one supported File type or Data. Workaround To workaround the issue at this point, Select 'Supports any File type' or explicitly to add one or more File types or Data formats in the Share Target Declaration.
View full article
Summary Error 9564 occurs when the module [COM Module Name] contains the COM data. Symptoms Building a release is when this COM server will not be activatable outside the Appx package. Cause This build error may be caused by a specified COM server that will not be activatable outside of this Appx package as all its registry entries and extension points are in its private hive and not exposed publicly to the system. Workaround To workaround the issue at this point, if your application uses COM only for its own personal use, then you can ignore this warning and rely on COM entries in the application’s private hive (Registry.dat) to support your app. All binaries in the same appx\msix package have access to that registry, but any other apps on the system cannot see into your app’s private hive.
View full article
Summary Error 9566 occurs while setting a declaration. Symptoms Building a release is when the executable ‘%1’ defined for declaration element does not exist in the package. Cause This build error may be caused by the custom executable specified for the declaration is not found in the package. Workaround To workaround the issue at this point, Redefine with the correct executable or add the executable to the package.
View full article