Technical Tip: Unable to activate fortitoken license via CLI and getting error message as import fortitoken license error :- 7566 while importing the Mobile/soft Fortitoken

[abarad]

Description	This article describes what to do when the error 'import fortitoken license error:- 7566' is showed when the mobile FortiToken is using the activation code.
Scope	Mobile/Soft FortiToken has to be imported into the FortiGate with the help of an activation code that is received at License purchase. The procedure to import the License via CLI is as below : exec fortitoken-mobile import EEEE-DDDD-CCCC-BBBB-AAAA  <---- Where EEEE-DDDD-CCCC-BBBB-AAAA is 20 digit license activation code. If the error 'import FortiToken license error:- 7566' appears, follow the solution section to resolve this issue. Why this error code occurs and what is the meaning of this error code: This error code occurs when the FortiToken license which the customer is trying to import into FortiGate is mapped with another unit serial number. For example: If FortiTken license EEEE-DDDD-CCCC-BBBB-AAAA is mapped with serial number FG100FTK20011111 and the user is trying to import this FortiToken license EEEE-DDDD-CCCC-BBBB-AAAA into the unit with serial number: FG100FTK20022222. The error message will appear on the screen while importing the license via CLI: 'import FortiToken license error:- 7566'. This error can occur in the HA environment as well as on standalone units. In an HA environment, all the FortiToken licenses should be imported on the primary devices only. There is no need to assign different levels of FortiToken license on two different units in HA. Once the FortiToken license is imported into the primary device (In HA setup) secondary unit. will automatically fetch information about FortiToken licenses.
Solution	This issue can only be resolved by mapping the FortiToken license on the proper unit serial number or transferring the existing FortiToken license to the unit serial number where the user wants to import the FortiToken license. Raise a case with FortiGate TAC CS (customer support team) for moving the license to a unit with the correct serial number with master mail id mapped with a support login account. It also asks TAC CS (customer support team) to give details of the mapped FortiToken license with the unit serial number. For the HA environment an error message as 'import FortiToken license error:- 7566' appears. On primary FortiGate and after raising a case with the TAC team you got to know that the FortiToken license is a secondary device in the HA cluster; it is possible to do a soft HA failover in this case (make current a primary unit as a secondary and set up current secondary unit role as a primary). If the TAC CS confirms that the certificates/licenses are active and valid, but still the Mobile Tokens can not be activated on the FortiGate, then check if the environment is running on multi-vdom. In case yes, make sure to check if the mobile tokens are activated under management VDOM (root VDOM ). If for some reason, it is necessary to transfer the mobile tokens from the root VDOM to another VDOM , refer to this article : Technical Tip: Moving FortiToken Mobile between VDOMs Related article: Technical Tip: How to force HA failover