There could be scenarios where the lmgrd service is not coming up due to multiple reasons , here are a few checks which can be made to start with
- The folder that are chosen for lmgrd, license file and debug log should be placed inside a sub folder of Program files in C drive.
- On Windows platforms, it is best practice to set the location of debug_log_path to a sub-folder of Program Data. This location has user-write permissions by default, which are needed when the license server runs as a service with Local Service permission.
- In the windows service (Properties ->Log on) Local system account should be ticked if faced with below error
Property to be modified
- lmgrd.exe must be located in a subdirectory of Program Files (x86) (for a 32-bit lmgrd) or Program Files (for a 64-bit lmgrd) when lmgrd is being started manually.
- Before running lmgrd manually, ensure that either of the following is true:
• The vendor daemon is in the same directory as lmgrd or in one of the directories specified in the lmgrd process’s $PATH environment variable.
• For license file–based licensing, the end user has edited the license file to include the path to the vendordaemon on the VENDOR line.
Additionally, for trusted storage–based licensing on UNIX platforms, the LD_LIBRARY_PATH environment variable must include the path to the vendor daemon’s activation library component, vendor_libFNP.so.
Was this helpful?
Related Articles
Cloudscape - Subscriptions - Getting Started 5Number of Views FlexNet Code Insight Scripting - Getting Started 3Number of Views Learning resources: Getting started with FlexNet Code Insight and Open Source (OSS) 5Number of Views SDK Integration - Getting Started With Usage Intelligence - Part 1 24Number of Views Event Tracking - Getting Started With Usage Intelligence - Part 2 38Number of Views
Revenera Assistant
Online
Hi, I am Reva - Ask me anything.
Updates
No new updates
Chat
Home
Updates
/**/
Thanks for the feedback!
Your feedback has been saved.Rate this response:
1
2
3
4
5
Add Additional feedback ( Optional )
0/240
English
English
Language changed successfully
Something went wrong
Email sent successfully
Something went wrong
Case create successfully
Are you sure you want to cancel
the case creation?
Please select a product to submit the case.
Please select a product version to submit the case.
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Revenera Assistant
© 2026 Flexera Software. All Rights Reserved.
Case id: 00001065
Activity: Status change: 2 hours ago