Novell ADMINSTUDIO 9.5 User Manual page 1145

Hide thumbs Also See for ADMINSTUDIO 9.5:

Table of Contents

Table 13-21 • ACE09 Summary

Description:

Resolution Type:

Two merge modules with identical ComponentIds but different versions are found in different packages.

To perform a manual resolution:

Obtain the latest version of the merge module displayed in the ACE message. The merge module may be

available for download at the vendor's web site.

Open the MSI package in InstallShield Editor.

Place the new merge module in one of the Merge Module Locations that are specified on the Merge Modules

tab of the ConflictSolver Options dialog box. This allows the merge module to be displayed in the

Redistributables view of the InstallShield Editor.

Navigate to the Redistributables View in the InstallShield Editor project. Deselect the old merge module

causing the conflict and select the new merge module in its place.

Select Save As on the File menu and save the changes as a Windows Installer Transform (.mst) file.

Open ConflictSolver and reimport this package with its newly created transform file into your Application

Catalog, and then use the Conflict Wizard to check it against ACE09 again.

ACE10 checks for the existence of identical Root/Key/Name registry combinations in components with different

ComponentIds. The ACE10 Error String is displayed in the following format:

The registry entry [REGISTRY_ENTRY] [REGISTRY_KEY] in the component [COMPONENT1] in the package

[PACKAGE1] conflicts with the same registry entry in the component [COMPONENT1] in the package

ACE10 is a warning, not an error.

AdminStudio 9.5 User Guide

Chapter 13: Identifying and Resolving Application Conflicts Using ConflictSolver

Checks to see if merge modules with identical ComponentIds are identical.

If merge modules with identical ComponentIds are different, a warning is generated.

Obtain the latest version of the merge module and rebuild the MSI.

ADS-0950-UG00

Application Conflict Evaluators (ACEs)

Troubleshooting