Symptoms There could be any number of reasons for an ARL update failure. The first place to check is at the end of the recognition.log file which resides in either of the following directory locations - 1. If the ARL scheduled task is set to run under the SYSTEM account - C:\Windows\Temp\ 2. If it's set to run under a specific user or domain account - C:\Users\<username>\AppData\Local\Temp There are some instances where the failure can occur prior to anything being written to this log file. If this is the case, you'll need to run the ARL updater executable manually from the a command line in order to capture the error message. It can be launched without any additional command parameters - "X:\Program Files (x86)\ManageSoft\DotNet\bin\MgsImportRecognition.exe" See below if this process returns the following error message - 'Command could not be executed - make sure SQL Client Tools are installed at Core Server' Resolution If the 'SQL Client Tools' error message is returned, check to see if the Recognition.exe file exists in the DotNet\bin folder. If it is not, please contact technical support so that they can supply you with the appropriate version of this file. ... View more

Summary If the FNMP app server and inventory beacon are installed on the same system, the beacon will return an IIS 500 error when attempting to connect to the parent download URL if it's been configured to use IIS. Symptoms This error will usually be encountered when configuring the initial parent connection settings, but can also occur when attempting to connect to the parent ManagesoftDL URL when trying to download agent policy, schedule, etc. Windows Error Message - FNMP connection failed: Test connection failed (Response status code does not indicate success: 500 (Internal Server Error).) The Windows application event log will also generate the following error - Event code: 3008 Event message: A configuration error has occurred. ... Application information: Application domain: /LM/W3SVC/1/ROOT/ManageSoftDL-1-130746744168474007 ... Exception information: Exception type: ConfigurationErrorsException Exception message: Could not load file or assembly 'BusinessImport' or one of its dependencies. An attempt was made to load a program with an incorrect format. Cause In version 2015 there are some extraneous references to assembly files that are unable to be resolved. These files are not required by the beacon to function properly and have been removed from the appropriate configuration file. Resolution Update the following file with the one attached - X:\Program Files (x86)\Flexera Software\Inventory Beacon\DotNet\Web.config ... View more

Symptoms When trying to click on any of the applications in the 'product summary page', a red bar error is returned in the UI. And in the WebUI.log (located in the C:\ProgramData\Flexera Software\Compliance\Logging\WebUI directory on the application server), the corresponding error message looks similar to the following stack trace - [INFO 2016-01-29 09:07:03,469 490988ms ortSnapshotManagerBase] Saving report 'All Computers' for user 'NA\NummerdorB' to snapshot 'Report_op15_Reports_View_657_fba84bd3f0514cd4b0227c3c58006224'. [INFO 2016-01-29 09:07:08,750 496269ms ken=b77a5c561934e089]]] Saved 113336 rows to snapshot 'Report_op15_Reports_View_657_fba84bd3f0514cd4b0227c3c58006224'. [ERROR 2016-01-29 09:36:25,617 2253136ms UiHelper_Grid ] Error retrieving data DevExpress.Xpo.DB.Exceptions.SqlExecutionErrorException : Executing Sql 'DECLARE @Groups xml;SET @Groups = N'<ArrayOfString />'; SELECT [N0].[SoftwareTitleProductID],[N0].[ProductName],[N0].[PublisherName],[N0].[ComplianceStatus],[N0].[ComplianceStatusText],[N0].[InstallationsInBreach],[N0].[Liability],[N0].[Consumed],[N0].[ConsumedPercentage],[N0].[LicenseRecords],[N0].[IncompleteLicenses] FROM [dbo]. Grid_ProductComplianceListModel (1, @Groups) [N0] WHERE ((([N0].[PublisherName] = @p0) and (([N0].[SoftwareTitleProductID] = -31971) or ... [SoftwareTitleProductID] = -11870) or ([N0].[SoftwareTitleProductID] = -13166))))' with parameters '{Microsoft}' exception ' System.Data.SqlClient.SqlException (0x80131904): Arithmetic overflow error converting expression to data type int . Cause A license that has an especially high number of entitlements could potentially cause this issue. This can be confirmed by verifying whether the following SQL query returns an arithmetic overflow error message - USE FNMSCompliance SELECT CASE WHEN SUM(lic.Licensed) > 0 THEN 100.0 * SUM(lic.Consumed) / SUM(lic.Licensed) ELSE NULL END AS test FROM TableLicenseComplianceSummary(1,'<ArrayOfString />') AS lic GROUP BY lic.SoftwareTitleProductID, lic.ProductName, lic.PublisherID, lic.PublisherName, lic.Liability_CurrencyFormat Resolution If the debug SQL query fails with returns an arithmetic overflow error, then the stored procedure used to generate the product summary page can be modified to account for licenses that have been assigned a large number of entitlements. Please download and run the attached .sql script ... View more

