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: AppPool shared by two installations
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
‎Jun 16, 2011
03:38 PM
AppPool shared by two installations
I have two installations, they share the same application pool. Is there a way to overwrite the app pool each time installations are installed and to do not have it removed when one of the installation uninstalled in any order?
I tried to create a component in each installation assosiated with that app pool, that installs some empty txt with reference counting enabled, but that does not help - app pool gets uninstalled anyway.
Tried to set "Overwrite existing pool" to "No", but in this order: install first, install second, uninstall first - app pool is removed.
Ideally I'd like to overwrite it each time, so if there are some lefovers from previous uninstalls, it would get updated with the proper settings.
Please help?
I tried to create a component in each installation assosiated with that app pool, that installs some empty txt with reference counting enabled, but that does not help - app pool gets uninstalled anyway.
Tried to set "Overwrite existing pool" to "No", but in this order: install first, install second, uninstall first - app pool is removed.
Ideally I'd like to overwrite it each time, so if there are some lefovers from previous uninstalls, it would get updated with the proper settings.
Please help?
(5) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 13, 2011
01:57 PM
6 months later, I'm having this same problem.
No matter what combination of "Mark Component as Permanent" and "Overwrite Existing Application Pool" properties I use, the application pool is always uninstalled by one of the applications I've installed it with (regardless of the order of which application I uninstall).
I'm using an InstallScript project, and the Application Pool name is being dynamically set during installation using TextSubSetValue. Even tried to set the name value statically with no success.
Anyone have a solution or workaround they'd like to share? Is this a known issue and there's a hotfix or something? Am I just doing something wrong?
No matter what combination of "Mark Component as Permanent" and "Overwrite Existing Application Pool" properties I use, the application pool is always uninstalled by one of the applications I've installed it with (regardless of the order of which application I uninstall).
I'm using an InstallScript project, and the Application Pool name is being dynamically set during installation using TextSubSetValue. Even tried to set the name value statically with no success.
Anyone have a solution or workaround they'd like to share? Is this a known issue and there's a hotfix or something? Am I just doing something wrong?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 13, 2011
03:08 PM
hi,
I ended up with having components with the same name, both 64-bit, both installing same empty txt file as key file and linked to the app pool - in both installations. So now the component, that is assosiated with app.pool has 2 for reference count, and is not being removed (with app pool) until the last installation is being uninstalled.
I ended up with having components with the same name, both 64-bit, both installing same empty txt file as key file and linked to the app pool - in both installations. So now the component, that is assosiated with app.pool has 2 for reference count, and is not being removed (with app pool) until the last installation is being uninstalled.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 13, 2011
03:22 PM
Thanks for getting back to me so quickly.
So, if I understand correctly, in the Components view, for component "AppPoolComponent", you have a text file that both installations will reference.
And, in IIS view, under Application Pools, you have the App Pool name, and what are your settings for "Mark Component as Permanent" and "Overwrite Existing Application Pool"? And back in the Components view, is the component marked as "Shared"?
So, if I understand correctly, in the Components view, for component "AppPoolComponent", you have a text file that both installations will reference.
And, in IIS view, under Application Pools, you have the App Pool name, and what are your settings for "Mark Component as Permanent" and "Overwrite Existing Application Pool"? And back in the Components view, is the component marked as "Shared"?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 13, 2011
03:46 PM
Yes, and the text file has the key set - to enable reference counting - I checked after both installations installed, it equals to 2.
Overwrite - No,
Permanent - No.
I found this solution when installed A, installed B, uninstalled A and analyzed A's uninstallation log.
Overwrite - No,
Permanent - No.
I found this solution when installed A, installed B, uninstalled A and analyzed A's uninstallation log.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 10, 2012
01:47 PM
Thanks for the info (and sorry for the lateness of my reply - holidays and other work issues).
Can't get this to work on my end. Is your project InstallScript? I'm guessing not.
Also thought that this could be related to the fact that we use one installer to install these two products (multi-instance install is enabled, we have a drop down for configuration to select which product). So, maybe since this is being done from one installer, that is the root cause?
Anyone from InstallShield have a comment?
I'm thinking of just creating the App Pool using appcmd.exe so it's not logged for uninstallation, as checking the "Mark Component as Permanent" doesn't seem to have the desired affect.
Can't get this to work on my end. Is your project InstallScript? I'm guessing not.
Also thought that this could be related to the fact that we use one installer to install these two products (multi-instance install is enabled, we have a drop down for configuration to select which product). So, maybe since this is being done from one installer, that is the root cause?
Anyone from InstallShield have a comment?
I'm thinking of just creating the App Pool using appcmd.exe so it's not logged for uninstallation, as checking the "Mark Component as Permanent" doesn't seem to have the desired affect.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)