Summary
Validation Error/Warning ICE80
Symptoms
ICE80 is only encountered during validation and is displayed in the following formats:
- ICE80 Error The Package contains 64 bit component [COMPONENTNAME] but the Template Summary Property does not contain Intel64 or x64
- ICE80 Error This 64BitComponent [COMPONENTNAME] uses 32BitDiretory [32BITDIRECTORY]
- ICE80 Error This 32BitComponent [COMPONENTNAME] uses 64BitDiretory [64BITDIRECTORY]
- ICE80Warning This 32Bit Package is using 64Bit Locator Type in RegLocator Table Entry [REGLOCATORTABLEENTRY]
- [COMPONENTNAME] resolves to the name of a component
- [32BITDIRECTORY] resolves to a directory in the 32bit portion of the OS
- [64BITDIRECTORY] resolves to a directory in the 64bit portion of the OS
- [REGLOCATORTABLEENTRY] is an entry in the RegLocator table
Cause
There are a several causes for these validation errors and warnings.Most come down to mixing both 64Bit and 32Bit in a single installation.
- This error will occur if your install does not specified the processor type as 64bit in the 'Template Summary' and then tries to use the 64bit portion of the machine.
- This error will occur if a component is marked as 64-Bit and then targets a 32bit location
- This error will occur a component is 32-Bit and then targets a 64-Bit location
- This error will occur if a system search has been created with the option for 64Bit check and this install targets a 32bit machine.
Resolution
When it comes to an MSI you can only target 32Bit or 64Bit. There is no ability to target both processor types.When it comes to a 64Bit install you do have access to 32bit portion of the machine but with a 32Bit install you have no access at all to the 64bit portion of the machine. This means that in a 64Bit install you can utilize the 32bit portion of the machine if you need but you will need to setup the components correctly. Below are ways to resolve a lot of the ICE80 errors
- This error is caused by not targeting the correct processor. To fix this Go to the 'General Information' view under the Installation Information heading. There is an option under the 'Summary Information Stream' of 'Template Summary'. You will need to target Intel64 or x64.
- Depending on the processor you intend to target and your needs there are a few ways to resolve this error.
- If you intend to target a 64bit processor but want to install to a 32bit location then you need to mark this component as a 32bit component. This would involve changing the '64-Bit Component' option to No.
- If you intend your component to be a 64bit component then you need to change the target location to a 64Bit location
- If you intend to target a 32Bit processor then you can't mark you component as a 64Bit component. You need to make this component a 32bit component. This would involve changing the '64-Bit Component' option to No.
- Depending on the processor you intend to target and your needs there are a few ways to resolve this error.
- If you intend to target a 64bit processor and a 64bit location then you will have to mark this component as a 64bit component.This would involve changing the '64-Bit Component' option to Yes.
- If you intend to target a 64bit processor but want to install to a 32bit location then you will need to mark this component as 32bit.This would involve changing the '64-Bit Component' option to No.
- If you intend to target a 32bit processor then you will need to change the location of this 32bit component to target a 32bit location.
- Depending on the processor you intend to target and your needs there are a few ways to resolve this error.
- If you do want to target a 64bit process then you need to change the Template Summary to target Intel64 or x64.
- If you intend to target a 32bit process then you need to uncheck 'Search the 64-bit portions of the Registry' in your registry system search.
Related Articles
flxconfig does not report a validation failure if "VerifySignatureCertificateRevocation=true" and no CRLs can be downloade… 1Number of Views Exchange rate validation may fail for values < 1 if browser language uses comma (,) as a decimal separator 9Number of Views Configuring Extended Validation (EV) Certificate information in InstallShield 11Number of Views Inventory Beacon fails to upload packages to FlexNet Manager Suite Cloud, error is "The remote certificate is invalid acco… 58Number of Views Importing computer inventory data from a spreadsheet/file may fail with a validation error if 'InstanceCloudID' field is m… 4Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago