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
- :
- Re: Vendor Daemon is down (Feature ... is untrusted)
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
‎Dec 18, 2014
03:45 AM
Vendor Daemon is down (Feature ... is untrusted)
Hi,
we are using InstallShield 2014 Premium and are running a FlexNet Licensing Server on a Virtual Machine for licensing the IS 2014 installation.
After rebooting the Virtual Machine we are not able to get the Vendor Daemon working again. When starting InstallShield 2014, we receive the error message "The desired vendor daemon is down. (-97, 121)".
The log file of the vendor daemon (msvn) contains the following entries:
7:45:01 (mvsn) Error: Feature IS2.win.DIM is untrusted
7:45:01 (mvsn) Error: Feature IS2.win.prem is untrusted
7:45:01 (mvsn) Error: Feature IS2.win.SAB is untrusted
7:45:01 (mvsn) License server system started on ...
7:45:01 (mvsn) No features to serve, exiting
7:45:01 (mvsn) EXITING DUE TO SIGNAL 27 Exit reason 4
Running TSConfig.exe /info returns for each registered license: Trust flags: 5, **BROKEN**
Any idea to solve this problem?
Thanks in Advance,
Dave
we are using InstallShield 2014 Premium and are running a FlexNet Licensing Server on a Virtual Machine for licensing the IS 2014 installation.
After rebooting the Virtual Machine we are not able to get the Vendor Daemon working again. When starting InstallShield 2014, we receive the error message "The desired vendor daemon is down. (-97, 121)".
The log file of the vendor daemon (msvn) contains the following entries:
7:45:01 (mvsn) Error: Feature IS2.win.DIM is untrusted
7:45:01 (mvsn) Error: Feature IS2.win.prem is untrusted
7:45:01 (mvsn) Error: Feature IS2.win.SAB is untrusted
7:45:01 (mvsn) License server system started on ...
7:45:01 (mvsn) No features to serve, exiting
7:45:01 (mvsn) EXITING DUE TO SIGNAL 27 Exit reason 4
Running TSConfig.exe /info returns for each registered license: Trust flags: 5, **BROKEN**
Any idea to solve this problem?
Thanks in Advance,
Dave
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 29, 2014
12:06 AM
After Flexera has reseted the broken licenses on their servers, i was able to active the licenses again and the vendor daemon continued working.
Thanks to the Flexera Support 🙂
Thanks to the Flexera Support 🙂
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 31, 2014
02:29 PM
If you are installing on a VM in Hyper-V make sure that the Virtual MAC address is setup as static and the same as what is in your license file.
dm@realtech wrote:
Hi,
we are using InstallShield 2014 Premium and are running a FlexNet Licensing Server on a Virtual Machine for licensing the IS 2014 installation.
After rebooting the Virtual Machine we are not able to get the Vendor Daemon working again. When starting InstallShield 2014, we receive the error message "The desired vendor daemon is down. (-97, 121)".
The log file of the vendor daemon (msvn) contains the following entries:
7:45:01 (mvsn) Error: Feature IS2.win.DIM is untrusted
7:45:01 (mvsn) Error: Feature IS2.win.prem is untrusted
7:45:01 (mvsn) Error: Feature IS2.win.SAB is untrusted
7:45:01 (mvsn) License server system started on ...
7:45:01 (mvsn) No features to serve, exiting
7:45:01 (mvsn) EXITING DUE TO SIGNAL 27 Exit reason 4
Running TSConfig.exe /info returns for each registered license: Trust flags: 5, **BROKEN**
Any idea to solve this problem?
Thanks in Advance,
Dave
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 02, 2015
12:52 AM
jpking17 wrote:
If you are installing on a VM in Hyper-V make sure that the Virtual MAC address is setup as static and the same as what is in your license file.
Thank you for this Information. I did not know, that the MAC addresses are stored in the license files.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 15, 2019
05:21 AM
I had this issue and managed to fix it myself:
Resolution:
- ​Gain GUI access onto the Machine running the License Server
- Opem cmd as Admin
- cd into the Flexera folder in Program Files
- Run 'tssconfig.exe /repair'
- Refresh the admin console (http://localhost:8090)
- Wait a bit
- Should now be fine
![](/skins/images/A5EADE085F77DE82FB3B14D6B307AE6A/responsive_peak/images/icon_anonymous_message.png)