Chapter 13: Identifying and Resolving Application Conflicts Using ConflictSolver
Validating Packages
AdminStudio 9.5 User Guide
ADS-0950-UG00
1109
Handling Invalid Windows Installer Packages
Ideally, all Windows Installer packages will pass validation. Realistically, many will fail. When a package fails
validation, it means the package was not built to Microsoft’s specifications. It does not mean the installation does
not work. However, there are a few things you can do when your package has validation errors:
About ICE43, ICE50, and ICE57 Validation Rules for
Shortcuts
Each entry in the
CreateLink
section of the
.inc
file is converted into an entry in the Shortcut table. The exact
properties of the shortcut depends upon the information in the
CreateLink
line as well as the nature of the target
file itself.
ICE 43, ICE 50, and ICE 57 are the most common validation rules for shortcuts.
Shortcut Types
The primary distinction between shortcuts is advertised vs. non-advertised. Here are two reasons why it is
preferable to create advertised shortcuts:
•
Advertised shortcuts are triggers for MSI’s self-repair mechanism.
•
Non-advertised shortcuts are intended for a per-user context only:
•
The target file must be a file installed in a user-specific directory.
•
The keypath of the component containing the target file must be a user-specific registry value.
Table 13-3 •
Validation Error Solutions
Solution
Explanation
Use Tuner to correct
validation errors.
This involves opening the base package using Tuner and creating a transform
file which contains your corrections. The same validation tool is available in
Tuner.
Contact the installation
vendor.
The company that created the installation (usually the same company that
created the software) may be able to resolve the validation issues and
provide you with a valid setup. Be sure to provide the validation report to
vendors so they know where to focus.
Reconsider using the
application.
Although it might be an extreme reaction to an invalid package, there may be
compelling reasons not to use an installation not built to Microsoft guidelines.
Ignore the problems and
import the package into
ConflictSolver anyway.
This is probably the most likely scenario. The invalid installation may not be
worth trying to fix, or even have errors that you are concerned about.
ConflictSolver allows you to import an installation package regardless of its
validity; just know that there could be problems in the future in doing so.
From a practical standpoint, this may be your best option.
Summary of Contents for ADMINSTUDIO 9.5
Page 1: ...AdminStudio 9 5 User Guide Version 9 5...
Page 50: ...Contents 50 ADS 0950 UG00 AdminStudio 9 5 User Guide...
Page 52: ...52 ADS 0950 UG00 AdminStudio 9 5 User Guide...
Page 156: ...156 ADS 0950 UG00 AdminStudio 9 5 User Guide...
Page 440: ...440 ADS 0950 UG00 AdminStudio 9 5 User Guide...
Page 1090: ...1090 ADS 0950 UG00 AdminStudio 9 5 User Guide...
Page 1426: ...1426 ADS 0950 UG00 AdminStudio 9 5 User Guide...
Page 1686: ...1686 ADS 0950 UG00 AdminStudio 9 5 User Guide...
Page 1794: ...Chapter 24 AdminStudio Public API Reference 1794 ADS 0950 UG00 AdminStudio 9 5 User Guide...
Page 1842: ...Index 1842 ADS 0950 UG00 AdminStudio 9 5 User Guide...
