Description The queries used to determine active users from Oracle EBS are not taking expired responsibility into account and users bound to the expired responsibility consume the license. Replication Scenario Check if there are expired responsibilities on the Oracle EBS. Workaround Remove expired responsibility from the EBS system. Alternatively, it is possible to manually override/exempt the consumption to account for this. Fix status This issue is under consideration to be addressed in a future FlexNet Manager Suite release. Other information Affected components: SAM for Oracle, Software license management Master issue ID: IOJ-2093927 Also known as: FNML-76688 ... View more

Summary License consumption for virtual machines belonging to resource pools may not consume most license types (except for IBM PVU licenses) when using FlexNet Manager Suite 2022 R2. Cause This issue is caused by a logic error when processing details of virtual machines belonging to resource pools. Mitigation This issue can be avoided by installing the Hotfix 1 for FlexNet Manager Suite 2022 R2. See the following post for details: Hotfix for FlexNet Manager Suite 2022 R2. See also Also see the following issue which is similar to this one: License consumption for SQL Server Standard Edition may be 0 (despite calculated consumption being accurate) for virtual machines belonging to resource pools (IOK-1006447). Fix status This issue is planned to be addressed in the following future FlexNet Manager Suite releases: 2022 R2.1 / Jan 2023 (Cloud), 2023 R1 (On Premises) Other information Affected components: Software license management Master issue ID: IOK-1007075 Also known as: FNML-77405 ... View more

Summary License consumption calculated for SQL Server Standard Edition may be shown as 0 on the Consumption tab of a license when it should be non-0 for virtual machines belonging to resource pools when using FlexNet Manager Suite 2022 R2. This is despite the total calculated consumption for the license record being accurate. Cause This issue is caused by a logic error when processing details of virtual machines belonging to resource pools. Mitigation This issue can be avoided by installing the Hotfix 1 for FlexNet Manager Suite 2022 R2. See the following post for details: Hotfix for FlexNet Manager Suite 2022 R2. See also Also see the following issue which is similar to this one: Virtual machines belonging to resource pools may not consume licenses (IOK-1007075). Fix status This issue has been fixed in the following FlexNet Manager Suite release: 2022 R2 / Nov 2022 (Cloud) This issue is planned to be addressed in the following future FlexNet Manager Suite release: 2023 R1 (On Premises) Other information Affected components: Software license management Master issue ID: IOK-1006447 Also known as: FNML-77401 ... View more

Summary Logging produced by the ServiceNow export process fnmp_servicenow_export.exe contains only start and end time information, with no other information about what the export process is actually doing. Cause This behavior is due to an incomplete introduction of a new logging subsystem in the FlexNet Manager Suite 2022 R2 release. Mitigation This issue can be avoided by installing the Hotfix 1 for FlexNet Manager Suite 2022 R2. See the following post for details: Hotfix for FlexNet Manager Suite 2022 R2. Fix status This issue is planned to be addressed in the following future FlexNet Manager Suite releases: 2022 R2.1 / Jan 2023 (Cloud), 2023 R1 (On Premises) Other information Affected components: Integration: ServiceNow Master issue ID: IOK-1004513 Also known as: FNML-77312 ... View more

