Premium Conversion Failure and where to begin Troubleshooting
Description
Cause

 

 

 

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
  1. Troubleshooting process:
  2. Uninstall Sage 100 Premium
  3. Remove Sage installation folder left behind
  4. Open Microsoft SQL Server and delete MAS_SYSTEM and all MAS_XXX databases
  5. Install a new instance of Sage 100 (version)
  6. Select MAS_MFG demo company from the Modules Listing screen during install for testing later
  7. Install Sage 100 (version) product update
  8. Log in to the new Sage to make sure it's functional and that access to Library Master functions are working as expected
  9. Exit Sage 100 Premium
  10. Backup Sage 100 (version) Premium new ..\..\MAS90 directory and all of its contents
  11. Open Microsoft SQL Server and create a backup of the new MAS_SYSTEM directory
  12. 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
    1. Providex.auc
    2. Providex.dcl
    3. Providex.dde
    4. Providex.ddf
    5. Providex.kdf
    6. Providex.prm
    1. Browse to the source ..\..\MAS90 directory and rename Providex files
    2. Copy in Providex files from a new installation of the source version
  13. Run normal Parallel Migration bringing over only the System files and VI
  14. 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)
  15. Create or alter an existing User to have full Administrator rights
  16. 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
  17. Log on with that logon and password
  18. Select MFG Company 
  19. 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
  20. Sage 100 Premium, so long as 1 returned for all command runs, knows about the Custom Office fields of client environment
  21. Exit Sage 100 Premium
  22. Backup Sage 100 (version) Premium new ..\..\MAS90 directory and all of it’s contents
  23. Open Microsoft SQL Server create a backup of the new MAS_SYSTEM directory
  24. Install client MODS as needed
  25. Logon to new Sage make sure its functional and that access to Library Master functions are working as expected
  26. Exit Sage 100 Premuim
  27. Backup Sage 100 (version) Premium new ..\..\MAS90 directory and all of it’s contents
  28. Open Microsoft SQL Server create a backup of the new MAS_SYSTEM directory
  29. Run Parallel Migration to bring over the datasets now that PU and MODS are back in place and functional
  30. Log on to Sage 100 Premium
  31. Open Library Master, Main, Company Maintenance
  32. Convert companies as normal
  33. Begin Testing phase after successful conversion run

 

Steps to duplicate
Related Solutions