Let the platform do the work

Health Check Error: Incompatible Integration

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 an "Incompatible Integration" error reported by the health check.

Symptoms

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

Resolution

To address this issue, the integration will need to be uninstalled from the Module Loader interface before proceeding with the upgrade. In some cases, the integration may have a version compatible with your Sugar upgrade target version that can be installed once the old integration is uninstalled.

Note: If you are running a compatible integration version but still encounter a Health Check error, your Health Check definitions may not be up-to-date. It is recommended to uninstall the integration and reinstall it after your upgrade is complete.

Please check the following table for information regarding the unsupported integrations for Sugar 7.x and above:

Integration Name Unsupported Versions Notes
Act-On Integrated Marketing Automation for SugarCRM version 7.x Prior to 4.0

Adobe EchoSign e-Signatures for SugarCRM Prior to 1.78
Bug 79365 79076 Workaround All This package is incompatible with Sugar versions 7.11.0.0 and higher.
Bug 79365 Workaround All This package is incompatible with Sugar versions 7.11.0.0 and higher.
BulkCRUDApi All
Calculated Fields Updater All
Calendar 2.0 V1.2 003 All
ContactIndicators All
Dashboard Manager All Customers are recommended to migrate to the Dashboard Template Deployer for Sugar 7 integration.
DashboardCopyManagerSugar7 Prior to 1.7
Dedupit All
DocuSign All Customers are recommended to migrate to the Sugar Connector to DocuSign integration.
DrilldownReportsChart Prior to 1.01
Dupdetector All
DuplicateCheck Prior to 3.2
FayeBSG Sugar - Authorize.Net Integration Prior to 2.1.0.1-21
FBSG Sugar - Dashboard Manager Prior to 2.3.5
FBSG Sugar - JIRA Integration Prior to 1.3.0-21
Flexidocs for SugarCRM All
Fonality All
Forums All
Freshdesk All
GoogleSalesMap Prior to 3.0.2
HS Dashboard Manager All
INBOX25 Prior to v4.7.3 The release may be obtained through this INBOX25 support article.
INET Maps All
inetDOCS Box All
iNetEditique Prior to 1.7.3
iNetMiniETL Prior to v1.7.0
Integral Sales All
IP Restriction Manager Prior to 2.1
JJWDesign_Google_Maps All
Map to Lead All
Marketo Marketing Automation for SugarCRM
Sugar Connector for Marketo
Prior to 3.1.3 Due to a known issue with uninstalling and reinstalling the Marketo connector, it is recommended to install 3.1.3 over your prior version rather than uninstalling your prior version.
MAS90Integrator All
Net-Results Marketing Automation All This package is incompatible with Sugar versions 9.0.0 - 10.1.x inclusive.
Pardot All
PixelRiver All
Posts All
Process Manager Prior to 4.5
Process Manager 3.0 On Demand
Process Manager 4.1.2 Upgrade
Process Manager 4.3 On Demand Upgrade
All
QuickBooks Prior to 1.85.13.1
RLS Social2Sugar All
Rolustech QuickBooks Online Plugin All
RT GSync Prior to 3.7 Sugar 7.11.0.0 and greater is compatible with versions 3.7 and greater. Sugar versions prior to 7.11 are incompatible with all versions of RT GSync
RT SalesMap Prior to 4.3 Sugar 7.11.0.0 and greater is compatible with versions 4.3 and greater. Sugar versions prior to 7.11 are incompatible with all versions of RT SalesMap.
sf_SalesFusion Prior to 6.8
Sugar Integrate Essentials This package is incompatible with Sugar versions 10.2.0 and higher. It must be uninstalled prior to upgrade to 10.2.x to avoid this health check error. For Sugar versions 10.0.x and 10.1.x, the Sugar Integrate Essentials package is required when using Sugar Integrate templates.
Sugar-Constant Contact Integration Prior to 2.8.5.4.2
Sugar-MAS90 Integration All
Sugar-Sage Integration Modules All Install "FBSG Sugar - Sage Integration" version 2.10.3 or higher instead.
SugarActivityStreamPurger All This package is incompatible with Sugar versions 9.1.0 and higher because it has been integrated with the core Sugar 9.1.0 product as the "Activity Stream Purger" job. Previously installed packages must be uninstalled to avoid conflicts.
SugarChimp Prior to 7.11.3c
SugarChimp - Force Sugar 7 Upgrade Prior to 7.7b
SugarSMS All
SynoDashboardTemplates Prior to 20170424
TagMe All
Teleseller All
Tenfold Number Fields Prior to 1.7 Version 1.7 can be installed after upgrading to Sugar 7.9.3.0 or higher.
Threads All
Timeline Dashlet Activities by CARRENET with license validation All
Viabl Prior to 2.0.7
wActivities76 Prior to 3.0
wMaps All
wGauge Prior to 1.31
XperiDo_Admin_ConfigButtons_7.5_V1.0.19
XperiDo_Admin_ConfigButtons_7.6_V1.0.19
XperiDo_Admin_ConfigButtons_V1.0.18
All
XperiDo_Core_&_Modules_&_Roles_V2.0.11
XperiDo_Core_&_Modules_&_Roles_V2.0.9
All
XperiDo_Core_And_Modules_V2.0.6 All
Zendesk Prior to 2.20
Zendesk Integration Prior to 2.0.0a

Uninstalling the Package

If the integration and version referenced in the health check error are not compatible with your upgrade target version, please use the following steps to remove the integration:

  1. Navigate to Admin > Module Loader.
  2. Locate the package (e.g. Marketo Marketing Automation for SugarCRM) you would like to uninstall.
  3. Click the Uninstall button to the right of the package name.
    ModuleLoader_UninstallButton
  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 to either remove or retain the database tables:
    • Do Not Remove Tables : Select this option if the integration will be used in Sugar 7 or greater by installing a newer version or once a compatible version is developed.
    • Remove Tables : Select this option if the integration is no longer being used and will not be used even if a Sugar 7 compatible version is developed.
  1. Click "Back to Module Loader" once the uninstall is complete.
    Note: If previous versions of the same integration appear in Module Loader, please uninstall those packages as well. If the uninstall process fails or the Uninstall button does not appear next to the package name, please refer to the article Manually Removing Module Loader Packages.

Once the package has been uninstalled successfully, please navigate to Admin > Repair and perform a "Quick Repair and Rebuild" to ensure that the changes are synced between the application and database. Then, perform the health check again to confirm that the error is no longer reported.