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 Knowledge Base
- :
- Installing 32bit lmadmin to "Program Files (x86)" folder on 64bit Windows prevents starting it as a ...
Subscribe
- Mark as New
- Mark as Read
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Installing 32bit lmadmin to "Program Files (x86)" folder on 64bit Windows prevents starting it as a service
Installing 32bit lmadmin to "Program Files (x86)" folder on 64bit Windows prevents starting it as a service
Summary
Installing 32bit lmadmin to "Program Files (x86)" folder on 64bit Windows prevents starting it as a serviceQuestion
With FlexNet Publisher 2015 (11.13.1), if you install lmadmin on a 64bit Windows system under "Program Files (x86)" folder (since it's a 32bit program), and then try installing it as a service, there is returned the following error "System error 1067 has occurred. The process terminated unexpectedly."If you install lmadmin directly under "C:\lmadmin" then you don't get that error. Why?
Answer
This is a permissions issue, tracked as FNP-11155. To work around it, the folder permission of the "lmadmin" folder needs to be changed to "Full control" for all users of the Windows system that is being used. Once this workaround is applied, the lmadmin service starts up successfully.Additional Information
If you use our lmadmin installer to install lmadmin, then the installer ensures the directory its installed to receives the correct permissions. In 11.13.1 we made the important change to run lmadmin with least privilege, per issue FNP-10475 (please see the release notes for details). The pattern is that one-time operations that require elevated privilege should be done an installer.If using trusted storage, you need the FlexNet Licensing Service. Our best practice is to install the FlexNet Licensing Service first, and then have lmadmin 'run as administrator' when it installs itself as a service. The above error should not occur in this case.
No ratings