FlexNet Manager Knowledge Base

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Knowledge Base Categories
This article applies to FlexNet Manager Suite cloud and on-premises implementations and provides help with utilizing the Unified Spend Analytics feature. Specifically, this article is tracking evolving details about how to obtain OAuth tokens for both cloud and on-premises implementations in order to export data to Unified Spend Analytics, and also provides information for obtaining a new license file for on-premises implementations that is required for using Unified Spend Analytics.
View full article
This article provide the information and an alternative method when the user uses Cyberark Management product integrated with Flexera inventory Beacon, in some circumstance if the password contain the special character ' $?! []' etc , the integration may not work and you will have discovery and remote inventory fail on access. The workaround is the following: 1. Either save the credential by using Beacon password store directly without using Cyberark integration  2. Or try to change/avoid the special character mentioned above in the password
View full article
Summary This article describes how the Office 365 (deprecated) and new Microsoft 365  connectors work with proxy setting and what sites (URLs) does it need online access to. Important: This article was written prior to the release of FlexNet Manager Suite 2018 R2, in which p roxy support was added to FlexNet Manager Suite PowerShell adapters . With releases of FlexNet Manager Suite 2018 R2 and later, in order to utilize proxy support, use the "Proxy Settings" section of the "Create PowerShell Source Connection" Flexnet Beacon dialog to enter proxy server, username and password information. The information in this article regarding whitelisting URLs that are needed for our Microsoft connectors applies to all versions of FlexNet Manager Suite. Synopsis Office 365 (deprecated) and new Microsoft 365 connectors will use the proxy configuration for whichever user is launching the ComplianceReader.exe executable. This effectively means that whichever service user account is set for the FlexNet Beacon Engine Service in the Services Manager, the proxy configuration for that user will be used when connecting to these connectors. If the Service is kept as using the Local System account, then the Proxy settings need to be distributed for the whole machine through Active Directory Group Policy. Discussion In order for the Office 365 (deprecated) connector to be able to pull data from the Office 365 Cloud environment, the FlexNet Beacon needs access to these sites/URLs (https over TCP Port 443 and http over TCP Port 80).  which are required by Microsoft (https over TCP Port 443 and http over TCP Port 80). Please refer this Microsoft KB article (Office 365 URLs and IP address ranges) -- https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges So on that page you can find under  ID 56  the following URLs: Below are some samples URL you will need to open the firewall. You may also need additional URL to be open per to the Microsoft KB (Office 365 URLs and IP address ranges) https://outlook.office365.com (to access the Microsoft Hosted instance) https:// *.prod.outlook.com (to access Microsoft's Exchange Server) https://login.windows.net (to get an authentication token) https://*.YourLoginDomain.com (whatever is after the @ symbol for the user set on the Beacon to run this task) https://*.onMicrosoft.com (If you are using a locally hosted Lync or Skype / Hybrid Office 365 environment) https://*.online.lync.com (to access Skype for Business Usage) http://ocsp.digicert.com & crl3.digicert.com & crl4.digicert.com & crl.microsoft.com & mscrl.microsoft.com (To access the CRL repositories needed for the Certificate Revocation Check during the SSL handshake) In order for the new Microsoft 365 connector to be able to pull data from the Microsoft 365 Cloud environment, the FlexNet Beacon needs access to these sites/URLs which are required by Microsoft (https over TCP Port 443 and http over TCP Port 80). Please refer this Microsoft KB article (Office 365 URLs and IP address ranges) -- https://docs.microsoft.com/en-us/office365/enterprise/urls-and-ip-address-ranges So on that page you can find under  ID 56  the following URLs: Below are some samples URL you will need to open the firewall. You may also need additional URL to be open per to the Microsoft KB (Office 365 URLs and IP address ranges) https://login.microsoftonline.com/common/oauth2 (for authentication)  https://graph.microsoft.com (this is a catch-all for all that is required for the deprecated Office 365 connector) In order to configure the proxy configuration for the Service Account, simply launch Internet Options as that user (or login to the device with that user) from Internet Explorer's Tools Menu or from the Control Panel. Enter the Proxy Settings needed for the Beacon to be able to go online and access Office 365.   Additional Information If the FlexNet Beacon Engine Service login is using the Local System account, which is the scenario by default, there are a couple options to overcome that: Change the FlexNet Beacon Engine Logon As setting to use your Service Account, then use the above options to set your proxy settings. The downside is that this setting would revert back to default after every Beacon upgrade. Have your Windows Admin set the correct Proxy Settings in the Group Policy and give access on the Proxy Server to allow the Machine to links above, which would work when using the Local System account.
View full article
Symptoms: The new Office 365 (O365) adapter fails when trying to retrieve the usage data. The error in the Importer log will look like - Failed to execute Reader 'Get Usage from Office 365 Exchange' from file C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Reader\microsoft 365\Usage.xml, at step line 1 Error: The remote server returned an error: (403) Forbidden.   Diagnosis:  The new O365 Adapter introduced in FNMS 2019 R1 release uses the Microsoft Graph API to collect information. Due to some changes made by Microsoft in December 2019, there are more permissions needed to capture the usage and hence, the O365 adapter will fail when trying to capture the usage data.   Solution: In order to resolve the issue, please do the following -  For the account that is used to generate the refresh token needed for the O365 adapter, add a new role in Azure AD - 'Reports Reader'. See the screenshot -  Generate a new refresh token and execute the adapter again  
View full article
Description There is an issue with the AWS adapter after upgrading to 2019 R2. Existing AWS connections which were created prior to upgrading to 2019 R2 will not run successfully after the upgrade.   This is caused due to the introduction of a new optional parameter on the connection page 'External ID' which is used when setting up a new IAM Role based connection. Replication Scenario The following line will be found in the log file:   2019-12-17 08:00:59,757 [ERROR] Failed to find required session variable 'externalId' for method 'Get-AWSHosts'. Check it is specified in the reader configuration file.   Workaround   Open the FlexNet Inventory Beacon UI Select the AWS connection on the Inventory connections page and click 'Edit' Make no changes, and click on 'Save' Repeat for each AWS connection on any beacons with AWS connections in place Version Fix Target This is expected to be resolved in the FNMS 2019 R2.2 release Resolution The bug is being tracked with reference  IOJ-2088702.
View full article
Symptoms: When starting the cognos service using IBM Cognos configuration, there may be a message in the IBM Cognos Configuration, or in one of the cognos logs ‘cogaudit.log’, similar to the one below. The message seems to indicate that ‘ServerA.xxx.com’ is the active Content Manager URL. However, in the specific scenario discussed in this article, ServerA is not the correct Cognos server and thus the active content manager should point to a different correct server. CM-SYS-5160 Content Manager is running in standby mode. The active Content Manager URL is http://ServerA.xxx.com:9300/p2pd/servlet. Diagnosis: The CMCAPACITY table in the ContentStore database stores URIs of both active & standby content managers (CMs). The active content manager contains the Usage value of 4 in this table. When the Cognos service is running, the CMPATH field contains the active content manager’s URI, but when the service is stopped, the value of this field is removed. The above symptom occurred when the CMCAPACITY table of the Contentstore database contained the incorrect server (ServerA) URI with Usage value of 4 in the CMPATH column. This can happen if there are two separate cognos environments inadvertently using the same ContentStore database. The impact of this issue is that user from FNMS webui>Reports tab is not able to access Analytics. Solution: The ContentStore database should not be shared between two cognos environments. In the above case, the IBM Cognos service was stopped and then disabled in the incorrect Cognos server ‘ServerA’ environment.
View full article
Symptoms: This KB article describes the error “We can’t retrieve the data from data set Flexera Data Models” when a user tries to access Cognos Analytics. The Cognos Analytics dashboards display the above message and do not load.   Solution: The error message is displayed due to an incorrect configuration of data source connections details on Cognos. One needs to follow the steps below as the Analytics Administrator (with Business Reporting Portal Admin account) to check the configuration issue: - Access the FNMS webui using the account that has the Business Reporting Portal Admin role. -Navigate to Reports>Analytics to access Analytics UI. - Click on the Manage icon 'click mark icon' around the bottom left side of the navigation bar. -Then navigate to Administration Console>Configuration>Data Source Connections. -Notice the three FNMP groups named below: FNMP-Dashboard FNMP-DW-DS FNMP-DW-DS-DQM -Click on each one of the above three groups and then click on the ‘More’ link under Actions on the right side of the page. -Then navigate to Set Properties>Connection. -Next to the ‘Connection String’ field, click on the pencil icon ‘Edit the connection string’. - Check both the ‘Native’ and ‘JDBC’ tabs. Ensure connection information, such as Server name, database name and port number, are correct.  Also ensure the port number is specified correctly in the ‘Port number’ field. -Also for both Native and JDBC connections, one can do test connection by clicking ‘Test the connection’ link. -The FNMP-Dashboard-Group connection string should point to the Compliance database and the rest of the other two should point to the DataWarehouse database.
View full article
Symptoms: When trying to connect Cognos to your SQL Server, you may see an error like: Error: "SQL Server did not return a response. The connection has been closed."  Diagnosis: If your SQL Server is configured to only communicate via TLS 1.2, you will see connection errors until a few additional steps are taken to configure Cognos to support only TLS 1.2.  Solution: The following steps can be taken to configure Cognos to communicate only via TLS 1.2: Get and install the Unrestricted SDK JCE policy files. These can be obtained here. Note: You will be required to create an IBM login to download these files Once downloaded, they files will need to be extracted under the Cognos installation location to be installed. By default, this location will be: C:\Program Files\ibm\cognos\analytics\jre\lib\security Next, you will need to add the SHA256 ciphersuites. This'll be done in the “IBM Cognos Configuration” utility. There'll be 2 areas to modify. The first will be Security > Cryptography. In here you'll want click edit on “SSL Protocols” and set this to only TLS 1.2, as seen in this screenshot: After this, you'll need to go into Security > Cryptography > Cognos, click edit on “Supported ciphersuites” and add all of the ciphersuites that have “SHA256,” as seen in this screenshot: Once these steps are completed, you'll want to close the “IBM Cognos Configuration” utility. Open the bin64 folder under the Cognos installation directory, by default this will be: C:\Program Files\ibm\cognos\analytics\bin64 Locate startwlp.bat, open this in a text editor and find the following line: set JVM_ARGS=-Xmx4096m -XX:MaxNewSize=2048m -XX:NewSize=1024m %DEBUG_OPTS% After this line add the following: set JVM_ARGS="-Dcom.ibm.jsse2.overrideDefaultTLS=true" %JVM_ARGS% Save and close this file Locate bootstrap_wlp_os_version.xml, open this in a text editor and find the following line: <param condName="${java_vendor}" condValue="IBM">-Xscmaxaot4m</param> After this line add the following: <param>"-Dcom.ibm.jsse2.overrideDefaultTLS=true"</param> Save and close this file Locate cogconfig.bat, open this in a text editor and find the following line: set J_OPTS=%DD_OPTS% %J_OPTS% After this line add the following: set J_OPTS="-Dcom.ibm.jsse2.overrideDefaultTLS=true" %J_OPTS% Save and close this file Start "IBM Cognos Configuration" using cogconfig.bat you modified in the previous step. Important: You must start "IBM Cognos Configuration" using cogconfig.bat In “IBM Cognos Configuration”, go to Data Access > Content Manager > Content Store. Right click on Content Store and choose “Test”. This should now be successful After these steps the test connection should be successful and the Cognos services can be started, the FNMS Analytics should now be accessible. If you are not seeing any of the data in the reports or widgets loading, you may need to take some additional steps to set a JVM argument for the QueryService to use TLS. The below IBM KB details these settings. 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.   For more information on this issue, you can refer to the following IBM KB: Connection to SQL Server fails when the server is configured to use TLS 1.2 or connecting to SQL Server 2016
View full article
The Tanium Connect exports your complete hardware and software inventory from Tanium into FlexNet Manager Suite and calculates your license consumption.
View full article
Summary How to enable tracing for Inventory Agent to gather more details on Inventory and Software gathering Problems Synopsis Some Software gathering like Microsoft SQL Server without Edition or Oracle inventory sometimes require more logging than the tracker.log to be able to understand what tasks have the Agent performed step by step. Discussion Non-windows Agents already have an etcp.trace file in its install directory. Windows Agents (prior to FNMS 2016 R1) and all Lite Agents, however, don't use the etcp.trace file by default, so you can follow the additional instructions in the Workaround section below. To enable tracing, you need to: 1) Open your etcp.trace file with notepad or any other text editor, which is located by default next to the Inventory Agent's install location. If you don't have one, please download the ndtrack.trace file as instructed in the Workaround section below. 2) To enable trace logs for all Error and Inventory tasks (which are already enabled in the attached ndtrack .trace file), remove the Hash Sign (#) prior to: +Inventory +Error 3) You need to set the location you want the log to be created in. Enter your location after the filename= field that has no Hash Signs. 4) Now you can run the Agent manually with administrator/root privileges. Below are a few examples after navigating to the directory ndtrack is in: For Windows Agents and Lite Agents: ndtrack.exe -t Machine -o LogFile=C:\Temp\tracker.log -o Upload=false -o MachineInventoryDirectory=C:\Temp For non-Windows Agents: ./ndtrack -t Machine -o LogFile=/tmp/log/managesoft/tracker.log -o Upload=false -o MachineInventoryDirectory=/tmp/log/managesoft For non-Windows Lite Agents: ./ndtrack.sh -t Machine -o LogFile=/tmp/log/managesoft/tracker.log -o Upload=false -o MachineInventoryDirectory=/tmp/log/managesoft 5) Collect the generated files once it's complete: tracker.log managesoft*.log *.NDI In order to enable a trace for other than a non-Windows Full Agent or a Windows Agent FNMS 2016 R1 and above, please download the attached ndtrack.trace file to the following directory and change the filename= path to where you want the log written to: For Windows Agents prior to FNMS 2016 R1: Save next to ndtrack.exe, which is by default at C:\Program Files (x86)\ManageSoft\Tracker (for 64-bit machines) or C:\Program Files\ManageSoft\Tracker (for 32-bit machines) For Windows Lite Agents: Save next to ndtrack.exe For non-Windows Lite Agents: Save in root /etc directory  
View full article
Symptoms: Users may see the following error when trying to edit reports with Firefox.     Diagnosis: This error is caused by a default setting of Firefox  as reported by the following KB article published by IBM:   https://www.ibm.com/support/pages/report-authoring-does-not-open-using-firefox-68  Solution: 1) Open Firefox and navigate to the configuration page by inputting "about:config" in the URL field. 2) Search the "dom.link.disabled_attribute.enabled" setting. 3) Set the "dom.link.disabled_attribute.enabled" setting to "false".  
View full article
Summary This article explains how to suggest changes to the ARL, SKU Library, or PURL. Question How can I suggest changes to the FlexNet Manager Suite ARL, SKU Library, or PURL? Answer Flexera Software welcomes requests from our customers for updates to the Application Recognition Library (ARL), Stock Keeping Unit (SKU) Library and Product Use Rights Library (PURL). I have not purchased a maintenance plan or it has expired, can I still suggest changes? Simple content requests which fulfill the criteria below can be submitted to the Content team. However, Flexera will not provide updates on the progress or completion of requests and may be denied by the Content team. Where do I submit the content request? Content requests should be submitted through a support case in our Community at  https://community.flexera.com When will my request be completed? Requests will be qualified and prioritized at our discretion. As general guidelines: We accept all submissions sent through Support. Most requests we receive are completed within 1 to 2 weeks. For example, ARL updates are often available within 1 to 2 weeks; SKU and PURL requests are usually available monthly. Large or particularly complex requests will be assessed separately. For any request that we're unable to deliver in a reasonable time-frame, Flexera Services may be available. Why has my request not been added? Please keep in mind that some applications, SKUs, and PURLs can't be added to our published libraries, such as: Application evidence that has been modified due to customer repackaging or don't include valid publisher, product or version information. The provided SKU details are incomplete, ambiguous, or otherwise unverifiable. Product Use Rights that are only available to a single customer through a unique contractual term. What information do I need to provide for the request to be fulfilled? ARL Unassigned Evidence Customers may generate Evidence submissions and submit these to Flexera Support, which will be attached to a Support ticket and redirected to the Content Team. This can be done in one of two ways, depending upon the version of FlexNet Manager Suite for Enterprises installed. All versions allow export of evidence into a Microsoft Excel spreadsheet, or some versions of FlexNet Manager Suite include a Share button on the Applications views that will generate a submission file. This submission can be emailed directly from the Share button wizard when enabled or can be saved locally and attached or uploaded separately. Note: Detailed instructions for exporting uninstalled evidence can be found in the attachments section. Classifications If you believe that an application has the wrong classification e.g. that it's currently listed as commercial, but it should be freeware, this can be submitted to the Content Team as well.  If possible, please also provide the web link from the vendor which proves the correct classification. New Applications All new application submissions need to follow the recommendations in 'Guidelines for Submitting Evidence in FNMP 2014+.pdf' which is attached to this KB article. If no evidence is known to be associated with the applications, please attach a spreadsheet with the following column headers completed for each application: Publisher, Product, Version, and Edition. SKU Library SKUs can come in many different formats, including price lists, purchase orders or simply just SKU values. Customers are encouraged to submit SKUs for processing to Flexera Support. This can be done in one of two ways: 1. Provide the original SKU data source (e.g., price list or purchase order); or 2. Use the attached template to provide SKU details. While we are happy to accept all submissions, even if you only have the SKU number. Please note that the more information you can provide, the quicker we can add it to the library. The following information for SKUs and PURLs are very helpful in speeding up adding to the content libraries: SKU value Publisher and Description License Type e.g. Upgrade, maintenance, full license A template is attached to this article that can be used to provide information on missing SKUs. If you can't provide this information, please send us the SKU anyway but please be aware that these typically take a lot longer to process as extensive research must be carried out and in some cases, we may not find enough information to process some SKUs. Sending as much information as you have on SKUs is preferable. PURL We welcome PURL requests or updates for how we can improve the PURL. A 'PURL Request' template is attached to this article, which can be used to submit PURL use rights questions or adjustments. The following information will be required for a review to occur: Publisher Product Use Rights Question or Adjustment Requested Reference Documentation Once we receive the completed template, we will review the documentation and provide feedback. How is the accuracy of the content libraries maintained? We have a large team of experts in software licensing and application recognition dedicated to maintaining and enhancing our content libraries. We publish updates weekly for the ARL and Monthly updates for the SKU and PURL, averaging tens of thousands of updates each month across the ARL, SKU, and PURL.  Additional Information The attachment 'Submission Template and Guidelines.zip' includes: 1. SKU / PURL submission templates 2. Guidelines for Submitting ARL data 3. How to engage with our Technical support team to request the content library changes
View full article
With FlexNet Manager Suite 2019 R2, downgrading to earlier versions of the FlexNet Beacon or inventory agent causes the application to unexpectedly quit.    
View full article
Symptoms: Unable to delete License Server Admin Set Diagnosis: The Delete button in the License Server Administrative Sets page does not work Solution: There is an existing bug on this issue.  Below is the workaround,  The  License Server Admin set can be removed from the database directly by means of an SQL script. The customer needs to modify the line "SET Name = 't3'" to use the name of the set you're wanting to delete. This is for SQL Server. DECLARE @Name NVARCHAR(max) SET @Name = 't3' -- Remove users from the set DELETE aa FROM MGR_LICSRVR_ADMINSET_ADMIN AS aa JOIN MGR_LICSRVR_ADMINSET as aset ON aa.ADMINSET_ID = aset.ID WHERE aset.NAME = @NAME -- Remove servers from the set DELETE ag FROM MGR_LICSVRADMSET_LICSVRGRP AS ag JOIN MGR_LICSRVR_ADMINSET as aset ON ag.ADMINISTRATIVE_SET_ID = aset.ID WHERE aset.NAME = @NAME -- Remove the set itself DELETE MGR_LICSRVR_ADMINSET WHERE NAME = @NAME
View full article
Description There has been a report of FNMS agent being deployed via InTune potentially resulting in a broken agent installation with auto repair prompts occurring post deployment. When the agent .msi file is configured in InTune, the Install Behavior option is to install as User, but agent needs to be installed in System/per-machine context.   Workaround It is possible to workaround this issue by creating a powershell script to launch the installer and specifying this script instead in InTune instead of the .msi file directly so that it can be executed as System from InTune. Version Fix Target An issue IOJ-2081669 has been submitted to enhance the agent installer to be able to support this InTune setting of installing as System directly.
View full article
Summary Information about FlexNet Manager Suite 2019 R1 FlexNet Manager Suite 2019 R1 Release: March, 2019 Prior Release Later Release FNMS 2018 R2 FNMS 2019 R2     Release Notes for FlexNet Manager Suite 2019 R1 are available in the following languages: FlexNet Manager Release Notes (English) FlexNet Manager Versionshinweise (Deutsch) Notes de publication FlexNet Manager (Español) Notes de publication FlexNet Manager (Français) FlexNet Manager リリースノート (日本語) These provide information relating to new features, significant changes, resolved issues, installation process and compatibility with other products.   Additional Information You can also download the following reports and updates from the Flexera Software Product and License Center: Reports Known Issues for FlexNet Manager Suite 2019 R1 Provides the current listing of issues relating to this release of FlexNet Manager Suite. This list may include issues resolved in any future release.   Hotfix Releases FlexNet Manager Suite Update 2019R1-05 Investigating and resolving application recognition issues is easier than ever thanks to the new  Evidence  tab which lists the evidence discovered for a selected inventory device. After applying this update when you see a listing for an application which you don't think is installed, or if you can't find an application which you know is installed, you can view the evidence used to recognize the applications on that device. Using this new evidence view enables you to identify and then determine the best way to resolve any discrepancies. FlexNet Manager Suite Hotfix 2019R1-04 Addresses an issue when processing purchases from the License Recommendations page. Any entries that recommend changing the licenses settings 'User multiplier infrequent' and/or 'User multiplier external', will fail to be applied. FlexNet Manager Suite Hotfix 2019R1-03 Fixes an issue when running a publisher specific reconciliation set to Oracle, the calculated licenses for IBM applications may be reset to zero. FlexNet Manager Suite Hotfix 2019R1-02 This hotfix resolves an issue when there is exemption set for any device role on the Use Rights & Rules tab of an Oracle licence, Oracle Instances consuming from this license are not shown in the Oracle Server Worksheet. FlexNet Manager Suite Hotfix 2019R1-01 This hotfix resolves the issue where the IBM PVU License Consumption report may show duplicate rows when multiple titles assigned to the same license are installed on the same inventory device.   Accessing the Product and License Center Ensure that you are logged into the Flexera Community From the top page of the Flexera Community, open FLEXNET MANAGER. Select Download Products and Licenses under the PRODUCT RESOURCES section. Choose the LET’S GO! Button under the group of products that includes FlexNet Manager Platform. Once the Product and License Center page has loaded, find and select FlexNet Manager Platform under Your Downloads. Under the Latest Version tab, you would typically see either the cloud or on-premises edition of FlexNet Manager Suite. Older versions of the on-premise edition reside under the Previous Versions tab. Click on your product. A list of available files to download will be presented. This will include a file similar to either: Known issues for FlexNet Manager Suite Cloud Edition Known Issues for FlexNet Manager Suite 2019 R1 Click on the presented file to download the report.
View full article
Find information about the FlexNet Manager Suite 2019 R2 release for on-premises
View full article
Summary This article outlines the processes involved in updating the FlexNet Manager Platform (FNMP) Application Recognition Library (ARL). Included in this article is information about the Flexera Software factory process, the automatic update process, the manual update process, and the ARL update behavior. Introduction Generally an updated ARL will be automatically downloaded and installed by operational FNMP systems on the Sunday after the first full week of the month at 1am. Discussion Flexera Software factory process Flexera Software continuously updates and improves rules and information in the ARL. This process includes the addition of new applications and associated evidence, and the extension and revision of existing titles. Revisions may include the standardization of data formats, such as application publishers, inclusions of details such as categories and classifications for application titles, and additional evidence. New evidence may include installer evidence for recognition and file evidence to allow usage data to be collected on a greater range of applications. The ARL is published as an SQL script hosted on the ManageSoft website (www.managesoft.com). This script is executed both to install the ARL on a new installation of FNMP, and to update an existing installation with new data. There are two ways to download and run this script: The Import ManageSoft Application Recognition Library scheduled task (configured in the Microsoft Task Scheduler) will collect and run the script on your schedule You can run the command-line tool, MgsImportRecognition.exe (typically installed to C:\Program Files\ManageSoft\DotNet\Bin), which will perform the same task as the automatic procedure. An updated ARL SQL script is normally published to the ManageSoft website sometime during the first full working week of each month. Automatic update process The Import ManageSoft Application Recognition Library task, by default, will check for an update at 1am on Sunday each week. If a new version of the ARL is found, the database update script will automatically be downloaded and executed, updating your database. Be aware that the scheduled task is created in a disabled state in new installations of FNMP. This gives you the opportunity to consider the implications of automatically downloading updates to ARL data before enabling the task, but it is normal to immediately enable the task soon after installing FNMP. If you are unsure whether the automatic update procedure is enabled, you can check the status using Windows Explorer: navigate to C:\Windows\Tasks and ensure that the Import ManageSoft Application Recognition Library task is Enabled. To confirm results from the most recent ARL update attempt, you may check Recognition.log. This log file can be found, in a default installation, in C:\Documents and Settings\Administrator\Local Settings\Temp (see below for more details about configuring the log file location). The first line of this file will show you the version of the ARL that the script attempted to install, and the last line will tell you if the latest download was successful. If the last line reads ?Finished: commit to new ARL state? then the latest ARL download and installation was completed successfully. If an error has occurred, the end of the log file will contain a message similar to the following: ------------------------------------------------------------------- Msg 50000, Level 16, State 1, Server QA01A, Procedure ARLConsistencyCheck_ONE_FUID_per_ONE_InstallerEvidence, Line 68 ERROR! Consistency check failed! Starting: Rollback to previous ARL state Finished: Rollback to previous ARL state The first line shows the error message (which will vary depending on the cause of the error), the procedure where the error was found, and the line of code which it references. The second line gives a brief description of the error, and the final two lines state that the database is being reverted back to the previous ARL state. For more detailed information on the error, scroll up in the log file to look for a sentence beginning with ?WARNING!? This is followed by a description of the error, and where applicable, details of the affected records in the ARL. If the ARL update is unsuccessful, please email the Flexera Software Support team, and include a compressed copy of the Recognition.log. Manual update process The automatic update process can be disabled if you prefer to run the task manually. To turn off the Import ManageSoft Application Recognition Library task, view the task properties using Microsoft Task Scheduler and uncheck the Enabled (Scheduled task runs at specified time) box. To run the update process manually, you can either right-click on the Import ManageSoft Application Recognition Library task and select Run; or you can run the ARL update using the MgsImportRecognition.exe command-line tool. In your operating system command line, navigate to C:\Program Files\ManageSoft\DotNet\Bin, and then enter MgsImportRecognition.exe to check for updates and install the latest ARL update. A Recognition.log similar to one created in the the automated update process is created in this scenario, too. For more detail on the manual update process see the FNMP_SystemReference Guide. Relocating the log file The ARL update process, whether run by scheduled task or manually, creates a Recognition.log file. In versions of ManageSoft Compliance Manager up to and including release 7.9.5, this log file was created in the directory from which the MgsImportRecognition.exe executable was run (by default, C:\Program Files\ManageSoft\DotNet\Bin). From release 8.0 of FNMP, this location has been changed. From release 8.0 of FNMP, the Recognition.log file is located, by default, in the Temp directory of the current account. For example, with the normal account of Adminstrator running the executable, the log file will be written to C:\Documents and Settings\Administrator\Local Settings\Temp. You can quickly access the Temp directory of the current account by typing %TEMP% in the address bar of Microsoft Windows Explorer. You can customize the directory where the Recognition.log file is written by adding a registry entry, as follows: In your registry editor (such as regedit), navigate to HKEY_LOCAL_MACHINE\SOFTWARE\ManageSoft Corp\ManageSoft\Compliance\CurrentVersion. If the registry key Recognition already exists, navigate to it. If it does not exist, manually create it (Edit | New | Key). In the Recognition key, create a new string value (Edit | New | String Value) with the name LogDirectory, and the data value being your new folder (for example, C:\Temp). ARL update behavior The execution of the ARL script can add new records, modify existing records, and delete old records. New records are added to increase the number of application recognized. Records are modified to make them more reliable and to help standardize the ARL. Old records that are no longer needed are deleted. Usually the modifications will be accepted, but in a few instances an ARL modification will be blocked. There are three reasons why an ARL update would be blocked: The record has been modified locally The record has a license attached The modification would result in a primary key clash Records modified locally For any given application, the ARL may update several database tables including SoftwareTitle, FileEvidence, InstallerEvidence, WmiEvidence, and the links that exist between these. In order to preserve any local changes that you have made to your data, each of these areas is guarded by separate checksums. If a checksum shows that you have altered an item, that item will no longer be updated by the ARL (although other related but unchanged items may still be updated). For example, if you edit a record of installer evidence linked to an application, then that installer evidence record will no longer be updated by the ARL, although the related application may still be updated. Similarly, if you add new evidence to an application (thereby changing the links between items), the ARL will no longer update relationships around this application (that is, will not make any changes to those links), but may still update the basic records. Also note that the checksums do not protect every field in a record, and you may change the 'unprotected' fields without impact. You can restore all your locally modified records to match the ManageSoft ARL by changing an internal ForceUpdateAllRecords configuration setting value to "true". This value can be set by running the following SQL command on your ManageSoft database: USE ManageSoft UPDATE SoftwareRecognitionConfiguration SET Value = 'true' WHERE Property = 'ForceUpdateAllRecords' Once this command has run, all records will be modified to match the ARL every time an ARL update is downloaded. To change it back to the default behavior, replace 'true' with 'false' and re-run the above command. Note: All of your local modifications will be lost when you update the ARL with this value set to 'true'. Records with attached licenses If the ARL attempts to delete an application that has been linked to a license, then that deletion will be blocked. Your database will keep the application and its attached license even though it is no longer in the published ARL. Any other types of modifications to the same record (other than deletion) should be updated successfully, as long as you have not also manually modified details on the application. Primary key clashes A primary key clash results when an ARL update tries to modify an existing record, or add a new record, in such a way that it will exactly match primary key values on an existing record. This is only likely to occur when an old record has been deleted from the published ARL, but has not been deleted locally for one of the two reasons listed above. Refer to ManageSoft Knowledge Base Article 100816 for further details.   Additional Information Reporting issues and requesting updates Issues, queries and requests for updates to specific titles in the ARL may be directed to the Flexera Software Support team. When reporting issues about a particular title in the ARL, please be sure to provide: Screenshots showing complete details of how the title appears in your local ARL, including information from the following tabs from the application properties dailog: General, File Evidence, Installer Evidence and History. A copy of the current Recognition.log (found in the %temp% directory - which is typically in C:\Documents and Settings\Administrator\Local Settings\Temp for FNMP v8.0 & later). Download URL's If you require the URL's to download the ARL and PURL files to perform the manual update process please review the FNMP_SystemReference guide ,Chapter 9: Command Line Tools, the URL's and update process is outlined in this document.The guide can be downloaded for the product and license center.
View full article
This article explains how to inventory Citrix XenApp and/or XenDesktop using up FlexNet Manager Suite.
View full article
Summary This article is intended to provide guidelines on the level of troubleshooting required by consultants and partner companies, prior to logging a Support Incident with Flexera Software Support team. Synopsis This article describes the initial steps to troubleshoot the most common FNMP Issues.   Discussion Is the incident related to any of the following FNMP issues: FNMP Server Management (e.g. Database, Custom Views) Compliance Import Hardware Asset Management Software Asset Management Remote Console Usage Tracking CSV Import Citrix XenApp Business Reporting Portal Application Recognition Issues (ARL, SKU and PURL issues) Business Adapter Studio Inventory Adapter Studio Legacy Reporting App Portal Integration Flexnet Manager for SAP a. FNMP Server Management Have all of the latest patches / service packs been installed? Is the problem related to Database or Custom Views? Database Is it a DB Permission, General Permission or DB Connectivity issue? Database Permissions What version of Windows and SQL Server is being used? Can the customer log onto their database when accessing it directly? If direct logon works but remote doesn?t then it?s a db connectivity issue If direct logon doesn?t work then follow point 3. What database authentication type is being used? What is the username and what level of access does that account have? General Permissions issues If access to the DB is available and some other permission related issue occurs on the server then: Are they using Active Directory (AD) or local groups? If using AD, is the user a member of MGS Compliance Users? Are the groups correctly setup on the database (Under the security section); i.e. if using AD groups do the AD groups appear in this section? If not then run \Program Files\ManageSoft\DotNet\bin\mgsPermissions -c -i "domain\group_name" (this will create the group in AD) If the group already exists in AD but just needs permissions correcting in the database you can run mgspermissions -i "domain\group_name" to apply the correct rights. Does the group appear correct in the dbo.Group table? e.g. SELECT * FROM [Group] WHERE GroupCN=?MGS Compliance Users? If for a specific user then is the user registered as an Operator? If yes then run "EXEC GrantCurrentOperatorFullAccess" ? this will grant full access to the currently logged on operator Once an administrator is logged in you should be able to add users and assign them to the relevant role (e.g. Compliance admins, Operators etc). Ensure the role has the relevant rights to perform the task, where they have anything other than "Administrator access" rights you should click the "Advanced" button and then expand the relevant section to see what they are allowed and denied access to. You should also check all roles the user is a part of as if a function is allowed on one role and denied on another the user will be denied as this takes precedence over allow. DB Connectivity If the user can logon to the db directly; check the database connection string and ensure it has the correct details Can they connect to the database remotely from the Inventory server? If not then this could suggest a DNS / Network Connectivity issue instead of an MGS issue. Custom Views Is the problem an error or data integrity (data not showing up/incorrect etc)? Error Is error related to a field error? If so then check that the field exists in dbo.ComplianceSearchTypeColumn as per the Customizing Property Sheets chapter of FNMP Reference Guide. If new specialized custom view is needed then refer to PS to create this. Data Integrity If issue is to do with Data integrity then edit the view, can you see the ViewXML and ViewSQL tabs? If no then navigate to [REGISTRY\Compliance\CurrentVersion] and create a string called ShowCustomViewQuery and set to true Check the SQL / XML to ensure that it?s checking the correct columns (if it was created in older version it might not be). If the query being run is incorrect; then get rpt of dbo.ComplianceSavedSearch where QueryName = ?<Custom view name>? then modify script as required. Back to FNMP   b. Compliance Import If the CM Import is initiated by scheduled task (Import ManageSoft Compliance data sources); what is the last result? Anything other than 0x0 is an error. Check the command, is it similar to; "C:\Program Files\ManageSoft\Common\ndcrproc.exe" -e "C:\Program Files\ManageSoft\DotNet\bin\ComplianceImporter.exe" -l "C:\Program Files\ManageSoft\DotNet\bin\ComplianceImporter.exe" -o CREATE_NO_WINDOW=True -- -a If the command is correct; open the GUI and right click FlexNet Manager Platform and select Compliance Import. Run with the same options as specified in scheduled task command; e.g. above at end of the command is -- -a which means that the only switch is ?a which means all data sources so just use All Data Sources and in addition show Data Source Warnings. Is there an error? If so search KB / past cases for that error. If the error isn?t clear enough or no error then you need to run a compliance trace: Navigate to the "C:\ProgramData\Flexera Software\Compliance\Logging" directory (or equivalent directory) Open the ?ComplianceReader.config? file and in there are the following points of interest: <file type="log4net.Util.PatternString" value="%property{ComplianceLoggingPath}\ComplianceReader\importer.log" /> This is the path of the created log file, the default is: ?C:\ProgramData\Flexera Software\Compliance\Logging\ComplianceReader\importer.log? <appendToFile value="false" /> Default is ?true? and this will create one importer.log that contains all the imports. Set to ?false? and it will create a new log file for each import. <maxSizeRollBackups value="15" /> Number of days that log files are kept for (default is 30) after which the logs are deleted The config file differs from the trace file in that the level of logging is more defined, it is set in the following section: <logger name="ManageSoft.Compliance.Importer.Logic.ComplianceImporter.Trace"> <level value="TRACE"/> </logger> The levels are: TRACE (only use on advice from support) DEBUG INFO WARN ERROR FATAL. The default is ?INFO? and this will include the levels below it (i.e. WARN, ERROR and FATAL) which means that in my code above where I have set it to TRACE my logs will contain the maximum level of detail as it includes all the lower levels as well. Open a command prompt window and change directory to <Program Files>\ManageSoft\DotNet\bin Run "compliancereader.exe" Once complete it will have generated the trace log in the location specified in compliance.trace and the error should be towards the bottom; search on it in KB / past cases. If a timeout error such as "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding." occurs, then increase timeout as per KB: Timeout expired error during compliance import on FNMP Keep increasing until the importer completes; then examine the log to see which procedure is taking the most time. Search on known issues for that procedure If none can be found, ask the customer to send the relevant Reader / Writer with the trace log to support. On 9.1 and below the Reader / Writer files can be located in: <Program Files>\ManageSoft\Compliance\ImportProcedures\Inventory On 9.2 and above the Reader / Writer files are located in:C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory Back to FNMP   c. Hardware Asset Management Is the device in the Inventory node when you search for it under the ?All? tab? If no then check to ensure the Compliance Import completed successfully. If it did then check to see if the Computer exists in dbo.ImportedComputer If it does exist in dbo.ImportedComputer check for the ComplianceComputerID and see if the name in dbo.ComplianceComputer for that ID matches; if not then the record may have been superseded/absorbed due to partial match of identification information (See the Inventory process flow in FNMP Reference Guide for more info). If the device does exist in Inventory (and therefore dbo.ComplianceComputer) check the status; 1 is New and 3 is Registered (linked to an Asset). Anything else means that the inventory record will not be used for compliance purposes and you should investigate why based on the status. If the computer is new but won?t link to an asset; check the asset record in dbo.Asset to find the AssetID and then search ComplianceComputer for that AssetID. If one exists then that asset is already linked and you should see if the linked computer record is still valid; delete it if not. Please note that depending on your settings virtual machines may share their host machine's asset in which case the VM will be in a status of registered but will not have a link to an asset - this is expected behaviour. If the Compliance Import did not complete successfully then on 9.1 and below you should activate the +Compliance\Importing tracking in <ProgramFiles>\ManageSoft\compliance.trace Once you?ve activated it (by removing the hash symbol from the relevant line); check the value in filename=?? at the top to see the location of the resultant log then save and close compliance.trace When a Compliance Import is next run it will produce that log and should contain an error which can then be searched for on the Knowledge Base. If on 9.2 or above, tracing is on by default and the latest importer.log can be found in C:\ProgramData\Flexera Software\Compliance\Logging\ComplianceReader\ Back to FNMP   d. Software Asset Management If the problem is a license not having specific features; check the FNMS Operation Guide Licenses chapter to ensure that correct license is used If a specific license type is unavailable; first check if a specific blade is needed e.g. Oracle is needed for Oracle license types; IBM for IBM license types etc. If that is correct; check the conditions of the license as some are only available in certain circumstances e.g. some license types are only available when you create the license; you can?t select it afterward. If Application consumption is incorrect; view the license details and see if any other application is linked to it. If the other application has Mandatory and the initial one doesn?t then the evidence will be linked to the application with mandatory evidence. If no other application is linked or there is no consumption; check the application evidence and compare the properties with what has been detected by the inventory agent; if these differ then it will not be marked as consumed. If the above 2 points are correct but consumption is still wrong then next check to see if the license is marked to not reconcile; run the query: SELECT * FROM SoftwareLicense WHERE CalculateCompliance=0. If any results appear then the licenses shown will not be reconciled and therefore will not automatically calculate compliance. If this is the case then run query: UPDATE SoftwareLicense SET CalculateCompliance=1 WHERE CalculateCompliance=0 and this will allow those licenses to be reconcilled again. If no evidence exists; first check that the ARL is up to date (see the "Import troubleshooting" section of Application Recognition chapter) If ARL is up to date, please review the "Content troubleshooting" section of Application Recognition chapter. Any other SAM issue; check the Known Issues KB article in first instance and then the KB / Release notes for fixed issues. Back to FNMP   e. Remote Console Does this affect all users or single user? If a single user then check that user is in the same AD groups as a working user e.g. MGS Compliance Users and that the user is set to an Operator (v8.4 and above). Are they using the same version as the core FNMP server? If using Windows 2008 make sure that ManageSoftServices is set to use Basic Authentication and/or Windows authentication (same domain only) and that the ManageSoftWebServiceAppPool is set to use .Net 4.0 on 8.6 and above or .Net 2.0 on 8.5 and below. Enter the URL from the remote console in Internet Explorer; does an error appear or does a page load? If a page loads, what happens when you click GetServices? Does it load? If an error appears; search the KB /send the information to Support If the database server is separate from the FNMP server, check the console error trace for a line similar to: System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. If this exists it could be caused by a "double hop" issue which is covered by KB article Resolving FNMP remote console double hop issue Back to FNMP   f. Usage Tracking Has Usage Tracking been configured and activated? If no then follow instructions in KB article: Configure Application Usage Tracking (AUT) in FNMP If usage tracking / software metering numbers are low after upgrading, please check Metering figures incorrect for local applications after upgrade of FNMP. If importing from SCCM then check that the application has recent data in the MonthlyUsageSummary and RecentlyUsedApps_DATA (9.2 SP3 and above) tables Check compliance trace for errors and send details to support. Back to FNMP   g. CSV Import Check columns used in CSV match the columns in the FNMP reference guide (Importing data from other systems chapter). While checking column names match, check data types as well e.g. if column requires an Integer value in documentation, make sure CSV uses an Integer (number) In the case of Purchase Order imports, the order of the CSV is important i.e. if there is an IsHeader record then THIS MUST BE FIRST before any PO line records for that Purchase Order. You should also ensure that the TotalPrice fields are completed as the system will not auto-calculate records imported by CSV (in most cases). If dates are used then they must be in the format yyyy/mm/dd otherwise a date-time error will occur. Back to FNMP   h. Citrix XenApp What version of Citrix Server is the XenApp Server Agent installed on? Check Release Notes for currently supported versions Do you have EdgeSight installed? If EdgeSight is not installed usage data cannot be obtained which means that applications will be licensed based on what the users / computers have access to instead of what is actually used. If EdgeSight is installed what version is it? Check Release Notes for currently supported versions Have you got .Net 4.0 installed? .Net 2.0 was for FNMP 8.5 and below, in 8.6 we now use .Net 4.0 instead Does the user account being used have access to at least read the XenApp server?s local file system? Is the agent installed on at least one server in the Citrix farm? Back to FNMP   i. Business Reporting Portal Has the Cognos Business Rreporting Portal been installed? If not follow the instructions on KB Adding the Business Reporting Portal to an existing FlexNet Manager Platform installation If it has been installed, review KB Troubleshoot Cognosfor some useful troubleshooting steps Back to FNMP   j. Application Recognition Issues Import Troubleshooting Is this an ARL Import or SKU/PURL Import issue? If ARL then is the owner for the tables to dbo? Is the ARL up to date? (Check ARLVersion in dbo.SoftwareRecognitionImport table) If yes, then is it using online updating or local updating? Has the other method been attempted (if possible) Check Recognition.log for ARL errors and search on KB then send to Support. If error message in log says "Customer Name '<Customers name on license>' does not exist in CFS database" then please send the exact customer name in the message to support who can add it to the database If SKU then: First check dbo.DatabaseConfiguration to see if the SKU version is up to date If old version then does the customer have ECM PURL Data in their license (v8.4 and above)? If there's a problem downloading SKUs (using PURL.cab on 8.4 and above) then check the "PURL-log.txt" file in the Temp folder (e.g. C:\Windows\Temp if task is run using SYSTEM or %TEMP% of the task user if a different account is used) - this log will detail any problems Try manually importing the SKU library using the same method as the manually updating the PURL (see steps in PURL section below) IF PURL then: Check "ImportPURL.log" file in the Temp folder (e.g. C:\Windows\Temp if task is run using SYSTEM or %TEMP% of the task user if a different account is used) - this log will detail any problems downloading the blades A common issue here is the security certificate as the PURL has additional certificates to install other than the ARL one, see KB: ARL,SKU and PURL Digital Signature Upgradeand check the Additional Information section. Try manually updating the PURL using the instructions in KB: Manual PURL Download & Importer instructions for FNMP 9.0 and abovefor 9.0 and above.. The above is only for issues regarding the actual import process. For issues where applications are not being recognised, please see the section below (Content Troubleshooting). Content Troubleshooting Once the ARL is up to date, this section covers how to troubleshoot problems with specific applications If the application does not exist; manually create the evidence and the applications should become linked after the next import. If this resolves the issue then you can request the application / evidence be added to the ARL using instructions in KB article: Changes to the ARL / SKU library. If the application already exists but you think that the evidence might be incorrect: Please refer to KB Diagnosing the Compliance Reader in Enterprise Compliance Manager version 8.2 to 9.2 which allows you to add custom views / SQL views that can be used to identify what evidence triggered recognition and this can then be checked on the device in question if required. You should now be able to identify if the evidence required for an applicaiton is found on the computers and if the application needs changes then contact support and quote this article including all your results and findings. Back to FNMP   k. Business Adapter Studio For any general MGSBI issues, ensure that the MGSBI.exe file in the Business Adapter Studio is the latest version (See KB article: Flexera Software Business Importer (MGSBI) for FNMP) If you get an error saying that the list of Worksheets could not be loaded, follow the guidelines on KB article: An error has occurred. The list of Worksheets could not be loaded. Back to FNMP   l. Inventory Adapter Studio If opening an existing adapter FNMP stores the adapters in %ALLUSERSPROFILE%\Flexera Software\Compliance\ImportProcedures . Back to FNMP   m. Legacy Reporting Try accessing http://<SSRS_server>/reports (where SSRS_server is the server SQL Server Reporting Services is installed on)- does it load? If no, then SSRS is either: Not installed on your environment and you will need to install it. Is on a different server in which case you should modify the URL above (and potentially the settings), review KB article: How do I export FNMP / Inventory Manager reports when SSRS is installed on another server and How to Configure Reporting Services. If the error you receive is ?The report server cannot open a connection to the report server database? then once you have accessed the /reports page: Click on MGSDefns Click on ManageSoft Ensure that the connection details in this page are for a valid SQL server that you are able to access from the FNMP server. Once settings have been modified, restart the SSRS service and try again. Back to FNMP   n. App Portal Integration As of FNMP 9.2 and App Portal 7.5 you can now use FNMP to provide licensing information for App Portal catalog items. The majority of the integration steps take place within App Portal however there are a couple of suggestions for dealing with issues on the FNMP side: For more general information on App Portal integration in FNMP, please review the Compliance Server and Database Settings chapter of the FNMP reference guide. The username / password for connecting to the Gateway is admin / admin respectively. App Portal connects to FNMP using the ManageSoftServices site via the Flexera Service Gateway so ensure that ManageSoftServices is set to use Windows Authentication or ASP Impersonation with a valid Active Directory account. Ensure that the Flexera Gateway is installed and that both App Portal and FNMP are registered with it before trying to search for licensing information in the App Portal catalog items. Back to FNMP     o. Flexnet Manager for SAP   If you get any incidents related to FNM-SAP Business Suite, here are some KB articles that may help: For initial troubleshooting, please review: Carry out basic troubleshooting for FNM-SAP Business Suite If you?re unable to start the admin module, can transaction ST03N be run directly on the basis system? If not, then the problem is on the SAP environment and this will need fixing before running FNM for SAP, once ST03N can be run then we can investigate further. If you're using FNM-SAP Applications (9.1 and above) and have any issues with the inventory imported into FNMP from SAP then please provide the relevant System and Consumption XML files. Back to FNMP   Related KB Articles Q201179: Troubleshooting guide for FNMP and Inventory Manager
View full article