Description When viewing the All Licenses view at different times, the column order or the grouping filter is not retained. This affects custom fields rather than out-of-box columns. Replication Scenario Create more than one custom field in license property pages. In the All Licenses view, select a custom field to be grouping value. Navigate away from the page and return. Workaround Hotfix attached for FNMS 2020 R1 Please back up the file below before replacing it with the one attached. <Install location>\FlexNet Manager Platform\WebUI\bin\Flexera.Web.Logic.dll   Resolution Fixed in FNMS 2020 R2 for cloud and premise. ... View more

Description When adding additional applications to a custom metric bundled license created from an existing SKU, the application remains unlicensed and will show up in the Unlicensed Installation view. Replication Scenario Process a SKU to generate a custom metric type license and add additional applications to be covered. The application shows up in the Unlicensed Installations view even after the device it was installed on was allocated to the custom metric license. Workaround Create a different license to cover the additional applications.   Resolution The bug is reported under  IOJ-2125500. No release ate is available yet. ... View more

Description The "hosted in" field of Oracle instances is showing "On-premises" instead of following what the host has. This is just a UI display bug and does not impact the license calculation. Replication Scenario Instances are showing the default value for the "hosted in" field, which is "On-premises".  Any instances in the UI should show the same "Hosted in" as the host. There is a bug in the grid query where it is not getting the cloudserviceproviderID of the host computer of the instance, and if cloudserviceproviderID is null, it will default to "On-premises".  Workaround No workaround is available. Resolution The bug is reported under  IOJ-2159924. Currently, there is no target date yet. ... View more

Description When attempting to delete a beacon in disabled status in the Beacons view, a red bar error occurs. The beacon remains undeleted.   Workaround Change the beacon status before attempting to delete. Or Run the query below on the compliance database with the name of the beacon that needs to be removed. DELETE FROM Beacon WHERE BeaconName = '<nameofbeacon>'     ... View more

Description If an inventory is updated with a nondefault role, the inventory does not consume any license. This is due to an incorrectly populated flag in the database. This can be confirmed with the query below: select * from ComplianceComputerRole where DefaultValue='<EnterRoleNameHere>' If ManageLicenses does not have value of 1, the device with this role will not consume licenses.   Workaround Run the query below to enable consumption on the the devices with the custom role. update ComplianceComputerRole Set ManageLicenses=1 where DefaultValue='<EnterRoleNameHere>' A reconcile is needed after to calculate consumption.   Resolution The issue will be fixed by Engineering with bug  IOJ-2094595. ... View more

Symptoms: When navigating to Inventory Evidence tab of the discovered device record, there is no evidence showing. The source of the inventory was from agent. Diagnosis: There is an incorrect connection string to the Inventory Database. Solution: Confirm that the registry value below is correctly pointed to the Inventory Database on both the web and batch server: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft corp\ManageSoft\Reporter\CurrentVersion\InventoryDatabaseConnectionString Confirm that the Server and DatabaseName column from the query result is correct. Please execute on the Compliance Database. SELECT * from ComplianceConnection where SourceType='ManageSoft' ... View more

Symptoms: When importing source data with Microsoft Office format data, the error message below appears: "The MicrosoftAce.OLEDB.12.0 provider is not registered on the local machine" Diagnosis: A prerequisite for the software is missing. Solution: Download and install the 32bit version of Microsoft Access Database Engine 2010 Redistributable. https://www.microsoft.com/en-us/download/details.aspx?id=13255 ... View more

