ICE32 resolution
I am getting ice32 as "Possible Mis-Aligned Foreign Keys Feature.1 = s32
MsiAssembly.Feature_ = s38 http://dartools/Iceman/ice32.html _Validation"
but in the column definition of the two talbles the column is s32 & identifier.......
not able to figure out whats wrong............
MsiAssembly.Feature_ = s38 http://dartools/Iceman/ice32.html _Validation"
but in the column definition of the two talbles the column is s32 & identifier.......
not able to figure out whats wrong............
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
MSIPackager
19 years ago
Yah this is something I've been getting occasionally - not worked out why, think it's a weird bug in Wise. Anyway here's how to fix it:
Open the MSI in Orca and right click on the Feature table and select Adjust Schema from the fly-out menu. Highlight Feature_Parent and retype the Length as 32 then click OK.
Re-validate and the ICE error will disappear.
If anyone knows what causes this I'd love to hear it.
Cheers,
Rob.
Open the MSI in Orca and right click on the Feature table and select Adjust Schema from the fly-out menu. Highlight Feature_Parent and retype the Length as 32 then click OK.
Re-validate and the ICE error will disappear.
If anyone knows what causes this I'd love to hear it.
Cheers,
Rob.
Posted by:
Lillude
19 years ago
Posted by:
MSIPackager
19 years ago
Posted by:
DevGowda
19 years ago
Posted by:
MSIPackager
19 years ago
Posted by:
requim
19 years ago
The problem you are having is being caused by an improperly authored Merge Module being included into your project. I'm not sure what tool you are using to develop your MSI package, however in the tool I use WiX, I can predefine a table in my main source so that when the merge modules are included, the offending table definition is ignored since it has already been defined.
You may want to look at the tool you are using to see if a similiar feature is available. Likewise you may also want to try identifying which Merge Module has the invalid definition. Warning: The ones coming from Microsoft via Visual Studio are frequent offenders.
You may want to look at the tool you are using to see if a similiar feature is available. Likewise you may also want to try identifying which Merge Module has the invalid definition. Warning: The ones coming from Microsoft via Visual Studio are frequent offenders.
Posted by:
MSIPackager
19 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.