Installation and Upgrade

The Installation and Upgrade section covers topics including troubleshooting issues during installation and upgrade, file system permissions, hardware guidelines, and particular installation situations. For basic instructions about installing Sugar, please refer to the Installation and Upgrade Guide.

Topics

When a customer wishes to downgrade Sugar editions, the following steps must be taken. When moving from any higher edition to a lower one, we recommend making the transition first on a cloned instance for testing prior to downgrading your production instance.

The main requirements to configure Sugar using an Oracle Database Server for data storage are the following:

Sugar Serve, a customer engagement solution, and Sugar Sell, a sales automation solution, are new product offerings beginning with version 9.1.0. When migrating from Sugar Enterprise to Sugar Serve or Sugar Sell, customers should keep in mind that there are a number of features (e.g. Accounts, Contacts) available between the Sugar products that will continue to be available after migration, but there are also key features that are exclusive to certain products. For more information on the features available for each license type, refer to the User Management documentation. Please note that your database will preserve the data for any modules which are no longer available following the migration.  

After initiating the SugarCRM Installer, it will not run again without editing the {sugarroot}/config.php file. Re-running the Installer may be required if an installation failed, to install another instance or to install a fresh database.

When proceeding through a Sugar upgrade, there is a step to upload the upgrade file. This article explains what to do if you do not see the button to perform the upload in that step.

While going through a Sugar upgrade, the system may detect that no zip support is found, and the upgrade fails.

Symptom: When selecting the Upgrade Wizard, the following error message appears:

Attempting to upload the upgrade file to SugarCRM fails, returning the view to the main screen. No error messages are displayed.

The Upgrade Wizard authenticates and downloads the upgrade file as expected, but does not allow the user to select the upgrade file to continue the upgrade.

The Upgrade Wizard hangs without error at the system check when upgrading or installing a patch to SugarCRM 5.0. Refreshing the browser window does not resolve the problem.

Instances hosted on Sugar's cloud service are automatically upgraded with Sugar's periodic releases (approximately one per month) to ensure they are benefitting from the latest feature enhancements and bug fixes. The entire upgrade process is handled by the Sugar Operations team, so there is no action required on your end to receive these improvements. This article provides answers to some common upgrade questions for SugarCloud instances.

Upgrades to Sugar 8.0 are available or required for instances according to the following guidelines:

Upgrades to Sugar 9.0 are available or required for instances according to the following guidelines:

Upgrades to Sugar 9.1 are available or required for instances according to the following guidelines:

Upgrades to Sugar 9.2 are available or required for instances according to the following guidelines:

Upgrades to Sugar 9.3 are available or required for instances according to the following guidelines:

The Health Check wizard must be run when upgrading in order to evaluate your instance's ability to move to the target version. During the health check, various types of issues may be detected which can affect your ability to upgrade. This article will cover how to resolve a "Cannot Perform Collation Conversion" error reported by the health check

The Health Check wizard must be run when upgrading in order to evaluate your instance's ability to move to the target version. During the health check, various types of issues may be detected which can affect your ability to upgrade. This article will cover how to resolve a "Cannot Remove Temporary Table" error reported by the health check.

The Health Check wizard must be run when upgrading to evaluate whether your instance is suitable for upgrade. During the health check, various types of issues may be detected which can affect your ability to upgrade. This article will cover how to resolve a "Found NULL values in moduleList strings" error reported by the health check. 

The Health Check wizard must be run when upgrading to evaluate whether your instance is suitable for upgrade. During the health check, various types of issues may be detected which can affect your ability to upgrade. This article will cover how to resolve a Found "print" error reported by the health check.

The Health Check wizard evaluates whether your instance is suitable for upgrade by detecting a variety of issues that may affect your ability to upgrade. This section covers how to resolve errors reported by the health check.

The Health Check wizard must be run when upgrading in order to evaluate your instance's ability to move to the target version. During the health check, various types of issues may be detected which can affect your ability to upgrade. This article will cover the " has unsupported custom views" error reported by the health check.

The Health Check wizard must be run when upgrading in order to evaluate your instance's ability to move to the target version. During the health check, various types of issues may be detected which can affect your ability to upgrade. This article will cover the " has unsupported custom views in module directory" error reported by the health check.

The Health Check wizard must be run when upgrading to evaluate whether your instance is suitable for upgrade. During the health check, various types of issues may be detected which can affect your ability to upgrade. This article will cover the "Use of removed Underscore APIs" error reported by the health check.

The Health Check wizard must be run when upgrading in order to evaluate your instance's ability to move to the target version. During the health check, various types of issues may be detected which can affect your ability to upgrade. This article will cover the "Use of removed Sidecar Bean APIs" error reported by the health check.

Reach out to us for help