Problem re-registering license after revoking on old server

I'm attempting to transfer my FOP2 license from a server that's being decommissioned to the server that is replacing it. I used --revoke on the old server prior to shutting it down, and it seemed to go through normally. Now I'm trying to use --register on the new server, and it's complaining that my serial number can only be used to register 2.20 (I have 2.26 installed). Is there a way to register without having to downgrade/upgrade?

Comments

  • Also, when I try to register through the web interface, the FOP2 service shuts down, but never restarts (service fop2 status returns "fop2_server dead but subsys locked"). I can manually restart the service, but it comes back up in unlicensed mode. The fop2.lic file is not being written, regardless of whether root or apache owns /usr/local/fop2
  • For full licensing options you should use the command line, you cannot revoke or reactivate via web. Permissions/ownership are not needed in the /usr/local/fop2 directory. But security restrictions like selinux can cause problems.

    Any kind of licensing problem cannot be handled in the forum due to the private nature of activation codes. But I can point you at some of the restrictions and licenses manage that users should know:

    1) if you revoke version X, you can only activate version X or older (not newer)
    2) to upgrade versions, DO NOT REVOKE FIRST, just download and install the new version
    3) if you want to move servers, you must install same FOP2 versions (as you will have to revoke)
    4) if you were planning to upgrade fop2 anyways, then upgrade in the old server, then revoke and install in the new one

    If you need to install a 2.26 version over a revoked 2.20 or similar, you will have to email me privately or contact me via the live help for instructions, as I need to know your activation code.

    Best regards,
Sign In or Register to comment.