Upgrading your Sage 300 (formerly Sage ERP Accpac) installation can sometimes encounter issues. This guide will walk you through common scenarios and provide solutions to help you resolve the problem.
Scenario 1: Upgrading from an Older Version (5.5 or Earlier)
If you’re currently running Sage ERP Accpac version 5.5, 5.4, 5.3, or an earlier release, you cannot directly upgrade to the 2022 version of System Manager. Instead, you’ll need to update your data to version 5.6 before proceeding with installing the 2022 version.
For versions 5.5, 5.4, or 5.3, consult the Upgrade Guide for version 5.6 to learn how to upgrade your data to that version. If you’re using version 5.2 or earlier, you’ll need to first upgrade your database to an intermediate version (5.3, 5.4, or 5.5), then upgrade to version 5.6. Refer to the Upgrade Guide for the intermediate version you choose. Once your data is successfully upgraded to version 5.6, you can install the 2022 version of System Manager.
A. Upgrading from an Older Version (5.5 or Earlier)
- Update your data to version 5.6 before installing the 2022 System Manager
- Refer to the Upgrade Guide for version 5.6 for instructions
B. For Versions 5.2 or Earlier
- Upgrade your database to an intermediate version (5.3, 5.4, or 5.5) first
- Consult the Upgrade Guide for the intermediate version
- After upgrading to the intermediate version, upgrade to version 5.6
- Then, install the 2022 System Manager
Scenario 2: Browser Security Alert When Running Help
If you encounter a security alert related to web page security when attempting to open Sage 300 Help while running Windows with high browser security settings, you can resolve this issue by adding Sage 300 Help as a trusted site. When the alert appears, click the “Add” button to trust the Sage 300 help site.
Steps to resolve:
- Click the “Add” button when the alert appears
- This will add Sage 300 help as a trusted site
Scenario 3: Upgrading Sage 300 Intelligence Reporting
If you were previously using Sage Accpac Intelligence (SAI) with an older version of Sage ERP Accpac, it is crucial not to change the company database ID during the upgrade process. Changing the database ID and then upgrading to Sage 300 2022 Intelligence Reporting may result in the loss of all security roles set up for Intelligence Reporting in the previous version.
A. If upgrading from Sage Accpac Intelligence (SAI) with a previous version
B. Do not change the company database ID
- Changing the database ID may cause a loss of security roles set up for Intelligence Reporting
Also, Read -> Troubleshooting Common Sage 300 Errors
Scenario 4: Migrating from Pervasive to Microsoft SQL
When migrating your database from Pervasive to Microsoft SQL, and your database contains Inventory Control items with units of measure that have the same name but mixed cases (e.g., “EACH” and “Each”), it is recommended to choose a binary collation method for your SQL database.
If you use a non-binary collation method and try to load data with mixed cases, the Database Load process will fail. Alternatively, you can repair your data by standardizing the unit of measure before running Database Load.
If your database contains Inventory Control items with mixed-case units of measure
- Choose a binary collation method for your SQL database
- Non-binary collation may cause Database Load failure
B. Alternative solution: - Repair your data by standardizing units of measure before running the Database Load
Conclusion
If you continue to experience difficulties or require further assistance, reach out to our team of experts who can help you with the Sage 300 Upgrade Installation Error.
FAQs on Sage 300 Upgrade Installation Error
Q. What should I do if I’m currently using Sage ERP Accpac version 5.5 or earlier?
A. If you are using version 5.5, 5.4, or 5.3, you must first update your data to version 5.6 before installing the 2022 System Manager. Refer to the Upgrade Guide for version 5.6. If you are using version 5.2 or earlier, you need to upgrade to an intermediate version (5.3, 5.4, or 5.5) first, then upgrade to 5.6, and finally install the 2022 System Manager.
Q. I’m getting a web page security alert when trying to open Sage 300 help. What should I do?
A. If you are running Windows with high browser security settings and receive a security alert about web page security when opening Sage 300 help, click the “Add” button on the alert. This will add Sage 300 help as a trusted site, resolving the issue.
Q. I was using Sage Accpac Intelligence (SAI) with a previous version of Sage ERP Accpac. Should I change the company database ID when upgrading to Sage 300 2022 Intelligence Reporting?
A. No, do not change the company database ID. Changing the database ID and then upgrading to Sage 300 2022 Intelligence Reporting may result in the loss of all security roles set up for Intelligence Reporting in the previous version.
Q: I’m migrating my database from Pervasive to Microsoft SQL, and it contains Inventory Control items with mixed-case units of measure. What should I do?
A. If your database contains Inventory Control items with units of measure that have the same name but mixed cases (e.g., “EACH” and “Each”), it is recommended to choose a binary collation method for your SQL database. If you use a non-binary collation method and try to load data with mixed cases, the Database Load will fail. Alternatively, you can repair your data by standardizing the units of measure before running Database Load.
