Novell ADMINSTUDIO 9.5 User Manual page 94

Chapter 2: Using the Process Assistant
ConflictSolver Process Assistant
Table 2-4 • Best Practice ACEs
ACE Rule
ACE06
ACE25
ACE26
ACE27
ACE28
ACE29
94
Description
Checks whether the
executable module (EXE,
DLL, OCX, HLP , CHM, TLB,
SYS, or DRV) within the
component is the key file.
Checks the entries in the
package's CustomAction
table to identify any hard
coded paths in the Target
field.
Checks the Merge Modules in
a package to confirm that
they have been imported into
the Application Catalog.
Checks to see if data exists in
the DuplicateFile MSI table
that is not being executed
with an associated
DuplicateFiles action.
Checks the Value field of the
package's Environment table
to identify any hard coded
paths.
Checks the Value field of a
package's IniFile table to
identify any hard coded
paths.
Result
If the executable module is
not the key file, ACE06 fails.
If a package has a hard
coded path in the Target field
of the CustomAction table, a
warning is generated.
If a package refers to a Merge
Module that does not exist in
the Application Catalog, a
warning is generated.
If a package contains data in
the DuplicateFile table but not
the necessary actions to use
this data, a warning is
generated.
If any hard coded paths exist
in the Value field of a
package's Environment table,
a warning is generated.
If the Value field of a
package's IniFile table has
any hard coded paths, a
warning is generated.
ADS-0950-UG00
CARD Resolution
The executable module is
automatically made the key
file.
Open the package file in
InstallShield Editor and
change the hard coded paths
to relative paths in the
CustomAction table.
Import the missing Merge
Module into the Application
Catalog.
Consider whether a
DuplicateFiles or
RemoveDuplicateFiles action
is needed for your
InstallExecuteSequence
table. If so, open the MSI file
in InstallShield and add the
appropriate action to the
InstallExecuteSequence
table, or remove the unused
data from the DuplicateFile
table.
Open the package file in
InstallShield Editor and
change any hard coded paths
in the Value field of the
Environment table to relative
paths.
Open the package file in
InstallShield Editor and
change any hard coded paths
in the Value field of the IniFile
table to relative paths.
AdminStudio 9.5 User Guide