Symptoms Using the out-of-the-box 'view only' permissions a user is getting a 403 permissions error when they click on a Oracle DB instance via the Oracle Instance page. Cause Viewing the details of an Oracle database instance requires licensing modification rights. Resolution Make sure to grant the 'Modify an existing software license' permission to the user role in question - ... View more

Summary This article describes usage metering data that FlexNet Manager Suite imports from Microsoft Endpoint Configuration Manager (also known as ConfigMgr, or SCCM), and suggests some SQL queries that can be used to investigate and troubleshoot problems with imported data. Queries used to extract usage data from ConfigMgr Usage metering data is obtained from two primary views in the ConfigMgr database: v_GS_CCM_RECENTLY_USED_APPS MonthlyUsageSummary The following query illustrates how data is obtained from the v_GS_CCM_RECENTLY_USED_APPS view. Usage data for both installer evidence and file evidence returned by this query is imported. Usage data for files is only processed for files that are shown by the query with a FileInstallationStatus of "Installed". (The query contains some example filters at the end which can be uncommented and modified as appropriate to return specific data that may be of interest.)   -- Run this query against the ConfigMgr database SELECT DISTINCT csd.Name00, csd.MachineID, sf.FileId, rua.ExplorerFileName0, rua.FileVersion0, rua.FileDescription0, rua.CompanyName0, rua.FileSize0, FileInstallationStatus = CASE WHEN si.ClientId IS NOT NULL THEN 'Installed' ELSE 'Not Installed' END, MsiDisplayName = ISNULL(NULLIF(msiDisplayName0, ''), ProductName0), MsiPublisher = ISNULL(NULLIF(msiPublisher0, ''), CompanyName0), MsiVersion = ISNULL(NULLIF(msiVersion0, ''), ProductVersion0), ProductCode = ISNULL(ProductCode0, ''), LastUserName0, rua.LastUsedTime0 FROM v_GS_CCM_RECENTLY_USED_APPS rua JOIN Computer_System_DATA csd ON csd.MachineID = rua.ResourceID JOIN SoftwareFile sf ON sf.FileName = rua.ExplorerFileName0 AND sf.FileVersion = rua.FileVersion0 AND sf.FileDescription = rua.FileDescription0 AND sf.FileSize = rua.FileSize0 LEFT OUTER JOIN SoftwareProduct sp ON sp.ProductId = sf.ProductId AND sp.CompanyName = rua.CompanyName0 LEFT OUTER JOIN SoftwareInventory si ON si.ClientId = rua.ResourceID AND si.FileId = sf.FileId AND si.ProductId = sp.ProductId WHERE -- csd.Name00 = 'name of computer' AND -- rua.ExplorerFileName0 LIKE '%name of executable%' AND -- rua.CompanyName0 LIKE '%name of software publisher%' AND -- rua.LastUsedTime0 > GETDATE()-90 AND 1=1     The following query illustrates how data is obtained from the MonthlyUsageSummary view.    -- Run this query against the ConfigMgr database SELECT csd.Name00, csd.MachineID, ExternalFileID = m.FileID, sf.FileName, sf.FileVersion, sf.FileDescription, sp.CompanyName, sf.FileSize, FileInstallationStatus = CASE WHEN si.ClientId IS NOT NULL THEN 'Installed' ELSE 'Not Installed' END, mu.FullName, StartDate = LEFT(m.TimeKey, 4) + '/' + RIGHT(m.TimeKey, 2) + '/01', m.LastUsage, m.UsageTime, m.UsageCount, m.TSUsageCount FROM dbo.MonthlyUsageSummary AS m JOIN Computer_System_DATA csd ON csd.MachineID = m.SystemItemKey JOIN dbo.v_metereduser AS mu ON mu.MeteredUserID = m.MeteredUserID JOIN SoftwareFile sf ON sf.FileId = m.FileID LEFT OUTER JOIN SoftwareProduct sp ON sp.ProductId = sf.ProductId LEFT OUTER JOIN SoftwareInventory si ON si.ClientId = m.SystemItemKey AND si.FileId = sf.FileId AND si.ProductId = sf.ProductId WHERE -- csd.Name00 = 'name of computer' AND -- sf.FileName LIKE '%name of executable%' AND -- sp.CompanyName LIKE '%name of software publisher%' AND -- m.LastUsage > GETDATE()-90 AND 1=1     What if usage is not recognized when expected? Some reasons for why usage of an application may not be recognized by FlexNet Manager Suite based on data imported from ConfigMgr are: The Application Recognition Library (ARL) does not contain an appropriate rule to recognize installer or file evidence details associated with the usage. The application the usage data is associated with is not recognized as currently installed. Running a query like the following and inspecting the assessment details in the last 4 columns can help to give insight into these situations when usage is recognized based on file evidence (a similar query would be possible to write for assessing installer evidence too):   -- Run this query against the FlexNet Manager Suite compliance database SELECT ic.ComputerName, ic.InventoryAgent, ic.InventoryDate, ife.FileName, ife.FileVersion, ife.Company, ife.Description, RawLastUsedDate = u.LastUsedDate, isd.IsUsed, RecognizedLastUsedDate = isd.LastUsedDate, 'Is file installed' = CASE WHEN iife.ExternalID IS NULL THEN 'No' ELSE 'Yes' END, 'Is file linked to application for usage' = CASE WHEN stfe.EvidenceExistenceRuleID IN (1 /* required */, 2 /* not for recognition */, 4 /* at least one */) THEN 'Yes' ELSE 'No' END, 'Linked application' = st.fullname, 'Is application recognized as installed' = CASE WHEN isd.SoftwareTitleID IS NOT NULL THEN 'Yes' ELSE 'No' END FROM ImportedInstalledFileEvidenceUsage u JOIN ImportedComputer ic ON u.ComplianceConnectionID = ic.ComplianceConnectionID AND u.ExternalID = ic.ExternalID JOIN ImportedFileEvidence ife ON ife.ComplianceConnectionID = u.ComplianceConnectionID AND ife.ExternalFileID = u.ExternalFileID LEFT OUTER JOIN ImportedInstalledFileEvidence iife ON iife.ComplianceConnectionID = ife.ComplianceConnectionID AND iife.ExternalFileID = ife.ExternalFileID AND iife.ExternalID = ic.ExternalID LEFT OUTER JOIN ImportedFileEvidenceMapping ifem ON ifem.ComplianceConnectionID = iife.ComplianceConnectionID AND ifem.ExternalFileID = iife.ExternalFileID LEFT OUTER JOIN SoftwareTitleFileEvidence stfe ON stfe.FileEvidenceID = ifem.FileEvidenceID LEFT OUTER JOIN SoftwareTitle st ON st.SoftwareTitleID = stfe.SoftwareTitleID LEFT OUTER JOIN InstalledSoftwareData isd ON isd.ComplianceComputerID = ic.ComplianceComputerID AND isd.SoftwareTitleID = stfe.SoftwareTitleID WHERE --ic.ComputerName = 'name of computer' AND --ife.FileName like '%name of file%' AND --ife.Company like '%name of software publisher%' AND --st.FullName like '%name of software application%' AND 1=1     If relevant evidence recognition rules are not currently configured in the ARL, you can configure rules yourself or send evidence details to Flexera with a request for rules to be added to the published ARL. Also consider that for usage to be detected it must meet the minimum usage period and other conditions configured on the "Usage" tab of the application record:. The following query can help to verify whether these data thresholds have been met in relation to usage recorded based on file evidence (a similar query would be possible to write for assessing installer evidence too):   -- Run this query against the FlexNet Manager Suite compliance database SELECT ic.ComputerName, ic.InventoryAgent, ic.InventoryDate, ife.FileName, ife.FileVersion, st.FullName, u.LastUsedDate, MinimumUsageDate = DATEADD(m, -(st.UsagePeriod * 30), GETDATE()), st.IsMonitoringSessions, u.NumberOfSessions, st.UsageSessions, st.IsMonitoringActiveTime, u.ActiveTimeInSeconds, st.UsageActiveTime FROM ImportedInstalledFileEvidenceUsage u JOIN ImportedComputer ic ON u.ComplianceConnectionID = ic.ComplianceConnectionID AND u.ExternalID = ic.ExternalID JOIN ImportedFileEvidence ife ON ife.ComplianceConnectionID = u.ComplianceConnectionID AND ife.ExternalFileID = u.ExternalFileID JOIN ImportedFileEvidenceMapping ifem ON ifem.ComplianceConnectionID = ife.ComplianceConnectionID AND ifem.ExternalFileID = ife.ExternalFileID JOIN SoftwareTitleFileEvidence stfe ON stfe.FileEvidenceID = ifem.FileEvidenceID AND stfe.EvidenceExistenceRuleID IN (1 /* required */, 2 /* not for recognition */, 4 /* at least one */) JOIN SoftwareTitle st ON st.SoftwareTitleID = stfe.SoftwareTitleID JOIN InstalledSoftwareData isd -- SoftwareTitle is recognized as installed ON isd.ComplianceComputerID = ic.ComplianceComputerID AND isd.SoftwareTitleID = stfe.SoftwareTitleID WHERE --ic.ComputerName = 'name of computer' AND --ife.FileName LIKE '%name of file%' AND --ife.Company LIKE '%name of software publisher%' AND --st.FullName LIKE '%name of software application%' AND 1=1       ... View more

