ACE12: Files from Merge Modules

AdminStudio 2022 | 23.0 | Application Manager

Edition:This test is included in the AdminStudio Professional and Enterprise Editions.

ACE12 checks for components that contain files that can be replaced by one of the merge modules that you have imported into the Application Catalog database. (Before running ACE12, you should import all merge modules that you are likely to use at your organization into the Application Catalog database.)

Test Group/Test Category

Application Conflicts/Package Data Conflicts/Files

Severity and Messages

ACE12 reports an error if the file in question originated from a merge module and the merge module was found in the Application Catalog. If the merge module was not found in the Application Catalog, ACE12 reports a warning:

ACE12 Output Summary

Package File	Severity	Message
Not from Merge Module	Error	The file [FILENAME] in the component [COMPONENT1] in the package [PACKAGE1] should be replaced with the merge module [MERGE_MODULE_NAME].
From Merge Module	Warning	The [FILENAME] file originating from the [ModuleID] Merge Module in package [PACKAGE1] is a candidate to be replaced with the [MERGE_MODULE_NAME]. However, the [ModuleID] Merge Module is not in the Application Catalog which makes proper evaluation impossible.

Background

ACE12 reports a warning if the file in question originated from a merge module and the merge module was found in the Application Catalog. If the merge module was not found in the Application Catalog, ACE12 reports an error.

Using merge modules is always preferable as a way to install files in a consistent fashion.

Resolution

Manual Fix

To resolve this issue:

1.

Open the MSI package in InstallShield Editor.

2.

In the View List under Organization, click Setup Design.

3.

In the Setup Design explorer, find the component that is listed in the message, expand the list under the component, and select Files. A list of the files included with that component is displayed.

4.

Right-click the file that was displayed in the error message, and then click Delete.

5.

Take note of the feature that contains the component.

6.

In the View List under Application Data, click Redistributables.

7.

Select the check box of the appropriate merge module.

8.

In the Conditional Installation pane, select check box of the feature that contains the component.

9.

Rebuild the package.

10.

Open Application Catalog and reimport this package with its transform file into your Application Catalog, and then use the Conflict Wizard to check it against ACE12 again.