Symptoms: With SCCM import, the reconcile fails with an error similar to the one below: Failed to execute Reader 'GetUniversalApplicationInstalledInstallerEvidence-CreateIndexes' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Reader\sms\InstallerEvidence.xml, at step line 2 Error: Operation failed. The index entry of length 910 bytes for the index 'IX_InstallerEvidence' exceeds the maximum length of 900 bytes. Warning! The maximum key length is 900 bytes. The index 'IX_UniversalInstalledInstallerEvidence' has maximum length of 1056 bytes. For some combination of large values, the insert/update operation will fail. Warning! The maximum key length is 900 bytes. The index 'IX_InstallerEvidence' has maximum length of 1056 bytes. For some combination of large values, the insert/update operation will fail. The statement has been terminated. Diagnosis: This is due to  the combined string of the installer evidence, version, and publisher being too long. This usually occurs if the any of the above values are modified or the installation was repackaged. Solution: This issue has bee resolved in FNMS 2019 R2.3. Workaround: The queries below can be used on the SCCM database to identify which entry and machine this evidence is coming from. If possible, please remove the evidence. If it is modified from the default value, there is a high chance this will not map to any existing entry in the library. SELECT DATALENGTH(DisplayName0) + DATALENGTH(Version0) + DATALENGTH(Publisher0), c.name00, arpd.* FROM dbo.v_GS_ADD_REMOVE_PROGRAMS AS arpd LEFT OUTER JOIN Computer_System_data AS c ON c.MachineID = arpd.ResourceID WHERE DATALENGTH(DisplayName0) + DATALENGTH(Version0) + DATALENGTH(Publisher0) > 900 SELECT DATALENGTH(DisplayName0) + DATALENGTH(Version0) + DATALENGTH(Publisher0), c.name00, arpd.* FROM dbo.v_GS_ADD_REMOVE_PROGRAMS_64 AS arpd LEFT OUTER JOIN Computer_System_data AS c ON c.MachineID = arpd.ResourceID WHERE DATALENGTH(DisplayName0) + DATALENGTH(Version0) + DATALENGTH(Publisher0) > 900 ... View more

Summary On the Project Assignment view, no imported users show up for selection. Symptoms When trying to assign an user to a workflow through the AdminStudio Process Assistant, none of the imported users show up. As a result, the process cannot be completed. Cause Setting in the web.config file is hiding all the users in the Project Assignment view. Steps To Reproduce 1. Launch the AdminStudio IDE and click on the Process Assistants tab. 2. Right click in the left window pane and choose "Create a new project". The New Workflow Project Wizard appears. 3. Click Next on the Welcome dialog. 4. Choose a Workflow template and click Next. 5. Leave the Source Package field blank and click Next. 6. Leave the Target Directory and Target Filename blank and click next. 7. On the Project Assignment screen, the list of "AdminStudio Application Catalog Users" is blank and the Finish button is disabled. Resolution In the Web.config file located in the wwwroot subfolder of the Workflow Manager installation , change the value of "ShowOnlyAssignedUsersInAS" to "0". The file is located at C:\WorkflowManager\wwwroot by default. ... View more

Summary Error 7354 occurs when building MSI project with entries in the MoveFile table. Symptoms Error 7354 occurs when building MSI project with entries in the MoveFile table using Installshield. ISDEV : error -7354: The English (United States) value for string 'ID_STRING2' does not contain a legitimate value for table MoveFile column SourceName Cause The SourceName column in the MoveFile table should be a Text data type and should not be validated. There is a bug in IS2016 that is trying to validate the value. Steps To Reproduce Create BMSI Add a sample file in Files and Folder view Navigate to MoveFile table Add "SampleKey" for FileKey file Add "AllOtherFiles" for Component_ Add "SourceFile.exe" for SourceName column Add "SOURCE~1|SourceFile.exe" for DestName column Add "INSTALLDIR" for SourceFolder column Add "INSTALLDIR2" for DestFolder column Add "1" for Options column Build project Resolution Backup the ISWIBuild.dll file at C:\Program Files (x86)\InstallShield\2016\System\ Extract the attached file to that location Restart InstallShield and try building again Additional Information The issue is tracked internally under the Work-Order# IOJ-1774403 and the hotfix issued will be included in the future releases of InstallShield. The download of InstallShield 2016 was updated on 9/8/2016 to include this hotfix, the updated version number for ISWIBuild.dll is 23.0.0.290 ... View more