Summary When the Config.ps1 script is run to configure a FlexNet Manager Suite 2022 R2 application server, it may fail with output showing the following error message: [...] 2022-12-13 14:13:49,511 [Release.InstallActions] [INFO ] - Rebuild Reports to set and configure details for API use. 2022-12-13 14:13:50,419 [se.PostInstall.Program] [ERROR] ============================================================ 2022-12-13 14:13:50,419 [se.PostInstall.Program] [ERROR] ConfigureSystem has encountered an unexpected error System.Data.DBConcurrencyException: DB concurrency violation. at ManageSoft.Compliance.Logic.Core.Impl.SearchUserDefined.EnsureSearchCompiled(Int32 p_SavedSearchID) at ManageSoft.Compliance.Release.PostInstall.RebuildReport.Run(String tenantUID) at ManageSoft.Compliance.Release.InstallActions.<>c__DisplayClass6_0.<RunInstallActionsByGroup>b__0(String tenantConnectionString, ITenantInfo tenantInfo) at Flexera.Broker.Connections.Impl.TenantActions.WithTenant(ITenantInfo tenant, ConnectionType type, Action`2 tenantAction) [...] Mitigation This issue can be avoided by installing the Hotfix 1 for FlexNet Manager Suite 2022 R2 before running the Config.ps1 script. See the following post for details: Hotfix for FlexNet Manager Suite 2022 R2. Fix status This issue is planned to be addressed in the following future FlexNet Manager Suite release: 2023 R1 (On Premises) Other information Affected components: Component installers Master issue ID: IOK-1004392 Also known as: FNML-77309 ... View more

Summary The WriteInstalledFileEvidenceAttribute inventory import writer step may run for a long time, and even eventually terminate with a timeout error when using the FlexNet Manager Suite 2022 R2 release. Details This issue is caused by a SQL database query that can perform poorly under certain conditions. Logging like as the following will be produced by the import process when this step fails with a timeout error: 2022-11-29 06:51:08,931 [INFO ] WriteInstalledFileEvidenceAttribute 2022-11-29 14:51:12,135 [INFO ] Failed to execute Writer 'WriteInstalledFileEvidenceAttribute' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\\Writer\FileEvidence.xml, at step line 1 Error: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Mitigation This issue can be avoided by installing the Hotfix 1 for FlexNet Manager Suite 2022 R2. See the following post for details: Hotfix for FlexNet Manager Suite 2022 R2. Fix status This issue is planned to be addressed in the following future FlexNet Manager Suite releases: 2022 R2.1 / Jan 2023 (Cloud), 2023 R1 (On Premises) Other information Affected components: Inventory import (read/write/export), SAM for Oracle Master issue ID: IOK-1000422 Also known as: FNML-77162 ... View more

Summary Attempting to open an adapter XML file in the Business Adapter Studio fails with the following error if the HKLM\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\MGSBI registry entry contains cryptographic data that cannot be processed: Import file definition […] cannot be loaded: The type initializer for ‘Flexera.BusinessImport.CryptographerSelector’ threw an exception. Workaround Delete the HKLM\SOFTWARE\WOW6432Node\ManageSoft Corp\ManageSoft\MGSBI registry entry. Open any adapters that have encrypted connection string details, and re-enter the connection strings. (Encrypted details in adapters will unrecoverable once the MGSBI registry entry becomes invalid or is deleted.) Additional details This issue may occur if the Business Adapter Studio is installed on a virtual machine that has been cloned or restored from a snapshot, or has had some other operation performed that invalidates cryptographic information on the computer. Also see the following article which describes a similar (but slightly different) error message and scenario: Known Issue: Business Adapter Studio or MGSBI.exe fails to encrypt source connection details with error when running without administrator rights: "The type initializer for 'Flexera.BusinessImport.BusinessImporterCryptographer' threw an exception" (IOJ-1720238) Fix status This issue is still open but not currently scheduled to be addressed. Other information Affected components: Business adapters Master issue ID: IOK-1009299 Also known as: FNML-77564 ... View more

Summary If the display name of installer evidence gathered by the FlexNet inventory agent in both inventory and usage data ends with a version number, usage data associated with that evidence may not be imported by the inventory import process. This will result in recognized installations of the application not being identified as used, even if raw usage data (on the Raw Software Usage page) shows usage. Details This behavior occurs due to differences in the process of installer evidence received from managed devices in inventory data and usage data. A version number that appears at the end of the display name property of installer evidence may (depending on various conditions) be removed when it is stored in the inventory database. This issue arises because the exact conditions when a version number is removed vary between usage data and inventory data. When a version is removed for one type of data but not the other type of data, the usage and inventory data cannot be reconciled, leading to the usage data not being imported. As an example, consider the following details that may appear in an inventory NDI file: <Package Name= "MindView 7.0" Version= "7.0.18668.0" Evidence= "MSI" > When this application is used, details such as the following appear in the usage MMI file: <APPUSAGE NAME= "MindView 7.0" VERSION= "7.0.18668.0" FILENAME= "MindView.exe" FILECOMPANY= "MatchWare A/S" FILEDESCRIPTION= "MatchWare MindView" FILEPRODUCTNAME= "MatchWare MindView" FILEPRODUCTVERSION= "7.0.18668" FILEVERSION= "7.0.18668" LONG_FILENAME= "C:\Program Files (x86)\MatchWare\MindView 7.0\MindView.exe" TOTALRUNTIME= "120" TOTALACTIVE= "0" SESSIONS= "1" DAYS= "3" /> In this situation: Installer evidence associated with the inventory data will be transformed and stored with the name “MindView”. However, installer evidence associated with the usage data will be stored with the name “MindView 7.0”. Because the names as stored do not match, the usage data does not get imported. Workaround An approach to workaround this issue is to ensure a file recognition rule that matches the executable file identified in the usage is associated with the relevant application in the application recognition library (ARL). Details required for the file recognition rule can be obtained from the Raw Software Usage page. A file recognition existence rule of “Not for recognition”, “At least one” or “Required” can be used (depending on if and how the file should be used to recognize installations of the application). For example, to recognize usage for the MindView example shown above, a file evidence recognition rule with the following properties could be linked to the MindView 7 application: File name = MindView.exe Version = 7.% Company = MatchWare A/S Description = MatchWare MindView Existence rule = Not for recognition Fix status This issue is under consideration to be addressed in a future FlexNet Manager Suite release. Other information Affected components: Uploaded file importers, Usage Master issue ID: IOK-1007093 Also known as: FNML-77524 ... View more

Summary When FlexNet Manager Suite is upgraded to 2022 R1 or later and Microsoft SQL Server was upgraded to SQL Server 2017 or later, the following error may occur: Running cm-migr1300-ComplianceSchema.sql...100%     Running cm-migr1300-CompliancePreCLRInstall.sql...50%         There was an error while attempting to run 'cm-migr1300-CompliancePreCLRInstall.sql'.         An error occurred in the Microsoft .NET Framework while trying to load assembly id 65538. The server may be running out of resources, or the assembly may not be trusted. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error:         System.IO.FileLoadException: Could not load file or assembly 'sqlproceduresclr, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An error relating to security occurred. (Exception from HRESULT: 0x8013150A)         System.IO.FileLoadException:            at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)            at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)            at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)            at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)            at System.Reflection.Assembly.Load(String assemblyString) Diagnosis The issue occurs because the older versions of SQLProceduresCLR.dll are signed with an older Flexera code signing certificate which is now expired. The newer versions are signed with an updated certificate, which the customer may have already imported into the database server. Since the old certificate may not exist in the database, the SQL Server treats that assembly as "not secure" and it does not allow the installation. Solution / Workaround The solution is to add the old certificate to the database. This needs the old as well as the new code signing certificates in the database, so that the migration runs successfully. If only the latest Flexera code signing certificate is imported on the database server: Download the Old Flexera Signed Security Certificate 2021 for SQL Server 2017 and 2019.zip and follow the steps mentioned in the readme.txt. If no Flexera code signing certificate is imported on the database server: Download the All Flexera Signed Security Certificates for SQL Server 2017 and 2019.zip and follow the steps mentioned in the readme.txt. Fix status This issue is under consideration to be addressed in a future FlexNet Manager Suite release. Other information Affected components: Database Master issue ID: IOK-1001941 Also known as: FNML-77237 ... View more

Summary The “Snapshot Optimization_Snapshot_FACT data” step of data warehouse export processes may fail with output in the export log file similar to: 2022-12-30 14:40:14,078 [INFO ] Snapshot Optimization_Snapshot_FACT data 2022-12-30 14:40:14,078 [INFO ] Failed to execute Exporter 'Snapshot Optimization_Snapshot_FACT data' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Exporter\fnmpdatawarehouse\MetricDataExport.xml, at step line 6 Error: Conversion failed when converting date and/or time from character string. LatestSnapshotDate : 30/12/2022 0:00:00 Cause This issue is caused by a logic error handling date values with various regional settings the use different date formats. Mitigation An internal configuration setting can be set to skip the problematic part of the export process. This can be done by executing the following SQL statement against the data warehouse database: UPDATE cts SET SettingValue = '0' FROM dbo.ComplianceTenantSetting cts JOIN dbo.SettingName sn ON sn.SettingNameID = cts.SettingNameID WHERE sn. Name = 'KPIDataExport' The impact of changing this configuration setting is that data required for the SAM Optimization Hub introduced in the 2022 R2 release will not be processed, so this functionality will not be able to be used. Affected versions This issue affects FlexNet Manager Suite 2022 R2. Fix status This issue is planned to be addressed in the following future FlexNet Manager Suite releases: 2022 R2.1 / Jan 2023 (Cloud), 2023 R1 (On Premises) Other information Affected components: Inventory import (read/write/export), Software license management Master issue ID: IOK-1005577 Also known as: FNML-77334 ... View more

Summary When inventory data is uploaded from a beacon to a FlexNet Manager Suite (on premises) application server, a process to perform a full inventory import (including running the “writers” phase of the import) is initiated. This process is run in addition to the full inventory import process that (by default) runs each night. Mitigation It may be preferable to have a full import process only executed once per day, and not whenever inventory data is uploaded from a beacon. It is possible to configure FlexNet Manager Suite so that when inventory data is uploaded from a beacon the data will only be staged in the database for subsequent processing the next time the inventory import process runs. This can be configured by running the following query against the compliance database: UPDATE cts SET SettingValue = '0' FROM dbo.ComplianceTenantSetting cts JOIN dbo.SettingName sn ON sn.SettingNameID = cts.SettingNameID WHERE sn. Name = 'PackageUploadTriggersWriters' Fix status This issue is under consideration to be addressed in a future FlexNet Manager Suite release. Other information Affected components: Inventory import (read/write/export) Master issue ID: IOK-1004611 Also known as: FNML-77313 ... View more

Summary An incorrect device version can appear in the Last Reported Version column of the FlexNet Inventory Agent Status page if there are multiple records for the same device. Multiple records can occur for various reasons but often originate from data inconsistencies or inaccurate data cleanup.  Troubleshooting To investigate this issue in a FlexNet Manager Suite system, you can review details in your compliance database and remove any outdated records for a device. Use the query below to troubleshoot the information displayed on the FlexNet Inventory Status page (Discovery & Inventory > FlexNet Inventory Agent Status). This query provides the data that generates the information you see on the status page. SELECT TOP 1 WITH TIES ist.ComplianceComputerID, ic.AgentVersion as 'VersionName' , ist.InstallDate FROM dbo.InstalledSoftware AS ist INNER JOIN SoftwareTitle AS st ON st.SoftwareTitleID = ist.SoftwareTitleID LEFT OUTER JOIN dbo.ImportedComputer ic ON ist.ComplianceComputerID = ic.ComplianceComputerID WHERE st.FullName LIKE 'FlexNet Inventory %' AND ic.InventoryAgent = 'FlexNet Manager Suite' You can adjust the query to locate records for a particular device name, as shown below. In this example, the query searches for agentmachine001. SELECT ist.ComplianceComputerID, ic.ComputerName, ic.AgentVersion as 'VersionName' , ist.InstallDate FROM dbo.InstalledSoftware AS ist INNER JOIN SoftwareTitle AS st ON st.SoftwareTitleID = ist.SoftwareTitleID LEFT OUTER JOIN dbo.ImportedComputer ic ON ist.ComplianceComputerID = ic.ComplianceComputerID WHERE st.FullName LIKE 'FlexNet Inventory %' AND ic.InventoryAgent = 'FlexNet Manager Suite' AND ic.computername = 'agentmachine001' For more information on the FlexNet Inventory status page, see the help article FlexNet Inventory Agent Status . Fix status This issue has been fixed in the following FlexNet Manager Suite releases: 2020 R1.1 / Sep 2020 (Cloud), 2020 R2 (On Premises) Other information Affected components: Inventory, Web UI Master issue ID: IOJ-2125525 Also known as: FNML-71094 ... View more

Symptoms Misleading error events related to gathering inventory for Oracle products may appear in the "ManageSoft" event log on Windows when inventory is gathered. Details When the inventory agent runs to gather inventory on Windows devices, error events with messages that relate in some way to gathering data about Oracle products may be reported in the “ManageSoft” event log. An example of a message that may appear in these events is: FusionMW: Copying [...] to stage as [...] Despite being reported with an event level of "Error", these messages to not actually indicate an error has occurred unless text clearly describes something that is an error in nature. The messages can generally be ignored. Related information Also see the following issue which is similar but covers other types of messages: Misleading error events about cloud server provider metadata, IBM DB2, and Toad for Oracle may appear in the "ManageSoft" event log when gathering inventory (IOJ-2231885). Fix status This issue is planned to be addressed in the following future FlexNet Manager Suite releases: 2022 R2.1 / Jan 2023 (Cloud), 2023 R1 (On Premises) Other information Affected components: Agent, Inventory, SAM for Oracle Master issue ID: IOK-999048 Also known as: FNML-77136 ... View more

Description Installations of applications that are linked to a license of type Custom Metric are shown in the Unlicensed Installations view. Replication Create a license of type Custom Metric, and add additional an application that is installed on an inventory device to the license. The installation is shown in the Unlicensed Installations view. This occurs regardless of whether the device is explicitly allocated to the custom metric license. Workaround Create another license to cover the application installations. Appropriate license types to use might include Device, Enterprise or Site. Add comments on the license to make it clear that the license record is not relevant from the perspective of calculating consumption, but is purely used to indicate that the installations are licensed and so they do not continue to be reported on the Unlicensed Installations page. Fix status This issue is still open but not currently scheduled to be addressed. Other information Affected components: Software license management Master issue ID: IOJ-2125500 Also known as: FNMS-68836 ... View more

Summary A red error bar message pops up in the web UI if the first HTTP request made by the web UI after a SAML session timeout occurs is an AJAX request (that is, not a full page refresh or load). Details When this issue occurs, logging like the following appears in the webui.log file on the web application server of a FlexNet Manager Suite system: [ERROR 2022-10-20 10:28:08,380 1171692ms b.Core.UnhandledErrors ] An unexpected error occurred (fbd86865-b905-4b05-8b67-820d0f68863a) ManageSoft.Compliance.ComplianceException: Access rights not initialized. Do not do access right checks in constructors or setters. at ManageSoft.Compliance.Logic.Core.API.ComplianceRightsInstance.EnsureRightsInitialized() [...] Mitigation When this issue occurs, the login session can be reauthenticated by refreshing the page in the browser or navigating to another page. Fix status This issue is still open but not currently scheduled to be addressed. Other information Affected components: SAML, Web UI Master issue ID: IOK-993495 Also known as: FNMS-76474 ... View more