cancel
Showing results for 
Search instead for 
Did you mean: 
IlkkaV
Pilgrim

Installation modifies unrelated application pools

I'm facing a strange issue related to application pools in IIS. The problem is that the application pool config of our latest version changes settings also for application pools created by other products (in this case our previous version). When I install our latest version, the following happens:

-All application pools targeting .NET (and ASP.NET) 2.0 get a duplicate ASP.NET v4.0 application pool
-All applications using the 2.0 pools automatically change to use the ASP.NET v4.0 version, even those that are totally unrelated to the product being installed.

Changing the .NET version of the application pool breaks our previous version, so this behavior is highly undesirable as our major versions can be installed side-by-side (product, upgrade, and component codes differ and there's no overlapping naming).

I first suspected that the issue was somehow related to .NET 4.0 installation, but that was not the case. I had the previous version installed when I upgraded my test machine to .NET 4.0 and the application pools were in their original configuration after that upgrade. However, when I installed our latest version (which uses .NET 4.0 for one of the two application pools) also the old version's application pools were modified.

Has anyone else run into this issue? All tips on how to fix this are very much appreciated.
Labels (1)
0 Kudos
17 Replies
Server
Pilgrim

Re: Installation modifies unrelated application pools

Are you sure that this is done by installation itself and not any other custom action? Like WCF activation on something like that...
0 Kudos
rrinblue22
Pilgrim

Re: Installation modifies unrelated application pools

I hope looking through the verbose installation log would help for an MSI installer
0 Kudos
IlkkaV
Pilgrim

Re: Installation modifies unrelated application pools

Server wrote:
Are you sure that this is done by installation itself and not any other custom action? Like WCF activation on something like that...


Well the change occurs as soon as the installation finishes. No additional configuration has been done to IIS or anything else on the computer, going straight to IIS manager after the installation reveals that the application pools have changed also for unrelated applications. This is also related only to IIS 7 and IIS 7.5. IIS 6.0 seems to work just fine.
0 Kudos
IlkkaV
Pilgrim

Re: Installation modifies unrelated application pools

rrinblue22 wrote:
I hope looking through the verbose installation log would help for an MSI installer


Unfortunately not, the affected unrelated application pools are not mentioned in the log at all.
0 Kudos
tjacobsky
Pilgrim

Re: Installation modifies unrelated application pools

Has there been a resolution to this issue? I am having the exact same problem and I don't know how to resolve it.
0 Kudos
BigDaddy
Pilgrim

Re: Installation modifies unrelated application pools

IlkkaV wrote:

I first suspected that the issue was somehow related to .NET 4.0 installation, but that was not the case. I had the previous version installed when I upgraded my test machine to .NET 4.0 and the application pools were in their original configuration after that upgrade. However, when I installed our latest version (which uses .NET 4.0 for one of the two application pools) also the old version's application pools were modified.


I don't think that test shows that it is not .NET 4.0 causing your problems. Just because you install something doesn't mean you use all of it. Could be that a portion of the .NET 4.0 is buggy and causing this problem but it doesn't appear until you install your latest version. ??

Not even sure about the problem, but just don't think the logic to rule out .NET 4.0 as your problem is valid.
0 Kudos
IlkkaV
Pilgrim

Re: Installation modifies unrelated application pools

BigDaddy wrote:
I don't think that test shows that it is not .NET 4.0 causing your problems. Just because you install something doesn't mean you use all of it. Could be that a portion of the .NET 4.0 is buggy and causing this problem but it doesn't appear until you install your latest version. ??

Not even sure about the problem, but just don't think the logic to rule out .NET 4.0 as your problem is valid.


It could indeed be a problem in .NET 4.0, but as it's not the .NET 4.0 that triggers the problems but our latest installer, guess who the customers are going to blame? Anyway, regardless of what's the underlying cause, I'd first and foremost need a way to fix or work around this problem.
0 Kudos
Highlighted
NassereB
Pilgrim

Re: Installation modifies unrelated application pools

Is there a resolution to this issue?

I am having the exact same problem:
- 1 application pool (asp.net 2.0) with 4 virtual directories.
- 1 application pool (asp.net 4.0) with 1 virtual directories.

After installation 4 additional apppools for each 2.0 virtual directory are created prefixed with "ASP.NET v4.0" and the 4 virtual directories point to the wrong apppools!!!

What am I doing wrong how do I resolve it.
0 Kudos
IlkkaV
Pilgrim

Re: Installation modifies unrelated application pools

NassereB wrote:
Is there a resolution to this issue?

I am having the exact same problem:
- 1 application pool (asp.net 2.0) with 4 virtual directories.
- 1 application pool (asp.net 4.0) with 1 virtual directories.

After installation 4 additional apppools for each 2.0 virtual directory are created prefixed with "ASP.NET v4.0" and the 4 virtual directories point to the wrong apppools!!!

What am I doing wrong how do I resolve it.


I have the issue solved now. In my case the final culprit was that there were overlapping internal names for IIS items. Those cannot be changed in the IIS view, so I had to use the Direct Editor and modify the ISIISItem table.
0 Kudos