About WheresThePizza

anhpham1652 · ‎Dec 13, 2021

Hello, I followed this link to configure TLS 1.2 SQL Server and IBM Cognos. All database connection is OK (both on IBM Configuration and Cognos Administration) but there is no data available at section Software Asset Management, etc. I've found some error such as "query service internal error has occurred please see the log for details" and in xqe log I've got this xqe log. https://drive.google.com/file/d/1u6s18xzvWg1isMJhx9ejFRD7GzIFmh1q/view?usp=sharing What should I do to fix it?

WheresThePizza · ‎Sep 02, 2021

Due to the nature of what is involved in elevating a user to the admin level required to expose these settings, we cannot publicly share these steps. Doing so could allow Cognos users (not just Flexera Analytics users) to gain admin access where they should not be able to. In this regard, these steps are only provided through support cases.

bwcbwc59 · ‎Sep 02, 2021

@WheresThePizza Thanks. Also, after further validation of the environment, we are actually on the 13.0.5882 build, so no discrepancy in the KB article. We are reverting to CU15 as CU 17 isn't currently available in RDS

WheresThePizza · ‎Jul 19, 2021

I must apologize, but it is not exactly clear what is being asked here. If you could clarify what exactly you are looking to do, then someone might provide some helpful information.

WheresThePizza · ‎May 21, 2021

@RichardBounds The issue listed in this KB was fixed in the 2020 R2.1 Cloud release and will be part of the 2021 R1 On-premises release.

WheresThePizza · ‎May 13, 2021

Symptoms: When you are using a beacon connected to our cloud endpoint, beacon.flexnetmanager.com, you receive an SSL/TLS error stating that the connection could not be made: Clicking OK on the error, going to Beacon configuration > Parent connection, and clicking Test connection will show failed for parent inventory beacon, but download and upload test succeed: Diagnosis: This is caused by missing cipher suites on the server that is hosting the beacon. The endpoint beacon.flexnetmanager.com is failing due to the change in certificate provider where this cipher suite is required to establish the TLS connection. The endpoint data.flexnetmanager.com may still work without error, as that endpoint is still using an older certificate type at this time. Solution: You will need to ensure that the cipher suite, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, is enabled on the server. If this is disabled, it was most likely controlled via Group Policy on the server, and you will want to work with your System Administrator/Security teams to have this enabled. You can also use a utility like ‘IIS Crypto’ that will allow you to verify and configure the cipher suites easily. Within IIS Crypto, you will want to go into the Cipher Suites view, find TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, enable this with the check box, check the Reboot check box, and then press the Apply button. Once the server is rebooted, this cipher suite will be enabled, allowing the beacon to connect to the endpoint without error. If you recheck this value after reboot and see that it is unchecked again, this would indicate that this value is still being controlled by Group Policy or something else that would clear this on the system startup. IIS Crypto: Group Policy:

winvarma · ‎Jul 14, 2020

Hi @flexeranoob , Instead of including the Flexera agent in the Image itself i would suggest that the agent should be installed separately once the OS is installed as we install the sccm, Antivirus using a script to deploy the agent or via sccm/bigfix etc so that it will avoid any further issues like uid duplication's etc. Just my thoughts on your issue. Regards,

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.

scott_thornhill · ‎Mar 04, 2020

I have been looking deeper into the support dates and using the data that is there. It is awesome to use. I have come across several titles that do not have support dates where I would have thought they would be there. Examples are RHEL, SUSE, CENT - these do not have support dates documented. The OS instances with dates are z/os, Windows, Solaris, and AIX. Should I expect that the catalog would have dates for recognized OS types?

jaalstead · ‎Feb 12, 2020

I reran the scheduled task and it completed just fine. Weird that it was hung up for hours.

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.

nalinih · ‎Feb 06, 2020

Thank You.

Online Status	Offline
Date Last Visited	‎Dec 28, 2021 06:43 PM

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

Re: Cognos/Analytics Single Sign On

Re: "Execution Timeout Expired" error with FlexNet Manager Suite databases hosted on SQL Server 2016...

Re: Discovery and Unrecognized evidence

Re: Issue exporting certain characters when downloading views as CSV

The request was aborted: Could not create SSL/TLS secure channel.

Re: How does a FlexNet Agent work if machines are cloned and then renamed

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: SoftwareTitle table in FNMS

Re: ARL import running LONG time (not completing)

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

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