How to upgrade to Sage 100 Premium 2015 or higher
Summary
- How to upgrade to Sage 100 Premium 2015 or higher
- How to upgrade from Sage 100 4.50 Premium
- How to perform Parallel Migration of Sage 100 Premium 2015 or higher
Disclaimer
Backup Warning
Use caution when working with the below product functionality. Always create a backup of your data before proceeding with advanced solutions. If necessary, seek the assistance of a qualified Sage business partner, network administrator, or Sage customer support analyst.
Database Warning
These steps require knowledge of database engines and application databases (DBs) used by your Sage product (including Microsoft/Transact SQL, Pervasive SQL, or MySQL, etc.). Customer Support is not responsible for assisting with these steps and cannot be responsible for errors resulting from changes to the database engine or DBs. Before making changes, backup all system and application DBs required for a full restore. Contact an authorized business partner or DB administrator for assistance.
Network Warning
This solution requires advanced knowledge of your network. Contact your system administrator for assistance. Modifying Windows security incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows security. Always create a backup of your data before proceeding with advanced solutions.
Operating System Warning
This solution requires advanced knowledge of your computer’s operating system. Contact your system administrator for assistance. Modifying your Windows Registry incorrectly can severely affect system operations. Sage is not responsible for operation issues caused by incorrectly modifying your Windows Registry. Always create a backup of your data before proceeding with advanced solutions.
Resolution
Installing new Sage 100 Premium Installation to new SQL Instance
- Have users exit the Source installation of Sage 100 Premium
- Stop Sage 100 Application Service for the Source installation
- Install a new SQL Instance for the New (Target) Sage 100 Installation
- Install Sage 100 Premium YYYY (YYYY= version\four-digit year) to new SQL Instance
- Install Product Update and Payroll (if you own Payroll and installing Sage 100 Premium 2018 or higher)
- Change the account running SQL Server service for new installation to LOCAL SYSTEM
- Open Start, Control Panel
- Open Administrative Tools
- Open Services
- Right-click ‘SQL Server (InstanceName)‘ and select Properties
- Note: InstanceName = name of the new Sage 100 installation SQL Instance)
- Select ‘Log On‘ tab
- Select ‘Local System account‘ radio button and or use an ‘Administrator‘ account. Do not use default NT Service account during migration
- Repeat prior step for both SQL Server current production instance and the new instance
- Select OK twice
- Restart ‘SQL Server (InstanceName)‘ service
- Exit Windows Services console
7. Verify the user who runs the Migration has the following permissions:
- SQL Server rights to backup the source SQL databases
- Operating system and network rights to read and write the source SQL server .bak files into the target SQL Server “Data” folder
(i.e. C:\Program Files\Microsoft SQL Server\MSSQL_11.SQL_INSTANCENAME\MSSQL\DATA\) - SQL Server rights to restore the .bak (backup) files from the source into the target Sage 100 SQL Server
- Operating system and network rights on the source and target Sage 100 ERP Premium systems to delete the .bak files created in Step 1 and 2
NOTE: In a workgroup (non-domain-network) environment; UAC must be disabled during the Premium to Premium Parallel Migration process.
Run Parallel Migration Utility
- Select Start, All Programs, Sage 100 YYYY, Parallel Migration Wizard
- Select ‘Sage 100 Premium ERP’ and check ‘Above step is complete’ to confirm the Firewall is configured to allow access to port 1433
- Select or Enter SQL Server Instance of Sage 100 YYYY installation
Select ‘SQL Server authentication using the login and password below” - Enter ‘SA’ logon credentials
- Select Next
- Enter New/Target Installation Password
- Select Next
- Enter Path to the MAS90 folder of the Source installation
- Select Next
- Select or Enter SQL Server Instance of Source installation
- Select ‘SQL Server authentication using the login and password below”
- Enter ‘SA’ logon credentials
Support
If necessary, seek the assistance of Acute Data Systems to help provide assistance with this process.