Sage 100

 View Only
  • 1.  "The encryption key is invalid "

    Posted 07-01-2019 17:44
    Upgrading from 2016 advanced to 2019 SU1 advanced.

    Right before the first migration of system and company files, I can run an installed module listing in 2019su1 - all good.

    Do the migration, (system and companies) - no errors.

    Start Sage100 again, and immediately re-run the installed module listing and get the error:

    "The encryption key is invalid - see your system administrator"

    I understand you can get this if you copy a MAS_XXX company folder, but that is not the case here.

    Has anyone seen this ?

    thanks
    Jeff Fiddelman

    ------------------------------
    Jeff Fiddelman
    Exeplex, LLC
    ------------------------------


  • 2.  RE: "The encryption key is invalid "

    Posted 07-01-2019 18:06
    Yes, we at TSS have run into this on 2 different installs BUT they were both standard, not Adv.  Andy has been in contact with Sage, who could not replicate on their Premium.

    ------------------------------
    Beth Bowers
    Mom to Samson, Peanut, ChiChi, Canton, and Cagney
    Beth Bowers
    269-445-1625
    ------------------------------



  • 3.  RE: "The encryption key is invalid "

    Posted 07-03-2019 09:22
    We think we have an answer on this and have communicated it to Sage.

    The system is testing company data to determine if the encryption key is valid.  This is a problem before company data conversion, as the encryption key is not in the company data.  Right after migration from older versions, none of the company data has the encryption key where they are checking.  We had company ABC, which we installed with 2019, but was not migrated, so when we added company ABC back in Company Maintenance, and changed to that company, we were able to run installed module listing, do system configuration, etc.

    Once we converted companies and changed to a converted company we could go into everything.

    We have requested that Sage not check company data when going into system things like the installed application listing, system configuration etc., or at the very least, add a message that says "Company data may need to be converted"...

    Jeff

    ------------------------------
    Jeff Fiddelman
    Exeplex, LLC
    ------------------------------



  • 4.  RE: "The encryption key is invalid "

    Posted 09-26-2019 15:56
    Running into this with v2019 ADV PU 2.  Trying to ready system for a go live over the weekend.  Imported 12 months of JE's and cannot balance to Sage 50 now.  Have determined issue happened in 2018 data.  Restored a copy of the GL that was created in v2018.  Have tried to run the data convert from company maintenance for this company but no data conversions are detected.  However, when I try to run reports, I get this error.  What needs to be modified to fire off the data conversion?

    TIA

    ------------------------------
    Jeff Schwenk
    FORMER 90M Board Member
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------



  • 5.  RE: "The encryption key is invalid "

    Posted 09-26-2019 18:54
    Wow, after waiting for three hours, there is no hope for a quick fix.  Encryption key will not allow an earlier (non 2019) version of GL to be brought in and converted.  Have to bring in the entire company folder and convert all modules....  This encryption key is a killer.

    ------------------------------
    Jeff Schwenk
    FORMER 90M Board Member
    Bottomline Software, Inc.
    Waynesboro VA
    540-221-4444
    ------------------------------