About WheresThePizza

WheresThePizza · ‎Apr 07, 2021

Symptoms: When using SQL Server 2016 SP2 CU16 (13.0.5882.1) to host the FNMS databases, you may start to see inventory import and license reconcile tasks failing with the error Execution Timeout Expired. This will always timeout regardless of the timeout limit set in the environment, and you will see errors like the following in the importer.log from the inventory import and license reconcile: Failed to execute Writer 'WriteComputers - set calculated user' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Writer\Computer.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. Failed to execute Writer 'MatchAccessingDevice' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Writer\AccessEvidence.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. Updating License compliance status based on new install counts. 2021-03-30 03:12:41,043 [ERROR] System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Data.SqlClient.SqlException: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> System.ComponentModel.Win32Exception: The wait operation timed out Diagnosis: This is caused by a bug in SQL Server 2016 SP2 CU16 (13.0.5882.1), that has been addressed in SQL Server 2016 SP2 CU17 (13.0.5888.11) Solution: To resolve this issue, you will need to apply CU17: KB5001092 - Cumulative Update 17 for SQL Server 2016 SP2

WheresThePizza · ‎Apr 07, 2021

If you do not see the settings, you need to open a support case to get the steps to enable the settings, as this is not something that can be published in the article. This is mentioned towards the bottom of the article: If you do not see these settings in the Admin Console, please open a support case for Flexera support to assist with getting access to these settings.

WheresThePizza · ‎May 11, 2020

I would not expect there to be any issues. In terms of the licensing, a server is just a device that is identified by the server OS. I would expect the license to still have 'devices' available that could be used by the EUC. You can verify what you have available in the FlexNet Manager Suite License page /Suite/YourFNMPLicense/Index This will show what you have available on your license. If you have devices available, then your standard OS devices should count against this total.

WheresThePizza · ‎Apr 23, 2020

FNMS Analytics from Cognos will only work with the version that it ships with. I believe the current plan for FNMS On-Premises is to include 11.0.13 with the next on-prem release, which should be FNMS 2020 R1. Unfortunately, I am not aware of what the current ETA for the release of this.

WheresThePizza · ‎Apr 13, 2020

I would first ensure that you have everything setup. We have this KB article along with the adapters reference that covers this. This is what I would refer to for best practice when setting up and using these adapters. There should be several diagrams that cover the different ways this can be implemented, and what data is gathered: https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/How-to-Inventory-Citrix-XenDesktop-and-XenApp-using-FlexNet/ta-p/122531 https://docs.flexera.com/fnms/EN/WebHelp/PDF%20Documents/Cloud/FNMSInvAdaptersAndConnectorsReference.pdf As far as validating the data this is something that you will need to ensure that you are seeing applications being recognized for users that are using them, and they you are seeing licensing being consumed as expected for the sample set you decide to use to validate the inventory. Hope this helps!

WheresThePizza · ‎Mar 25, 2020

It appears that you already have a case with support that you are working on this. It would appear that the difference in data is the result of an error during the migration scripts execution. Since you already have a support case for this, it would be best to continue to work through that.

WheresThePizza · ‎Feb 12, 2020

You can also run the executable responsible directly, sometimes this will give a much better output than the logs and we do often recommend this for troubleshooting. This would just involve running MgsImportRecognition.exe, without any switches. This will be located by default in: C:\Program Files (x86)\Flexera Software\FlexNet Manager Platform\DotNet\bin

WheresThePizza · ‎Feb 12, 2020

The SoftwareTitle table will contain information about any software being managed by FNMS. This would come from our ARL, as well as local applications. In this regard, this table should be updated anytime something is updated from ARL, you create a local application, or modify a local application. If you are talking about the standard reporting (not Analytics powered by Cognos), these details should be able to be reported on using "Application", as well as some others, possibly "Assigned license". If you are using Analytics then I believe this data should be accessible in one of the data models. For more information on the tables and the Analytics data models, I would suggest checking out the schema reference we have: https://helpnet.flexerasoftware.com/FlexNetManagerSuite2019R2/EN/WebHelp/PDF%20Documents/On-Prem/FNMSSchemaReference.pdf

WheresThePizza · ‎Feb 12, 2020

I completely agree that the best approach would be to do a migration of the OS instead of an in-place upgrade, and doing a clean install of FNMS on the new server. Doing this would also allow you to keep FNMS up and running, and could remain running if any issues were faced in the migration.

