Forum Discussion
RPriesing_79448
Nimbostratus
NimbostratusF5 Mgmt Pack License File corrupt
F5 monitoring service won't continue to run, found these errors in F5 event log. Tried to use commands to update license, continue to get errors stating license already in use on another device. We only have one mgmt console.
This copy of F5 Networks ManagementPack for Microsoft Operations Manager is not currently licensed or the license file is corrupt. Please run f5mpcmd.exe or f5mpgui.exe specifying the /UpdateLicense with a valid registration key to create a valid license file. If you are still having problems, please contact F5 Networks technical support.
Detailed Exception Information:
F5Networks.F5Exception: This copy of F5 Networks ManagementPack for Microsoft Operations Manager is not currently licensed or the license file is corrupt. Please run f5mpcmd.exe or f5mpgui.exe specifying the /UpdateLicense with a valid registration key to create a valid license file. If you are still having problems, please contact F5 Networks technical support. ---> System.Configuration.ConfigurationErrorsException: This copy of F5 Networks ManagementPack for Microsoft Operations Manager is not currently licensed or the license file is corrupt. Please run f5mpcmd.exe or f5mpgui.exe specifying the /UpdateLicense with a valid registration key to create a valid license file. If you are still having problems, please contact F5 Networks technical support.
at F5Networks.ManagementPack.Services.DeviceMonitor.OnAsyncServiceStart()
at F5Networks.Services.WorkerServiceBase._OnAsyncServiceStartHelper()
--- End of inner exception stack trace ---
5 Replies
- Hello,
We have reviewed the license activation logs and it looks like the key was previously activated on a machine with MAC address: 00:15:5D:01:9D:28
The latest attempt to run the service and activate the key is on a machine with MAC address: 00:15:5D:0A:2C:3A
Do you recognize either of these MAC addresses? Was there a hardware change?
Thank you,
Stephen Fisher
F5 Networks 
RPriesing_79448Our OpsMgr console is running on a Hyper-V virtual machine so it's likely our Core group did a change that modified the NIC settings in the VM. 00:15:5D:0A:2C:3A is the current MAC address of the machine. How can I proceed from here?- We do have a known issue where the licensing locks the product to a few settings in the hardware environment, including the MAC address and cpu/chipset information. If these settings change, as can happen with some virtualized hosts, then the licensing checks may trigger an error. We are investigating a licensing solution, but do not currently have an ETA.
Do you expect this change to happen again? Or is this a one-time transition?
If this is a one-time transition, we can unlock the key.
If this hardware transition is expected to reoccur, then our current recommendation is to move the F5 Monitoring Service to a non-virtualized Management Server until we can resolve the hardware licensing issue.
Thank you,
Stephen Fisher
F5 Networks - RPriesing_79448From what I am told there are no plans to make any more changes. Please unlock the key when you have a chance.
Thanks - Hello,
We have put in a request for a new license key for you to activate. We hope to have it generated within 1-2 business days, if not sooner.
Thank you,
Stephen Fisher
F5 Networks
