Health Check Error: Custom module with the same name as new Sugar7 module

Overview

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 "Custom module with the same name as new Sugar7 module" error reported by the health check.

Note: This article pertains to Sugar versions 12.0.0 and lower. 

Symptoms

This error generates an output similar to the following in health check:

Resolution

In this example, the root cause of this error is that a custom module is installed in Sugar with the same name as the Revenue Line Items module introduced in 7.0.0.0 for Enterprise and Ultimate editions.

To address this issue, the custom module will need to be uninstalled via Admin > Module Loader before proceeding with the upgrade. It is recommended that the table(s) be backed up before uninstalling, so the data is not lost.

Uninstalling the Package

Use the following steps to uninstall the custom module via Module Loader:

1. Navigate to Admin > Module Loader.
2. Locate the package for the custom module you would need to uninstall.
3. Click the Uninstall button to the right of the package name.
4. Click the Commit button to begin the uninstall process.
   Note: If the package has added any database tables to your instance, you will see selection options (Do Not Remove Tables, Remove Tables) to either remove or retain the database tables. If the database tables include any information you would like to keep, select the "Do Not Remove Tables" option.
5. Click "Back to Module Loader" once the uninstall is complete.
6. Navigate to Admin > Repair and run the "Quick Repair and Rebuild".
7. Run the health check again to confirm the error is no longer returned.

If uninstalling the module via Module Loader is not possible, you can disable the custom module at the file level by following the steps below:

1. Log into the server and navigate to the root directory of the Sugar instance.
2. Go to the ./custom/Extension/application/Ext/Include/ directory in the instance.
3. Create a directory named 'Disabled' if it does not already exist.
4. Locate the PHP file in the current directory that references your custom module.
5. Move that file to the 'Disabled' directory.
6. Log into Sugar as an administrative user.
7. Navigate to Admin > Repair and run the "Quick Repair and Rebuild".
8. Run the health check again to confirm the error is no longer returned.