| | Premium Conversion Failure and where to begin Troubleshooting |
| Resolution | - This document will assist in removing a bad installation upgrade attempt
- How to set up the new Sage 100 Premium and when to do backups
- How to vanilla down source for Migration and Conversion
- Steps to know when to put 3rd-party MODS back in
- Steps to update Data Dictionaries with Custom Office modifications from source
- Troubleshooting process:
- Uninstall Sage 100 Premium
- Remove Sage installation folder left behind
- Open Microsoft SQL Server and delete MAS_SYSTEM and all MAS_XXX databases
- Install a new instance of Sage 100 (version)
- Select MAS_MFG demo company from the Modules Listing screen during install for testing later
- Install Sage 100 (version) product update
- Log in to the new Sage to make sure it's functional and that access to Library Master functions are working as expected
- Exit Sage 100 Premium
- Backup Sage 100 (version) Premium new ..\..\MAS90 directory and all of its contents
- Open Microsoft SQL Server and create a backup of the new MAS_SYSTEM directory
- Parallel Migration is done at this phase after switching out current source Data Dictionary files from client Sage 100 Premium current installation with canned Data Dictionary files
- Providex.auc
- Providex.dcl
- Providex.dde
- Providex.ddf
- Providex.kdf
- Providex.prm
- Browse to the source ..\..\MAS90 directory and rename Providex files
- Copy in Providex files from a new installation of the source version
- Run normal Parallel Migration bringing over only the System files and VI
- Remove the new Data Dictionary files from source and rename clients Providex files back as they were so they can continue to work in the Source version or have access to that version for comparison testing (No further customizations can be done in the source version from this point forward as the System files CAN NOT be migrated again)
- Create or alter an existing User to have full Administrator rights
- Verify in Role Maintenance that the Role attached to the Admin type user has full rights, as security updates could have taken away rights in the past
- Log on with that logon and password
- Select MFG Company
- Update Data Dictionaries with source Custom Office changes by following the steps below:
- y/y = module (for example: S/0, C/I, I/M, etc.)
- xxx = company code
- 1 is returned if the last command was successful
- Click on the File menu, click Run.
- In the Program field, enter SYZCON
- Click OK.
- At the prompt, enter O=NEW("SY_ACTIVATION_BUS",%SYS_SS)
- Press ENTER.
- At the prompt, enter PRINT O'ACTIVATE("y/y","xxx")
- Notes:
- Rerun command for each Module installed
- At the prompt, enter bye
- Press ENTER
- Command window should now be closed
- Sage 100 Premium, so long as 1 returned for all command runs, knows about the Custom Office fields of client environment
- Exit Sage 100 Premium
- Backup Sage 100 (version) Premium new ..\..\MAS90 directory and all of it’s contents
- Open Microsoft SQL Server create a backup of the new MAS_SYSTEM directory
- Install client MODS as needed
- Logon to new Sage make sure its functional and that access to Library Master functions are working as expected
- Exit Sage 100 Premuim
- Backup Sage 100 (version) Premium new ..\..\MAS90 directory and all of it’s contents
- Open Microsoft SQL Server create a backup of the new MAS_SYSTEM directory
- Run Parallel Migration to bring over the datasets now that PU and MODS are back in place and functional
- Log on to Sage 100 Premium
- Open Library Master, Main, Company Maintenance
- Convert companies as normal
- Begin Testing phase after successful conversion run
|
|