Novell ADMINSTUDIO 9.5 User Manual page 1600

Chapter 20: Analyzing Installations Prior to Deployment
Predeployment Test Reference
Summary
Table 20-29 • ACE24 Summary
Conflict Type:
Description:
Result:
Resolution Type:
Resolution:
Cause
A registry entry with the same registry hive, key, and value name in a package is found in both the source and
target package, but the registry entry has a different data type or value.
Resolution
This conflict requires a manual resolution. Follow these steps:
Task: To resolve this conflict:
1. Open a transform file or MSI package in InstallShield Editor.
2. Once the project is open, navigate to the Registry view, and find the registry value causing the conflict.
Replace that value with the same registry value and data type found in the target package.
3. Select Save As from the File menu and save the changes as a Windows Installer Transform (.mst) file.
4. Open ConflictSolver and reimport this package with its transform file into your Application Catalog, and then
use the Conflict Wizard to check it against ACE24 again.
1600
Registry
Checks to see if registry entries with the same registry hive, key, and value name have
the same data type and value.
If a registry entry with the same registry hive, key, and value name in a package is found
in both the source and target packages, but the registry entry has a different data type
or value, ACE24 fails.
Manual
Investigate and decide which registry entry has precedence. If the source registry entry
has precedence over the target registry entry, remove the target registry entry.
ADS-0950-UG00 AdminStudio 9.5 User Guide