WheresThePizza · ‎Feb 12, 2020

You can find logs on the App server/batch processor by default in %ProgramData%\Flexera Software\Compliance\Logging\Content The logs in here could give some insight into what is causing the problem. Depending on exactly where it is at in processing, it may not be the cleanest task to kill. You can see if there is anything being processed by the batch processor with .\BatchProcessTaskConsole.exe list-tasks ( located by default in C:\Program Files (x86)\Flexera Software\FlexNet Manager Platform\DotNet\bin). The scheduled process is being run through the shodowhost.exe, and there could be more than one task being run from this. If this was previously working fine, then I would check a few things that could impact this, like if security software may be involved, like an AV scan occurring during this task. If it is at the stage that it is writing to the DB, then it could also be a performance issue on the SQL server, especially if other jobs are running at that time.

WheresThePizza · ‎Feb 06, 2020

If you are referring to scheduling the InventoryScanner, this would just be something that you should be able to do through a scheduled task (if we are talking Windows). The main advantage of the InventoryScanner is that it is a single executable, so there is not much to track or manage with it compared to the full agent install. I would suggest just doing some simple tests on a test VM, to see which would work better for your use.

WheresThePizza · ‎Feb 06, 2020

Yes, this is something that you could do. I would suggest looking into the InventoryScanner as an option if you were using a rule to inventory this before with 0 foot print. You could also install an agent, and remove the INSTALLMACHINEPOLICY = 1 from the setup response. This will cause the agent to be installed, but it will do nothing. This could then be run from a scheduled task. For command line options and more details on the InventoryScanner I would reference the Gathering Inventory guide: https://helpnet.flexerasoftware.com/fnms/EN/WebHelp/PDF%20Documents/Cloud/GatheringFlexNetInventory.pdf

WheresThePizza · ‎Jan 28, 2020

As a first step, I would advise reviewing this KB article, to make sure that everything was configured correctly: https://community.flexera.com/t5/FlexNet-Manager-Knowledge-Base/How-to-Inventory-Citrix-XenDesktop-and-XenApp-using-FlexNet/ta-p/122531

WheresThePizza · ‎Jan 23, 2020

This looks like it was not an intentional thing to remove. I will submit a ticket to development to check into this.

WheresThePizza · ‎Dec 26, 2019

If you do not see these options you will want to open a support case so someone from the support team can help. They are missing because of they way permissions are provisioned for FNMS. These views require having a system administrator account. To rectify this you would need to modify a user entry in the Content Store database. Given the nature of what is involved to accomplish this, we provide these steps through a support case as opposed to public forum or KB articles.

Online Status	Offline
Date Last Visited	‎Apr 08, 2021 09:13 PM

Execution Timeout Expired: SQL 2016 SP2 CU16 (13.0.5882.1)

Re: Analytics/Cognos – connection to SQL server fails when server is configured to use TLS 1.2

Re: Obtaining EUC inventory with just FNMS Data center license

Re: IBM Cognos release in FlexNet 2019R2

Re: Validating data received from Citrix Xenapp agent in the FNMS UI

Re: Issue with DB Migration script while upgrading from 2017R2 to 2019 R!

Re: ARL import running LONG time (not completing)

Re: SoftwareTitle table in FNMS

Re: How can FNMS be retained if the OS is being upgraded?

Re: ARL import running LONG time (not completing)

Re: Schedule Windows task to run 'ndtrack.exe' on local device, instead of remote execution (zero fo...

Re: Schedule Windows task to run 'ndtrack.exe' on local device, instead of remote execution (zero fo...

Re: XenDesktop inventory gathering issue

Re: Where's the spinning gear wait animation?

Re: Cognos/Analytics Single Sign On

Execution Timeout Expired: SQL 2016 SP2 CU16 (13.0.5882.1)

Re: Analytics/Cognos – connection to SQL server fails when server is configured to use TLS 1.2

Re: Obtaining EUC inventory with just FNMS Data center license

Re: IBM Cognos release in FlexNet 2019R2

Re: Validating data received from Citrix Xenapp agent in the FNMS UI

Re: Issue with DB Migration script while upgrading from 2017R2 to 2019 R!

Re: ARL import running LONG time (not completing)

Re: SoftwareTitle table in FNMS

Re: How can FNMS be retained if the OS is being upgraded?

Re: ARL import running LONG time (not completing)

Suggested Actions

Suggest an improvement

Open a support case