Hi,
I am trying to validate my MSI file and I am getting this error:

ICE32 ERROR Possible Mis-Aligned Foreign Keys
ModuleSignature.1 = s144
ModuleComponents.ModuleID = s72

What is the problem? How can I fix this?

Thanks, Dafna
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
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.
Answered 03/08/2006 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
0
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
Answered 01/31/2011 by: neel_singh
Yellow Belt

Please log in to comment
0
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?
Answered 02/25/2011 by: apopompi
Orange Belt

Please log in to comment
0
This thread may help.

Spartacus
Answered 02/26/2011 by: spartacus
Black Belt

Please log in to comment
0
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!
Answered 02/26/2011 by: apopompi
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity