[Problem Details] You may not able to restart a probe after old expiration date surpassed, even though you have applied new probe license (with new expiration date) to UIM environment.
Here is UIM alarm you would see.
Probe 'XXX' FAILED to start, the license has expired
[Resolution] This problem is caused by controller defect, which was fixed with robot 7.80.
[Workaround] a. (If it is possible) Restart controller probe. b. (If it is possible) Deploy distsrv probe on every HUB, configure license info forwarding from distsrv which has the new probe license info.
[Note] If you have only one HUB in your UIM environment, this problem description does not apply. If you have multiple HUB in your environment, every HUB has local distsrv probe and every distsrv probe has shared the same new probe license entries, this problem description does not apply.
1. controller (robot) probe 7.05 / 7.6X / 7.70 2. HUB which the controller belongs to do not have "distsrv" probe.
(*) There are 2 types of license in UIM. "Probe license" and "HUB License" In this article, "probe license" means license for probes except for HUB. HUB probe license is managed by HUB itself.
[Problem explanation] controller probe manages every probe's license expiration date in expire.cfg in robot directory. If you have multiple HUB in your environment, technically, every HUB don't have to run local distsrv probe. When controller detects probe license expiration (upon restarting a probe), it is supposed to try to retrieve new license info using distsrv within the same HUB first, if local distsrv is not found, it is supposed to try to retrieve new license info using distsrv running on any of other HUB. However, due to controller defect, it does not work if license resolution fails using distsrv within the same HUB.