Synopsis The FNMS beacon calls ActiveDirectoryImport.exe which uses a Windows system API for querying AD. It first obtains a list of all the organizational units (OU). The specific search for each OU to obtain users is then: ( &(objectCategory=person)(objectClass=user)(!(userAccountControl:1.2.840.113556.1.4.803:=2)) ) with the query results returned being "cn", "distinguishedName", "sAMAccountName", "mail", "objectGUID", "objectSid", "userAccountControl". It then checks that each record has at least a cn, distinguishedName and userAccountControl. In addition it also checks that the name is not a conflict by ensuring that the distinguishedName does not include a "CNF:". Finally, there is a check to make sure that the user is not a duplicate or a trust account and that they are a normal account. Discussion The following checks could be made for users that may be missing from a .actdir file: 1. Is the OU for the user being reported. If not, then all the users in that OU will not be reported. Are the missing users non-normal accounts, trust accounts or duplicate accounts. 2. If the OU is missing, we could investigate that further. ... View more

Symptoms FNMS agent based Oracle introspection scan fails to generate an Oracle inventory file, and the tracker.log file (found in either %TEMP%\Managesoft\ directory or C:\Windows\Temp\Managesoft) displays the following debug output - [11/2/2016 9:12:35 AM (G, 0)] {8440} Executing oracle inventory rules [11/2/2016 9:12:35 AM (G, 0)] {8440} WARNING: Configuration properties for the Oracle home "D:\oracle\product\11g\db" could not be discovered and instances in this home will not be inventoried. [11/2/2016 9:12:35 AM (G, 0)] {8440} ===== Discovered Oracle database instances and listeners [11/2/2016 9:12:35 AM (G, 0)] {8440} +-- "D:\oracle\product\11g\db": Discovered by = Process,Service,Registry,Rule, DBA group = "ora_dba", Has SQLPlus = true, SQLNet Authentication Services = "NTS", Can Inventory = false [11/2/2016 9:12:35 AM (G, 0)] {8440} | +-- Instance "ORCL": Discovered by = Process,Service,Registry, Process ID = 10212/10212, State = running [11/2/2016 9:12:35 AM (G, 0)] {8440} | +-- Listener "LISTENER": Discovered by = Service [11/2/2016 9:12:35 AM (G, 0)] {8440} Oracle home environment information was not discovered. [11/2/2016 9:12:35 AM (G, 0)] {8440} Finished tracking Oracle database instances using inventory recognition rules Cause Check the $ORACLE_HOME\Admin\Network directory to see whether the TNSNames.ora file exists. Although the agent does not use the information in this file to perform the Oracle scan, it still must reside in the expected directory in order for the agent to connect to the database instances. Resolution Create an empty tnsnames.ora file in the $ORACLE_HOME\Admin\Network directory. ... View more

Symptoms When running the pkgadd command to install the agent on Solaris, the following error is returned - root@sch1p457:/export/.../agent> pkgadd -n -a admin -r /dev/null -d managesoft-12.0.0.sparc.pkg ManageSoft pkgadd: ERROR: unable to open admin file <admin> Resolution Create a file called noask-pkgadd in the /var/sadm/install/admin directory with the following lines - conflict=nocheck setuid=nocheck action=nocheck partial=nocheck After that re-run the pkgadd command and include this additional parameter: -a noask-pkgadd ... View more

Synopsis When installing the FNMP agent on HP-UX systems version 11.xx and up, PHSS_30048 or later "ld(1) and linker tools cumulative patch" from HP must be already installed on the machine. ... View more

Symptoms When trying to access a custom report when logged in with a user role that only has 'normal' privileges for reports (list reports = allow / everything else = disallow), a '403: Unauthorized' message is displayed. Cause There is a bug in version 2015 R1, R2, and R2 SP1 that prevents users from accessing custom created reports when logged in with only read-only report permissions. Resolution This has been fixed in FlexNet Manager Suite 2015 R2 SP3. Workaround In addition to 'List reports', the permission to 'Modify an existing report' must also be granted in order to be able view custom reports. ... View more