Health Check Error: is not MB module


    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 “is not MB module” error reported by the the health check.


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


    This error occurs for any custom module installed that contains a file other than those created by Module Builder or Studio. In this example, the module was created in Module Builder, but the Example_file.php was added manually and only contains a comment. The content of the file is not a factor in this health check error. The directories that are scanned for these non-standard files are ./modules/{custom module name}/ and ./custom/modules/{custom module name}/.

    Please note that the module directory may contain multiple files that fit the criteria, but health check will only generate an output for the first file it detects in the directory. 


    To address the health check error, Sugar creates a file under ./custom/Extension/application/Ext/Include/upgrade_bwc.php during the upgrade and adds the following line to enable this module for Legacy mode:

    $bwcModules[] = 'EX_Example';

    Note: This file should never be manually modified to remove a module out of Legacy mode. Our developer guide details how to convert a module out of Legacy mode.

    The custom module will not be upgraded to the Sidecar user interface and will continue to be available with the Legacy user interface upon upgrade of your instance. It is recommended that the module be tested after upgrade to ensure that it continues to work as expected. 

    in Troubleshooting Health Check Output

    Reach out to us for help