This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- FlexNet Publisher
- :
- FlexNet Publisher Forum
- :
- We go the same error: Flexnet License Manager: Error in saving configuration settings
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
May 22, 2006
11:50 AM
Flexlm Windows license finder - Error in saving configuration settings
If no environment variable is set and no registry entry exists on the Windows platform, the FlexLM License Finder is invoked. On my system, after I supply a valid server name (port@host) or license file path, I get an error dialog box that says "Error in saving configuration settings". The tool then comes up, but indeed the next time I invoke, the license is again not found.
I seem to remember that the "finder" used to fix the problem, presumably by creating a registry entry. The finder never changes the registry, with or without a placetaker entry present. Registry permissions are not a factor.
Lmgrd and vendor daemons were built with 10.8.0.1. Perhaps the vendor has to implement saving the corrected settings in thier application code?
I seem to remember that the "finder" used to fix the problem, presumably by creating a registry entry. The finder never changes the registry, with or without a placetaker entry present. Registry permissions are not a factor.
Lmgrd and vendor daemons were built with 10.8.0.1. Perhaps the vendor has to implement saving the corrected settings in thier application code?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Mar 12, 2015
02:01 PM
We received the same error. Something in the registry was blocking our saving of the license server information. It could either be a software glitch or Windows security setting gone awry.