Skip to main content
Legend
July 2, 2019
Answered

$10K CF Enterprise License Doesn't Work

  • July 2, 2019
  • 1 reply
  • 1327 views

Trying to get hold of Adobe support on this but wondering if I can get help here faster.

Just purchase the CF2018 Enterprise edition.  Enter the serial number into CFAdmin and it logs me out with this message:

"There was an error accessing this page. Check logs for more details."

Application log has this entry:

"Warning","http-nio-8500-exec-8","07/02/19","10:00:32",CFADMIN,"There was an error while verifying the token. Either the session timed out or un-authenticated access is suspected."

Ideas?

    This topic has been closed for replies.
    Correct answer pete_freitag

    The most probable cause is that you had the CF admin page with the serial number form open in your browser for a long time and the session timed out before you hit submit. If it happens repeatedly I'd try to clear cookies or try another browser.

    The license key is stored in a file called license.properties which you could try to manually update if all else fails, but I'd hope that you can get it working through CF admin.

    Pete Freitag

    Foundeo Inc. 

    1 reply

    pete_freitag
    pete_freitagCorrect answer
    Participating Frequently
    July 2, 2019

    The most probable cause is that you had the CF admin page with the serial number form open in your browser for a long time and the session timed out before you hit submit. If it happens repeatedly I'd try to clear cookies or try another browser.

    The license key is stored in a file called license.properties which you could try to manually update if all else fails, but I'd hope that you can get it working through CF admin.

    Pete Freitag

    Foundeo Inc. 

    Legend
    July 2, 2019

    I'm not sure I had the admin page open for a long time, but I tried a new browser and BINGO!  Jeez, who'd of thought.  Thanks, Pete.

    FYI, The failure was happening in FireFox.  Chrome worked.

    pete_freitag
    Participating Frequently
    July 2, 2019

    Glad you got it working, and good to know that the issue happened in FireFox. Maybe something for the Adobe team to look into if it is reproducible on FireFox.