PreviousNext
Macrovision

ACE12

FLEXnet AdminStudio 7.5 » ConflictSolver

AdminStudio Professional Edition

AdminStudio Professional Edition

ConflictSolver is included with FLEXnet 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 you are likely to use at your organization into the Application Catalog database.)

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

Output

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 replace with the [MERGE_MODULE_NAME]. However, the [ModuleID] Merge Module is not in the Application Catalog which makes proper evaluation impossible.

Summary

ACE12 Summary

Topic

Description

Conflict Type:

Conflict Rule / Files

Description:

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 you are likely to use at your organization.)

Result:

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.

Resolution Type:

Manual

Resolution:

Rebuild the package using the merge module rather than the duplicate files.

Cause

A component within one package contains a file that is found in a merge module of another package. Using merge modules is always preferable as a way to install files in a consistent fashion.

Resolution

This conflict requires a manual resolution. Follow these steps:

Task

Task

To resolve this conflict:

  1. Open the MSI package in InstallShield Editor.
  2. Once the project is open, navigate to the Components View, and find the component that needs to be modified by referring to the component name displayed in the error message.
  3. Expand the list under the component and select Files. A list of the files included with that component is displayed.
  4. Select the file that was displayed in the error message, right-click, and select Delete from the menu.
  5. Take note of the feature that the component is associated with and then navigate to the Redistributables View.
  6. In the Redistributables View, select the appropriate merge module.
  7. After selecting the merge module, move to the Conditional Installation View on the right side and select the feature that was mentioned earlier.
  8. Rebuild the package.
  9. Open ConflictSolver and reimport this package into your Application Catalog, and then use the Conflict Wizard to check it against ACE12 again.
Copyright Information | Contact Macrovision