Software Deployment

Using Orca, you need to edit the ModuleSignature and ModuleComponents table schema and ensure that both columns ('1' and 'ModuleID') have the same string length.

Hi,

I am trying to validate my MSI file and I am getting this error:
ICE32 ERROR Possible Mis-Aligned Foreign Keys
Component.1 = s255
ModuleComponents.Component = s72

Please let me know how to fix it

Hi there,

I'm having the same error with 4 different tables (that actually show empty on my MST):
Possible Mis-Aligned Foreign Keys: ISIISCommon.1=s50 ISWebSite.ISIISCommon_=s72
Possible Mis-Aligned Foreign Keys: ISIISCommon.1=s50 ISVRootAppMaps.VRootKey=s255
Possible Mis-Aligned Foreign Keys: ISIISCommon.1=s50 ISIISMetaData.ISIISCommon_=s72
Possible Mis-Aligned Foreign Keys: Component.1=s72 ISIISWebServiceExtension.Component_=s0

I have already exported the ISWebSite, ISVRootAppMaps, ISIISMetaData and ISIISWebServiceExtension tables and manually changed the string length values, then imported them back and the ICE32 dissapears, however if I close the editor and reopen it, the string values get back the to old state, thus the ICE32 error returns on validation.

I have also tried to modify these tables through ORCA, and it's the same thing. At first, IS seem to recognize them, but as soon as the editor gets closed and reopened, it overwrites the previous values.

I have also tried to modify the tables on the MSI instead of on the MST, to no avail. Finally, I tried to import the tables, close the editor, move and rename the mst/msi and reopen (trying to break the IS cache information about this package), but after all that the values returned to the non-matching string lenghts.

I'm running out of ideas, why on earth IS keeps changing those values back?

This thread may help.

Spartacus

Thank you very much! Although it says that this can't be fix through an MST, at least gives me an option to offer to the QA revisor (rebuild the project as an ISM).

Thank you!