SparkleFlow is the acclaimed packaging solution that combines all aspects of a software packaging project into a single interface. Preparing an application migration? Need to reduce your TCO? Need to manage lots of applications? Want to setup your applications right now and not waste to much of your value time? SparkleFlow Package Management offers the complete solution for creating structure in your packaging project.
Written by Manfred van Poorten
Description:
ICE02 validates that certain references between the Component, File, and Registry tables are reciprocal. These references must to be reciprocal for the installer to correctly determine the installation state of components.
Concerns:
The installer uses the KeyPath column of the Component table to detect the presence of the component listed in the Component column. The KeyPath column contains a key into the Registry or File tables. Both of these tables have a Component_ column that contains a key back into the Component table pointing to the component that controls the registry entry or file. These references must be reciprocal.
Additional information:
This ICE checks whether the links between the component table and the file and the registry are correct.
Examples of possible errors:
File: 'File1' cannot be the key file for Component: 'Component2'. The file belongs to Component: 'Component1'.
Example:
Component table:
|
Component |
ComponentId |
Directory_ |
Attributes |
Condition |
KeyPath |
|
Component1 |
|
INSTALLDIR |
0 |
|
File1 |
|
Component2 |
|
INSTALLDIR |
0 |
|
File2 |
|
Component3 |
|
TARGETDIR |
4 |
|
Registry1 |
|
Component4 |
|
TARGETDIR |
4 |
|
Registry2 |
File Table:
|
File |
Component_ |
FileName |
FileSize |
Version |
Language |
Attributes |
Sequence |
|
File1 |
Component1 |
File1 |
1024 |
1 |
NL |
|
1 |
|
File2 |
Component1 |
File2 |
1024 |
1 |
NL |
|
2 |
|
File3 |
Component3 |
File3 |
1024 |
1 |
NL |
|
3 |
Registy Table:
|
Registy |
Root |
Key |
Name |
Value |
Component_ |
|
Registry1 |
2 |
Softwareexample |
TestKey1 |
Value1 |
Component3 |
|
Registry2 |
2 |
Softwareexample |
TestKey2 |
Value2 |
Component3 |
This example produces two ICE02 errors:
1. File: 'File2' cannot be the key file for Component: 'Component2'. The file belongs to Component: 'Component1'
2. Registry: 'Registry2' cannot be the key for Component: 'Component4'. The key belongs to Component: 'Component3'
The reason for error 1: ‘File2', said to be keypath for ‘Component2', is linked in the File table to ‘Component1'.
The reason for error 2: ‘Registry2', is said to be keypath for ‘Component4', but according to the Registry table belongs with ‘Component3'.
This error has to be fixed;
Make sure your references are correct. These errors only occur when you manually have edited the tables. Neither Wise nor AdminStudio produces this error.
» Back to article overview