ACE14: Duplicate INI File in Different Components

AdminStudio 2023 | 25.0 | Application Manager

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

ACE14 checks for the existence of components with different ComponentIds that modify the same INI file entry, such as the [File Name/Section/Key/Value] entry.

Test Group/Test Category

Application Conflicts/Package Data Conflicts/INI Files

Severity

Warning

Message

The INI file entry [INI_FILE_ENTRY] in the file [INI_FILE_NAME] in the component [COMPONENT1] in the package [PACKAGE1] conflicts with the same INI file entry in the component [COMPONENT1] in the package [PACKAGE2].

Background

If the same INI file entry is modified by different components, ACE14 fails.

Resolution

Manual Fix

To resolve ACE14, change the ComponentId of the Source component to match the ComponentId of the Target component.

To resolve this conflict:

Open the MSI package in InstallShield Editor.

In the View List under Organization, click Components.

In the Components explorer, find the component that is listed in the message.

In the Component Code setting, change the value to match the component code (ComponentId) of the component in the other project.

If it is unclear what value you should use, do the following:

In InstallShield Editor, open the package that will not be edited.

In the View List under Additional Tools, click Direct Editor.

In the Tables explorer, click the Component table.

Search for the component name that is included in the message, and note the value that is listed in the ComponentId column for that component. This is the component code that you should use for the component in the other package.

On the File menu, click Save As, and save the changes as a Windows Installer Transform (.mst) file.

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 ACE14 again.