IIS 6 resets after changing ASP.NET FW version

[Guest]

Hi there,

We encounter the following problem.

When we change the .NET FW version (ASP.NET tab) in a virtual directory of
IIS, it looks like there is a IISRESET in the background; all the worker
processes are ended.

This behavior is really a problem in a production environment.

Does anyone have an idea how this can be avoided ?

Peke

 

[Michael Nemtsev]

Hello Peke,

It's feature by design. No way to cope with it

P> Hi there,
P>
P> We encounter the following problem.
P>
P> When we change the .NET FW version (ASP.NET tab) in a virtual
P> directory of IIS, it looks like there is a IISRESET in the
P> background; all the worker processes are ended.
P>
P> This behavior is really a problem in a production environment.
P>
P> Does anyone have an idea how this can be avoided ?
P>
P> Peke
P>
---
WBR, Michael Nemtsev [C# MVP]. Blog: http://spaces.live.com/laflour
team blog: http://devkids.blogspot.com/

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

 

[Walter Wang [MSFT]]

Hi Peke,

To avoid restarting the whole W3SVC process, you can put your web site in a
separate AppPool and only restart the AppPool after you changed the script
mapping of it using aspnet_regiis.exe -s. Please refer to following blog
article for complete steps:

#Jerry Orman: ASP.NET Support : ASP.NET tab forces restart of W3SVC
http://blogs.msdn.com/jorman/archive/2006/04/14/576605.aspx

Hope this helps.


Sincerely,
Walter Wang ([email protected], remove 'online.')
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications. If you are using Outlook Express, please make sure you clear the
check box "Tools/Options/Read: Get 300 headers at a time" to see your reply
promptly.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Guest]

Ok,

Thx, I'll have a look at it.

Peke