Overview
This article shows license administrators how to capture FlexNet license usage data from an nTop floating license server, remove names and machine details, and send it to nTop if requested. It follows Revenera’s official FlexNet Publisher License Administration Guide and assumes your server is already set up as described in Getting Started with FlexNet Floating License. nTop may ask for usage data to troubleshoot checkout failures or denials, confirm how many seats your team uses at peak, or help you right-size your license count at renewal. We only need to see when licenses were checked out, returned or denied, and how many and NOT who your users are.Before you begin
- Administrator access to the license server machine. Run LMTOOLS, Command Prompt and PowerShell as administrator.
- The nTop license tools.
lmutil,lmgrd, LMTOOLS and the nTop vendor daemon (ntoplm.exe) are installed byntoplm-1.0.0.msiinto thentoplmfolder inside your nTop installation folder. The commands below are run from that folder. - Your license server address, in the form
port@hostname(for example,27000@licserver). - A folder the license service can write to. Revenera recommends a sub-folder of
C:\ProgramDatabecause the license service, running as LocalService, can write there by default. This article usesC:\ProgramData\nTopLM\logs. Create it before you start.
Which files nTop needs
FlexNet produces three kinds of usage data. Support will usually ask for the debug log and a status snapshot. Send the report log only if we ask for it.
Revenera describes each log in Debug Log File and Report Log File.
Step 1: Turn on usage logging
You turn on logging in an options file, a plain-text file the nTop vendor daemon reads at start-up. Do this once; logging then continues until you change it. Collect at least two weeks of data before sending it, so it covers a normal work cycle.- In the folder that holds your nTop license file, create a text file named
ntoplm.opt. The vendor daemon finds a file with this name automatically. If you keep it elsewhere, add its path to theVENDOR ntoplmline of the license file asOPTIONS=<path>. - Add these two lines (keep the quotes):
+appends to the file instead of overwriting it each time the server restarts.OBF_ADDMARKplaces markers around each user name in the debug log (for example OBF_STRT:jsmith:OBF_END@ENG-WS-042). The Step 4 script handles these markers.HIDE_USERhashes user names (SHA-2) before they are written to the report log.
- Apply the change. In LMTOOLS, open Start/Stop/Reread and click ReRead License File, or run
lmutil lmreread -c 27000@licserverfrom the ntoplm folder, or restart the nTopLM service. - Confirm a file named ntoplm_debug.log now appears in C:\ProgramData\nTopLM\logs. Open it in a text editor and check for OUT: and IN: lines after someone opens and closes nTop.
Note: File Explorer may show the size as 0 KB while the server has the file open; that is normal.
<lmadmin data folder>\logs by default. The ntoplm.opt lines above still apply.
Older servers: OBF_ADDMARK and HIDE_USER are newer keywords. If the debug log reports an error for either line, remove that keyword, reread, and redact the log by hand in Step 4.
References: DEBUGLOG, REPORTLOG, Creating an Options File.
Step 2: Capture a status snapshot
A snapshot shows license counts and current usage at one moment. Take it while the issue is happening, or at a busy time of day.- Open Command Prompt as administrator and go to the
ntoplmfolder. - Run this command, replacing the server address with yours:
--no-user-info reports feature usage without listing individual users. If your version does not recognize it, run lmutil lmstat -a -c 27000@licserver instead and redact the result in Step 4.
This output leaves out the license server and vendor daemon status lines. If Support asks for server status, also run lmutil lmstat -lm -vd -c 27000@licserver (it lists no users).
3. Open ntoplm_status.txt and check that it lists each feature you are licensed for (for example ntop_full, and ntopcl_full if your license includes it) with their issued and in-use counts.
Without --no-user-info, lmstat -a lists each user’s name, computer, display, checkout time and process ID (lmstat reference).
Step 3: Collect the files
Copy the files into one working folder, for exampleC:\ProgramData\nTopLM\to_share. Always copy, never move: the server is still writing to the originals.
ntoplm_debug.logfromC:\ProgramData\nTopLM\logsntoplm_status.txtfrom Step 2- Only if Support asked for it: the report log. First close it so the copy is complete, by switching the server to a new report log file:
- Only if Support asked for it: the server (lmgrd) debug log. Its location is the Path to the debug log file field under Config Services in LMTOOLS.
Step 4: Remove personal information
Replace names with consistent placeholders (user001, host001) rather than deleting lines. nTop still needs to count distinct users and see every checkout and denial; we do not need to know who they are. Work on the copies in your to_share folder only.
A typical debug log line before and after redaction:
4a. Replace user names, computer names, IP addresses and personal paths
This PowerShell script replaces every user@computer pair with a consistent placeholder, replaces the license server’s host name with licserver, masks user names in C:\Users… paths, and masks IPv4 addresses. Run it on the license server itself. It also saves a key file mapping each placeholder to the real name. Keep the key file; do not send it. It lets you match nTop’s findings back to real users. Run it in PowerShell, adjusting$in to your file:
4b. Review by hand before sending
Scripts catch the common patterns, not every one. Open each file in a text editor and search for:- Any remaining user or computer names, including on
DENIEDand error lines - Your license server’s own host name. The script replaces it, but check for any fully qualified form for example
licserver.corp.example.com - File paths containing a person’s name outside C:\Users (the script covers
C:\Users\jsmith\...) - Email addresses, domain names, or project names you consider confidential
- In an
lmstatfile made without--no-user-info, the per-user lines under each feature. Delete them and keep the counts
HIDE_USER (Step 1) to protect user names in it. If you cannot share it as-is, tell Support and send only the debug log.
Step 5: Send the files to nTop Support
- Put only the redacted files in a new folder:
ntoplm_debug_redacted.log,ntoplm_status.txtand, if requested,ntoplm_report.rl. Leave out the key file, the original logs and your license file. - Compress the folder into a .zip file named with your company name and date, for example
Acme_ntoplm_logs_2026-10-19.zip. - Open a ticket at Request Support and attach the .zip. Include:
- The period the logs cover
- Your FlexNet Publisher version (from
lmutil lmver lmgrd.exe) - What you would like us to look at, such as denials, peak usage, or a server error
- ITAR customers: use the Request ITAR Support option on the same page instead of the standard form.
Troubleshooting and FAQ
No log file appears after the reread. Look for “Options file used:” in the lmgrd output or the LMTOOLS server log. If it is missing, check thatntoplm.opt is in the same folder as the license file, or that the VENDOR ntoplm line points to it. Check that the log folder exists and that the license service can write to it. Then restart the nTopLM service.
The debug log is very large. Add AUTO_ROLLOVER 100 (size in MB) to the end of the DEBUGLOG line. The log also rolls over at midnight. Send the files covering the requested period.
Can I log fewer events? The NOLOG keyword can suppress IN, OUT or DENIED lines, but please leave them on. They are exactly what nTop needs to analyze usage (NOLOG).
Does logging slow the server? Debug and report logging are normal FlexNet operation. Running lmstat -a repeatedly on a busy server can be slow; Revenera calls it a potentially expensive command, so run it once per snapshot.
Can nTop identify my users from the redacted files? No. Only you hold the key file that maps placeholders to real names.
References
Revenera FlexNet Publisher License Administration Guide:- Debug Log File · Debug Log Messages · Informational Messages
- Report Log File · REPORTLOG · lmswitchr
- DEBUGLOG · NOLOG · Creating an Options File
- Capturing Debug Log Output for a License Server
- lmstat · · Command-Line Utilities

