ACE22: IniFile and File Table Entries for the Same File

AdminStudio 2021 R2 | 22.0 | Application Manager

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

ACE22 checks file name/target directory pairs in the File table to see if they conflict with similar entries in the IniFile table. The IniFile and File tables can change the same physical file. As a result, this ACE identifies these duplicate file changes so that they can be evaluated.

Test Group/Test Category

Application Conflicts/Package Data Conflicts/INI Files

Severity

Warning

Message

The INI file [INI_FILENAME] installed using the File table to the destination [PATH_NAME] in the package [PACKAGE3.MSI] conflicts with the same file in the IniFile table in the package [PACKAGE4].

Background

If a file name/target directory pair in a component in the File table is also listed as an IniFile table entry, ACE22 fails.

Resolution

Manual Fix

To resolve ACE22, ensure that identically named INI files with identical destinations are identical in both the File and IniFile tables. This may involve adding or deleting sections or changing values in the INI files.

To resolve this issue:

1. In InstallShield Editor, open a transform file or MSI package that has an entry in the IniFile table.
2. In the View List under System Configuration, click INI Files Changes.
3. In the INI Files explorer, find the INI file entry that is listed in the message.
4. Analyze the sections, keywords, and values in this INI file and compare them to the INI file in the other MSI package. Edit the sections, keywords, and values in this INI file so that they match those of the second INI file. This may require adding and/or deleting data in the INI File Changes view.

To retrieve the INI file from the other MSI package, you may need to extract it from the MSI file itself or a cabinet file if the files are compressed on the source media.

5. On the File menu, click Save As, and save the changes as a Windows Installer Transform (.mst) file.
6. 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 ACE22 again.