This can be seen if the Token Application Code has been generated from an unsupported release. Confirmed to occur when generating the activation codes from Defender 5.6 (which has been out of support as of June 2016). Upgrading to the currently supported version prior to creating the Token Activation Codes should address the issue.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center