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: install is requesting 'x86'
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
Nov 05, 2012
01:33 PM
install is requesting 'x86'
i have a web application install package that fails after this test
IIS6 check for ASP.NET version bitness, install is requesting 'x86'
my questions are ~
what makes the install request x86?
can i can that?
what are my options?
additional info about my failure=
installing on a x64 server with IIS6 (installs on x86server IIS6 okay)
have tried setting template summary to x64
have tried setting component 64-bit property to YES
have tried setting IIS ASP platform to both 32 & 64
have tried all of the above in multiple combinations 😞
IIS6 check for ASP.NET version bitness, install is requesting 'x86'
my questions are ~
what makes the install request x86?
can i can that?
what are my options?
additional info about my failure=
installing on a x64 server with IIS6 (installs on x86server IIS6 okay)
have tried setting template summary to x64
have tried setting component 64-bit property to YES
have tried setting IIS ASP platform to both 32 & 64
have tried all of the above in multiple combinations 😞
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Nov 05, 2012
05:33 PM
DISCOVERY!
1st, another piece of background info
= installed under "Default Web Site" which was set to ASP.NET 4.0
---
so, i discovered that if i removed the ASP.NET 4.0 setting, the package gets delivered okay
well, "okay" in that you just have to go into IIS afterward and specify 4.0 under the site's ASP.NET tab
but that seems like a small sacrifice - or does it?
1st, another piece of background info
= installed under "Default Web Site" which was set to ASP.NET 4.0
---
so, i discovered that if i removed the ASP.NET 4.0 setting, the package gets delivered okay
well, "okay" in that you just have to go into IIS afterward and specify 4.0 under the site's ASP.NET tab
but that seems like a small sacrifice - or does it?