Summary This article describes a problem that may occur in Writer 'WriteAccessedSoftwareOccurrence' during Reconcile Symptoms Reconcile fails and like the following error is logged in importer.log on FlexNet Manager Suite 2016. 2016-09-09 11:51:55,103 [INFO ] All retries have been attempted for Writer 'WriteAccessedSoftwareOccurrence' 2016-09-09 11:51:55,149 [ERROR] System.Data.SqlClient.SqlException (0x80131904): The INSERT statement conflicted with the FOREIGN KEY constraint "FK_AccessedSoftwareOccurrence_AccessedSoftware". The conflict occurred in database "FNMP", table "dbo.AccessedSoftware_MT". Deleted 10 accessed software occurrence which does not exist in source Deleted 4 accessed software records which has all the occurrences removed Updated 11111 AccessCount of accessed software occurrence records for existing accessed softwares The statement has been terminated. Inserted 0 new accessed software occurrence records at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at ManageSoft.Compliance.Importer.Logic.XML.Writer.Execute(IExecutionContext context) at ManageSoft.Compliance.Importer.Logic.ComplianceImporter.ExecuteWriters(ComplianceReader p_ComplianceReader, IExecutionContext context, String singleConnectionIdentifier) ClientConnectionId:d14b0e70-b836-4f75-807f-3e5939667b71 Error Number:547,State:0,Class:16 Cause This issue had been idendified as Bug # IOJ-1776872 (FNMS-35999). Resolution The bug had been fixed in FlexNet Manager Suite 2016 R1 SP1. Workaround The patch is available under attachment file 'FNMS-35967.zip'. Please follow the 'readme.txt' instructions to apply the patch on your system. Carefully backup before apply the patch is always recommended. ** Note !! The 2016 R1 Cumulative update 1 doesn't include the fix. Therefore be aware if you applied the patch before CU migrate , CU will revert back to default defect status. ... View more

Summary This article describes a known issue that old WMI evidence is not cleared from the database and invalid applications are reported. Symptoms Users may see applications that were already removed being reported as installed with FlexNet Manager Suite between FlexNet Manager Suite 2015 R2 and 2016 R1 SP1. Cause There was a defect in the WMIEvidence writer that old WMI evidence is not removed from InstalledWMIEvidence table appropriately. Resolution The issue was fixed in FNMS 2017 R1 release. Workaround The current attached XML is for 2015 R2 SP4 customer. 1. Backup your existing WMIEvidence.xml 2. Replace the downloaded file under C:\ProgramData\Flexera Software\Compliance\ImportProcedures\Inventory\Writer If you need a corresponding version of the XML file for your affected product version, please contact Flexera Technical Support instead of using this XML file which is only for 2015 R2 SP4. Please use this article as a reference when contacting support. Related KB Articles FNMS-35892 ... View more

