Sage 100 Premium to Premium Upgrades Problematic For Some
Some consultants are noting problems when upgrading or migrating Sage 100 Premium to another Premium version ( upgrade ) or server location.
The issues seem glitches with either user rights or file locking.
The big problem:
When migrations fail with an error similar to the one noted in this Sage City post (and pasted below ) - your only option might be a complete reinstallation of the Sage 100 version you are migrating to.
So far the primary workaround that I’ve heard is as follows:
After you first install the updated Sage 100 Premium and convert data - MAKE A BACKUP OF THAT CLEAN VERSION BEFORE ATTEMPTING TO MIGRATE.
Here’s what I’ve been backin up:
Make a copy of \MAS90 (and all subfolders) after you first install the upgraded Premium version
Make a SQL backup of MAS_SYSTEM ( this is key )
If your migration fails you may have no choice but to restore Sage 100 from a backup which means renaming the Sage 100 folder to old.mas90 and restoring the two backups ( #1 and #2 above ) and restarting migration.
This seems to be a known issue that isn’t documented very well except to suggest that most migration errors can only be resolved by reinstallation (or using your backup files to start again ).
Backups are you friends. Also test an initial migration and a re-migration just to be sure that you have no surprises on the day you are going live.
Read more about this in Sage City.