Symptoms: When FNMS is working with Microsoft Server SQL Server 2019 version, they might receive the follow error message: System.InvalidOperationException: Memory optimized tables and natively compiled modules cannot be accessed from within SQLCLR stored procedures. Analysis: SQL Server 2019 (15.x) introduces a new feature that's part of the in-memory database feature family: memory-optimized tempdb metadata. When this feature is enabled, the system tables involved in managing temporary table metadata can be moved into latch-free, non-durable, memory-optimized tables. However any memory optimized tables and natively compiled modules cannot be accessed from within SQL CLR stored procedure, and therefore causing compatible issue with FNMS. User may see the error message listed above during some data activities such as during data warehouse export process. Solution: When using SQL Server 2019, please ensure the cumulative update package 5 for SQL Server 2019 or later is installed. Disable TempDB_Metadata using any of the following commands and then restart the SQL Server. --Option 1: ALTER SERVER CONFIGURATION SET MEMORY_OPTIMIZED TEMPDB_METADATA = OFF GO --Option 2: EXEC sp_configure 'tempdb metadata memory-optimized' , 0 GO RECONFIGURE GO   ... View more

Symptoms: This KB article will provide a way to help customers who experiences the following error message after they restored a VM to a previous check point where the Business Adapter Studio was running on it with encryption option ticked. ERROR: MGSBI.XML has not been successfully encrypted. The type initializer for 'ManageSoft.CryptographerSelector' threw an exception.   Cause: VM restoration sometimes caused changes of some characteristic of the underlying VM hardware that the VM is bound to, so it generates different crypto info.   Solution: Open up the Windows Registry at the following path: HKLM\Software\Wow6432Node\ManageSoft Corp\ManageSoft There is a value name called MGSBI, rename it to “MGSBI_Backup” Then next time when MGSBI runs, a new key at the same path will be created, and should resolve the error, however the user may have to recreate the import profile with encryption option due to the key changed. ... View more

Symptoms: This KB article will provide an alternative to help customer who has a lot of child beacons and discovery rules, which may generate a massive amount of activity log files waiting for upload, and holds up inventory upload.   Workaround: Open Windows task scheduler, click on Flexera Inventory Beacon folder on the left panel. Duplicate the existing task called “Upload Flexera logs and inventories” with a new task name, so now we have two upload tasks. In the newly created task, right click and choose property, find the Actions tab, edit the action, in the Add arguments textbox, change it to “-o uploadRule=ActivityStatus -t machine”, so from now on this task will only upload Activity logs. Open up the existing “Upload Flexera logs and inventories” task, edit the argument to “-o uploadRule=Inventory -t machine”, this set the task to only perform inventory files upload.   Additional Information The above change will result as two scheduled task which only uploads Inventory files and Activity log files, and both can run in parallel and not holding up each other. The default setting in the argument “-a -t Machine” is doing everything by the single task. Extra rule names can be viewed in the following registry path: HKML\Software\WOW6432Node\ManageSoft Corp\ManageSoft\Common\Rules ... View more