I was wondering if anyone has found any different ways to force-fix this "encryption key is invalid" message with newer systems. I am performing a test Sage 2016 Premium to Sage 2020 Premium upgrade + server move to a different host (so can't migrate across servers) and have performed the steps in Carmen's documentation for the "manual merge" of databases and program files on the new server. This client owns just Core modules. The data appears to convert but when trying to access various tasks, I receive the encryption key message. I have worked between the MAS_SYSTEM folder that was installed with Sage 2020 as well as the copied set of files from Sage 2016, but there's no difference. I also checked the AES Encryption Key between systems for each company in the SY_Company table and they match between the live Sage 2016 system and the test Sage 2020 system. I even tried copying one existing company to a brand new company code to see if that could reset anything but still no luck. Are there any other files that hold encryption key values that I can check besides SY_Company, maybe? Any suggestions would be appreciated. Thanks!
------------------------------
Amber Prayfrock, Blytheco
------------------------------