Summary This Knowledge Base article describes a product defect found in FlexNet Manager Platform 2015 R2 Service Pack 4. The issue will affect database transaction log growing to out of space issue. Symptoms This Knowledge Base article describes a product defect found in FlexNet Manager Platform 2015 R2 Service Pack 4. The issue will affect database transaction log growing to out of space issue. For reference, the transaction log related error is: System.Data.SqlClient.SqlException (0x80131904): The transaction log for database 'FNMSCompliance' is full due to 'LOG_BACKUP'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds, Boolean describeParameterEncryptionRequest) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.ExecuteNonQuery() at ManageSoft.Database.DatabaseCommand.ExecuteNonQuery() at ManageSoft.Database.Impl.DatabaseLayerBaseSql.Execute(CommandType p_CommandType, String p_CommandText, DatabaseParameter[] p_Parameters) at ManageSoft.Compliance.Database.Impl.ActivityTable.AddObject(DatabaseObject p_Object, Boolean p_Resync) at ManageSoft.Database.Impl.DatabaseTableBase`2.UpdateRecurse(TTableObject p_Object, Hashtable p_UniqueTables, Boolean p_Resync) at ManageSoft.Database.Impl.DatabaseTableBase`2.Save(TTableObject p_Object) at Flexera.ActivityLogging.DBActivityWriter.WriteEventsToPersistence(IEnumerable`1 eventsToWrite, ActivityReport basicProperties) at Flexera.Common.Logging.ActivityLogging.BufferedActivityWriterBase.WriteContentsOfBuffer() ClientConnectionId:b3874555-9b5d-47ba-bff4-4218d1d2c830 Error Number:9002,State:2,Class:17 Cause The ComplianceReader tool initiates a transaction on a separate connection, inserting a row into the DatabaseMutex_MT table and holding that transaction uncommitted until the end of tenant processing. Since SQL Server will only allow its transaction log to be truncated up to the oldest open transaction, this causes the transaction log to continue to grow in size until it reaches its maximum or the transaction is closed (committed or rolled back). Transaction log backup can occur and will succeed, however it will not release the log size. At times of high change throughput, the transaction log can run out of space, causing failures across FNMS as no actions can be performed on the system. Resolution The permanent fix was added in 2015 R2 Service Pack 5 release. Workaround For affected customer on product version 2015 R2 service pack 4. Please apply the DR patch from the attachment "FNMS-32082.zip" Please follow the the 'readme.txt' for the steps of how to applying the patch. ** If the issue is happens on any other version , other service pack number , please contact with Flexera technical support before applying this patch specifically for sp4. Additional Information DBCC SQLPERF(LOGSPACE) ... View more

Summary This article will provide with a general instruction how to find out when machine inventory ndi file was resolved but generated a BadLog folder. This could happens across all version of FlexNet manager platform inventory resolving activity. Synopsis Sometimes, while machine inventory is resolved, it will failure and a "BadLog" folder will be generated such as c:\ProgramData\Flexera Software\Incoming\Inventories\BadLogs. In that situation: 1. The machine inventory wasn't resolved successfully 2. Application Server didn't receive the machine information 3. The original machine inventory file will be found under C:\ProgramData\Flexera Software\Incoming\Inventories\BadLogs Discussion Please Use the following steps to attempt to manually import a file that has been rejected: 1. Disable the "Import inventories" scheduled task 2. Save the file to ...\Incoming\Inventories 3. Execute: \Importers\bin\mgsimport.exe -t Inventories 4. Inspect the output from mgsimport.exe and see what it did with the file. Additional Information Be aware most of time, such resolve issue will run through on the 2nd try by above steps. So if it's succeeded by above steps it may not be easily to figure out why it's at failed first time. But if it's return any meaningful information regarding the failure, please do take a screenshot and send it to Flexera support. ... View more

Summary This knowledge base article described a product defect when Inventory Beacon is downloading it's own policy. Error will be shown on BeaconEngine.log and how to fix this issue. Symptoms This knowledge base article described a product defect when Inventory Beacon is downloading it's own policy. Error will be shown on BeaconEngine.log and how to fix this issue. The error looks like below: [ERROR 2016-01-05 16:30:48,216 2803054ms HandleErrorAttribute ] An unhandled error occurred System.ArgumentException: An item with the same key has already been added. at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) Cause A defected on the product, affected version 2015 R2 SP3 or earlier version. Resolution The permanent fix is added int FNMP 2015 R2 SP4 or later. It's a data driven issue caused by a table/view "DiscoveredDeviceExtended" in FNMPCompliance database. Workaround For affected product version, please run attached SQL script which will update the view statement "DiscoveredDeviceExtended". 1. Please backup the original view statement 2. Run the attached script. 3. Trigger another Beacon policy download to confirm the issue is solved. ... View more

Summary This knowledge base article describes the capability of Flexera usage agent to track application usage installed via a certain type of installation technology and its limitation. Synopsis From Flexnet Manage Suite version 2014 +, the Flexera usage agent is able to support automatic usage tracking of applications installed via standard installers (eg. MSI, RPM etc). There is currently no practical way to enable usage tracking of applications installed via other means. Inventory Manager 9.2 used to handle this via Manual Mapper packages or usage tracking integrated with the licensing portal which is now deprecated. There is no official product guideline to how to configure this feature. Hence Manual Mapper is not officially supported in v2014+. Discussion MSI is an installer package file format used by Windows. Its name comes from the program's original title, Microsoft Installer, which has since changed to Windows Installer. MSI files are used for installation, storage, and removal of programs. From the inventory ndi file, you can particularly look for <Key Name="WindowsInstaller" Value="0x00000001 (1)"/> appearing in the body of a software installation evidence collection. See below as an example. <Key Path="{1D8E6291-B0D5-35EC-8441-6616F567A0F7}"> <Key Name="AuthorizedCDFPrefix" Value=""/> <Key Name="Comments" Value="Caution. Removing this product might prevent some applications from running."/> <Key Name="Contact" Value=""/> <Key Name="DisplayVersion" Value="10.0.40219"/> <Key Name="HelpLink" Value="http://go.microsoft.com/fwlink/?LinkId=146008"/> <Key Name="HelpTelephone" Value=""/> <Key Name="InstallDate" Value="20170201"/> <Key Name="InstallLocation" Value=""/> <Key Name="InstallSource" Value="d:\fddad678d4681047dd7281dbf6bf\VC_Red_x64\"/> <Key Name="ModifyPath" Value="MsiExec.exe /X{1D8E6291-B0D5-35EC-8441-6616F567A0F7}"/> <Key Name="NoModify" Value="0x00000001 (1)"/> <Key Name="NoRepair" Value="0x00000001 (1)"/> <Key Name="Publisher" Value="Microsoft Corporation"/> <Key Name="Readme" Value=""/> <Key Name="Size" Value=""/> <Key Name="EstimatedSize" Value="0x00003777 (14199)"/> <Key Name="UninstallString" Value="MsiExec.exe /X{1D8E6291-B0D5-35EC-8441-6616F567A0F7}"/> <Key Name="URLInfoAbout" Value=""/> <Key Name="URLUpdateInfo" Value=""/> <Key Name="VersionMajor" Value="0x0000000a (10)"/> <Key Name="VersionMinor" Value="0x00000000 (0)"/> <Key Name="WindowsInstaller" Value="0x00000001 (1)"/> <Key Name="Version" Value="0x0a009d1b (167812379)"/> <Key Name="Language" Value="0x00000000 (0)"/> <Key Name="DisplayName" Value="Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219"/> </Key> Workaround An existing product enhancement is raised: IOJ-1664037 Usage tracking of applications not installed via a standard installer ... View more

Summary This article will explain the reason why Oracle License will have status "in breach" but License Entitlement is still greater than raw consumption and how to fix. Synopsis From FlexNet Manager Platform version 2015 + , sometimes user will notice the Oracle License with type such as Name User Plus or Oracle Processor ; the license entitlement number is still greater or quails to raw consumption, but license status will showing Red -- In Breach. Further more when you open the license, on Compliance Tab you will find the Breach reason: "Option License does not match instance" Discussion This is happens when on an Oracle server, the database instance is consuming one Oracle license type (eg: Oracle Processor), however the corresponding Database Option of the instance is consuming the other license type (eg: Oracle Name User Plus) or vice versa. This mismatch warning will be shown and reported as 'In Breach". Workaround Please check those In Breach Oracle license -> Consumption tab to find out which server is existing across the DB License & Option License with different type. The following query can also be used to identify Oracle instances associated with both types of Oracle licenses and identify the options tied to the conflict license. Once the consumption is under the same Oracle License type, followed by a reconcile. The alert will be removed and License Compliance status will be back to 'Compliant' select nup.computername, nup.InstanceName, nup.license as 'nup license', nup.[option pack] as 'nup option', oracleproc.license as 'oracle proc license', oracleproc.[option pack] as 'oracle proc option' from ( select i1.ComplianceComputerID, i1.InstanceID, cc.ComputerName, i1.InstanceName, sl.name as 'license', fullname as 'option pack' from Instance i1 join SoftwareLicense sl on sl.SoftwareLicenseID = i1.SoftwareLicenseID join softwaretitle st on st.softwaretitleid = i1.softwaretitleid join ComplianceComputer cc on cc.ComplianceComputerID = i1.ComplianceComputerID and st.SoftwareTitleTypeID in (2,3) where licensetypeid = 17 ) nup join ( select i1.ComplianceComputerID, i1.InstanceID, cc.ComputerName, i1.InstanceName, sl.name as 'license', fullname as 'option pack' from Instance i1 join SoftwareLicense sl on sl.SoftwareLicenseID = i1.SoftwareLicenseID join softwaretitle st on st.softwaretitleid = i1.softwaretitleid join ComplianceComputer cc on cc.ComplianceComputerID = i1.ComplianceComputerID where licensetypeid = 16 and st.SoftwareTitleTypeID in (2,3) ) oracleproc on oracleproc.ComplianceComputerID = nup.ComplianceComputerID and oracleproc.InstanceName = nup.InstanceName ... View more

Summary This article describes an Application Recognition Library (ARL) import failure error message and how to resolve it. Symptoms The ARL library import generally happens weekly. The following error message can be encountered during a failed ARL import: Exception caught: SQL Server returned error code 2627 : line: 12 in procedure: ARLRecreateSuitesDeletedByTrigger Violation of PRIMARY KEY constraint 'PK_SoftwareTitleSuite'. Cannot insert duplicate key in object 'dbo.SoftwareTitleSuite'. The duplicate key value is (175773). Cause There are some content data changes in the Nov 2015 release, however the ARL import script doesn't have correct error handling code, so the combination of the system data + the ARL content factory data updates causes this SQL violation error. There is a sample Recognition.log file attached to this article that you can use to compare whether this is the same error thrown when the import reaches the ' ARLRecreateSuitesDeletedByTrigger: ' update. Resolution A permanent fix has been added in the Jan 31st 2016 release. Try to download any version later than the above release date and it should fix the issue. If the import still experiences the same issue, please send a support request to Flexera Technical support team by submitting an updated Recognition.log file. Workaround There isn't a workaround if you don't have a newer ARL version later than Jan 31st 2016. We don't recommend a clean up your system data to avoid the SQL violation error. It should be handled by the ARL import script. ... View more

Summary This knowledge base article will describe a product defect of content library ARL import issue which cause the following library SKU , PURL not being uploaded. Symptoms User may observe from system dashboard that SKU & PURL library updated date is older than ARL library. See below screenshot of sample Please be advised , the current product limitation includes: 1. There is no failure message of ARL import failure 2. There is no alert message of SKU/PURL not being updated due to ARL import failure 3. There is no seperation import mechanism at this stage that if ARL import fails, SKU or PURL will start importing independantly. Cause The cause of other two LIbrary not being updated can be the defected recently identified in ARL import with version v2145. It was released on 22nd of June 2017. For On Premise customer 1. Check ARL import failure Please check below SQL table SELECT * FROM SoftwareRecognitionImport ORDER BY 1 DESC if the Failure Reason is about similar message "SQL Server returned error code 2627 : line: 71 Violation of UNIQUE KEY constraint 'UQ__#Upgrade__A9B787AF38CE4EA6'. Cannot insert duplicate key in object 'dbo.#UpgradeDowngradeSoftwareTitles'. The duplicate key value is (14354, -122219, 2, 2). Note: This file should not be executed manually. For manual ARL execution please call mgsImportRecognition.exe." Then your system has been impacted by the defect of ARL script released in v21145. Resolution Please import any newer ARL version released at or after 29th of July 2017 (any ARL version from v2159 or later) It will solve the ARL import failure. Consequntely your SKU and PURL will be updated accordingly. If even ARL with latest version has been imported successfully ,but your SKU or PURL are still not updated. Please collect the PURL.log from user temp and send them to Flexera Support for further investigation. ... View more

Summary This article will describe a product defect that user will receive a red error message at Raw Software Usage page under "Discovery and Inventory" Tab and provided with a SQL patch workaround in this article. Symptoms When changing the filter on the Raw Software Usage page to any value, it throws a red box error on the web UI as well as the error message in the webui.log. The error message in the webui.log looks like: [ERROR 2017-05-14 07:59:23,125 539321ms UnhandledErrors ] An unexpected error occurred (cd400e3b-0560-4af0-8be5-523ea17a9b7f) System.NullReferenceException: Object reference not set to an instance of an object. at ASP._Page_Views_IMSoftwareUsage_RunTimeTemplate_cshtml.Execute() in c:\Program Files (x86)\Flexera Software\FlexNet Manager Platform\WebUI\Views\IMSoftwareUsage\RunTimeTemplate.cshtml:line 7 at System.Web.WebPages.WebPageBase.ExecutePageHierarchy() at System.Web.Mvc.WebViewPage.ExecutePageHierarchy() at Flexera.Web.Core.Display.WebViewBase`2.ExecutePageHierarchy()   Cause This is caused by an internal SQL FUNCTION [dbo].[List_SoftwareUsageRecords] which returns the undertermined row_number() value , it will cause UI fail to load the result and red error box will be thrown. Resolution The issue was fixed in FNMS 2017 R2. Please upgrade to this version or later. Workaround   ... View more

Summary This knowledge base article will describe a current product limitation on Inventory Beacon, the system path %ProgramData% can't be customized during the beacon installation. Symptoms Due to security policies in place, some customers would like to have the ability to keep any software and data files off the c: drive. For instance the below system path folder by default will be in the C Drive. %programdata% %temp% %appdata% When deploying the Beacons, the current product will create a number of folders still being installed on the C: drive, even though the installation path had been specified as the e: drive: C:\ProgramData\Flexera Software\Beacon C:\ProgramData\Flexera Software\Beacon_tmp C:\ProgramData\Flexera Software\Compliance C:\ProgramData\Flexera Software\Incoming C:\ProgramData\Flexera Software\Beacon The beacon installer allows you to "Change Distribution Folder" when it still uses the %ProgramData% path (often defaulting to C:\ ) Cause System path -- %ProgramData% variable is still used so this setting has no effect Resolution For Product version 2015 R2 SP2 or prior, the beacon installer doesn't change the system path folder location even when the user specifies a customized location in the installation UI. Additional Information This has been submitted as an enhancement request under FNMS-18451 for future releases. At this stage we recommend customers to use the default folder location in the C drive. ... View more

Summary This knowledge base article describes an issue where the Beacon fails to upload 3rd party inventory data using ComplianceUpload. Error: The remote certificate is invalid according to the validation procedure. Symptoms This knowledge base article describes an issue where the beacon fails to upload 3rd party inventory data using ComplianceUpload. Error: The remote certificate is invalid according to the validation procedure. The specific error is: [ERROR] Package upload failed Flexera.SaaS.Transport.Core.ComplianceApiException: Could not retrieve token (An error occurred while sending the request.) ---> System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure. at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult) at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar) ? End of inner exception stack trace ? at System.Net.HttpWebRequest.EndGetRequestStream(IAsyncResult asyncResult, TransportContext& context) at System.Net.Http.HttpClientHandler.GetRequestStreamCallback(IAsyncResult ar) ? End of inner exception stack trace ? ? End of inner exception stack trace ? at Flexera.SaaS.Transport.Upload.UploadClient.CreateUploadToken(String fileName) at Flexera.SaaS.Transport.Upload.UploadClient.UploadSegment(FileSegment segment) at Flexera.SaaS.Transport.Upload.UploadProcess.TryUpload(UploadClient client, UploadedPackageFile package, Action notifySuccessfulConnection) at Flexera.SaaS.Transport.Upload.UploadProcess.Retry (String actionName, Func`2 action, Int32 times) at Flexera.SaaS.Transport.Upload.UploadProcess.ProcessPackage(UploadedPackageFile package) at Flexera.SaaS.Transport.Upload.UploadProcess.ProcessPackageList(Int32 exitCode, List`1 packages) 2015-05-19 09:13:35,305 [Upload.Program ] [INFO ] Running ComplianceUpload Cause There is a known issue (FNMS-24184) in the Inventory beacon where the affected versions are v2014 - 2015 R1 Resolution The bug is permanently fixed in FlexNet Manager Suite 2015 R2 and later version. Workaround CheckCertificateRevocation=False in the following registry location: [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ManageSoft Corp\ManageSoft\Common] ... View more

Summary This article describes a product defect which may cause upload of 3rd-party inventory result to fail and provides a workaround. Symptoms A product defect has been reported in FlexNet Manager Suite 2017 R1 & R2. If an Inventory Connection name contains trailing space, it may cause two strange behaviors below. 1. The ComplianceUpload process may fail with the error message below: [ERROR] Package upload failed System.NullReferenceException: Object reference not set to an instance of an object. at Flexera.SaaS.Transport.Upload.UploadProcess.ProcessPackageList(Int32 exitCode, List`1 packages) 2. The compressed result set of 3rd party inventory data may contain 'strange' folder structure as shown below. Cause This defect is being tracked as bug IOJ-1846345 (FNMS-52956). Resolution This issue will be fixed in a future release of FlexNet Manager Suite. Workaround A simple workaround is to remove any trailing spaces from the Inventory Connection name. ... View more

Summary This knowledge base article describes a workaround for a current limitation of FlexNet Manager Suite when an operator tries to use one-off spreadsheet upload with financial figures. Currently spreadsheet upload only supports your default currency. Synopsis There is a current limitation of FlexNet Manager Suite when an operator tries to use one-off spreadsheet upload with financial figures. Currently spreadsheet upload only supports the single currency that you have set as your corporate default currency. The highlighted column value is imported as your default currency type. Discussion Current limitations of spreadsheet uploads include: 1. Any financial value is imported as your default currency type. For example, if you have set USD as your default currency in FlexNet Manager Suite, all financial values in an imported spreadsheet are in USD. 2. There is no support for one spreadsheet containing multiple items (such as purchase orders) that refer to different currencies. All spreadsheet rows use the same default currency. Workaround Instead of using spreadsheet imports for multi-currency scenarios, use a business adapter created through the Business Adapter Studio. Business adapters have a more mature data model, and support mapping items to multiple currencies. ... View more

Summary This article will explain the situation when a FNMS OnDemand user is unable to login to the Cloud tenant system, due to the tenant license file being expired. Synopsis OnDemand customer may hit login -- Sign in Failure with error message shown below The URL will lead user to above error page looks like below: https://www.flexnetmanager.com/Suite/Login/Failure/NoRole Discussion This error is due to Cloud tenant license is over due/expired. The cloud subscription based license renew due date information can be found from below page. We strongly recommend you add above due date information into your calendar before the due day. It will be better leave enough days for communicating with Flexera Order team for the renew process. Flexera Order team will perform the cloud license renew process once customer purchase the new subscription license. Once the date is passed the renew due date, no user is able to login cloud tenant system !! Additional Information This has been reported under the issue number: FNMC-487 - Logging in to a tenant with an expired license shows permissions error instead of license error ... View more