- Flexera Community
- :
- FlexNet Manager
- :
- FlexNet Manager Suite Known Issues
- :
- Known Issue: Usage .mmi files may fail to import if any software names end with a digit or special c...
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Known Issue: Usage .mmi files may fail to import if any software names end with a digit or special character and contain a "\" after the last space (IOJ-2181551)
Known Issue: Usage .mmi files may fail to import if any software names end with a digit or special character and contain a "\" after the last space (IOJ-2181551)
Summary
Usage data gathered by the FlexNet inventory agent may fail to be recorded in the inventory database and reported in FlexNet Manager Suite if the application package name associated with any metered executable matches both the following conditions:
- The application package name ends with a digit or one of the following special characters: ()[]._
- A backslash character ( \ ) appears in the application package name after the last space (if any)
A potential symptom of this issue is that new usage files regularly appear under the C:\ProgramData\Flexera Software\Compliance\Incoming\UsageData\BadLogs directory on the inventory server (FlexNet Manager Suite On-premises edition only).
Details
An example of data usage data appearing in a usage .mmi file generated and uploaded by the agent that will cause this problem is:
<APPUSAGE NAME="Hardcopy (C:\Program Files (x86)\Hardcopy)" [...]/>
An attempt to process such a .mmi file with the mgsimport.exe tool fails with an error like the following:
Processing file C:\ProgramData\Flexera Software\Incoming\UsageData\dsk123456 at 20210323T000002.mmi.gz: EXCEPTION: -------------------- System.ArgumentException: parsing "/\A0*x86\Hardcopy/" - Unrecognized escape sequence \H. at System.Text.RegularExpressions.RegexParser.ScanCharEscape() at System.Text.RegularExpressions.RegexParser.ScanBasicBackslash() at System.Text.RegularExpressions.RegexParser.ScanRegex() at System.Text.RegularExpressions.RegexParser.Parse(String re, RegexOptions op) at System.Text.RegularExpressions.Regex..ctor(String pattern, RegexOptions options, TimeSpan matchTimeout, Boolean useCache) at System.Text.RegularExpressions.Regex.IsMatch(String input, String pattern, RegexOptions options) at ManageSoft.Usage.Importer.UsageImporter.MungeNameAndVersion(String& ioName, String& ioVersion) at ManageSoft.Usage.Importer.UsageImporter.Import(String importType, Stream inputStream, Boolean isGzipped, String sourceIdentifier, String targetFilename, MGSLicenseTermCheckResult licenseTermCheckResult, ImportProcessingStats& stats, IDispatcherPreferences preferences)
Workaround
No effective workaround to this issue is known.
Fix status
This issue is still open but not currently scheduled to be addressed.
Other information
Affected components: Uploaded file importers, Usage
Master issue ID: IOJ-2181551
Also known as: FNMS-70398
Tip: If you have been impacted by this issue, please click the KUDOS button above. This helps to track the relative significance and importance of issues. Clicking on an option against "Was this article helpful?" also helps assess and improve the usefulness of content.