Sage 100

Installed Sage 2018 and did a test migration of data from an existing Sage 2016 install last night. This morning the client is unable to open Sage getting the ""No valid activation found"" message. Checked and found that activate.pvx had been renamed to migrate_activate.pvx which we have seen before. Renamed it back to activate.pvx and now getting an Sy_InvalidReg: error. Tried restoring activate.pvx and same message. No hits on the Sage KB or Google. Not sure what to try next, any suggestions?

This is a WAG so try at your own risk. There is a pvxwactv.exe and a $ACTPVX.BAT file in the HOME folder. Possibly related to registration?

Also, always safer to convert from a copy of a live system rather than the live system itself...

do you get a message when you just try to run pvxwin32.exe from mas90\home on the 2016 version on the server ?

@JeffFiddelman - I do get that message when I run pvxwin32.exe from the home folder on the 2016 version on the server. I just learned that the migration failed with a message that sy0ctl.soa was missing in the 2016 version. I located that file from the previous night back and restored it, still getting the error message.

I think you have bigger issues if you can't run pvxwin32.exe... and missing Sy0ctl.soa ..... (sorry) when is their last full backup of the mas90 folder ?

We ended up restoring the MAS_SYSTEM, SOA and SY folders to fix this issue. Moral of the story is make a copy of the MAS90 folder and migrate from that.