This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Adding a web site causes a validation error
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Aug 22, 2007
05:20 AM
Adding a web site causes a validation error
I am using a basic msi project, when I add a web site using the IIS view it causes the generate msi to have a ice32 error. The error is:
ICE32 ERROR Possible Mis-Aligned Foreign Keys
ISIISCommon.1 = s50
ISWebSite.ISIISCommon_ = s72
Is anyone else seeing this? I know what the error means and how to fix it by editing the msi, but I would like a way to prevent the msi from containing the error in the first place. Is it possible to edit the ism to prevent this validation error?
I thought this had been fixed in IS 2008, I am getting this using both the standalone builder and the IS gui on clean installs and upgrades.
ICE32 ERROR Possible Mis-Aligned Foreign Keys
ISIISCommon.1 = s50
ISWebSite.ISIISCommon_ = s72
Is anyone else seeing this? I know what the error means and how to fix it by editing the msi, but I would like a way to prevent the msi from containing the error in the first place. Is it possible to edit the ism to prevent this validation error?
I thought this had been fixed in IS 2008, I am getting this using both the standalone builder and the IS gui on clean installs and upgrades.
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 03, 2007
04:26 AM
Is anyone else experiencing this or able to reproduce the error?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 11, 2007
04:36 AM
Although no one responded to this as someone else may search for info on this problem, like I did, I will post my findings here.
I raised this issue with support, who have investigated and confirmed that despite this being marked as fixed in the release notes it isn’t. Support have opened an issue for it, 1-NTJDJ. Currently they have no estimate on when it will be fixed…
I raised this issue with support, who have investigated and confirmed that despite this being marked as fixed in the release notes it isn’t. Support have opened an issue for it, 1-NTJDJ. Currently they have no estimate on when it will be fixed…