Solved

IIS restarts after building a website with .NET 2.0

Posted on 2009-04-07
10
1,113 Views
Last Modified: 2012-05-06
Hello world,

This is going to take a while to read but this is a very interesting problem that I am having and discovered.
We have started building websites with the .NET 2.0 framework on them.  The developers are coding it as such and I build the websites in the web servers in IIS.  Every time I build a website, when I go to the .NET tab and change it from .NET 1.1 to .NET 2.0 it restarts IIS.

After doing extensive testing and research, I found a hotfix (http://support.microsoft.com/kb/953343) that provides you a hotfix for this issue.  I called Microsoft and the .NET team in India gave me the hotfix.  After applying service pack 1 for 2.0 and the hotfix (in that order), we were still having the same problem.

I called Microsoft again to report this as a bug and at first they were hesitant about it and said that it was unlikely that I found a bug in one of their hotfixes (really????).  We spent about 10 hours working on this (two calls) and finally they were able to replicate the issue on their end and admitted that this is a bug; that indeed the hotfix does not fix this problem.  They went as far to tell me that according to their call records and logged issues, I was the first one to report this hotfix bug (unlikely but ok...whatever) and that they were going to give me a grace case so the developers and application team that coded this hotfix would talk to me and work to get a resolution.

I was wondering if someone out there, in this vast world of ours of IT gods, has had the same problem and if someone has found a fix/workaround for this problem.

I want to make clear that I have applied the service pack, the hotfix and that Microsoft themselves are scratching their head on this one.  Maybe someone in this great community of ours knows something about the issue.  See under the code the errors from the event viewer of one of the test boxes I am using to resolve the issue and read KB article 953343 (http://support.microsoft.com/kb/953343) before answering.  This is a tough issue and I will be willing to award the points to someone that comes up with the fix.  After testing that fix and if indeed it works, not only will I send you a box of chocolates and beer, I will award the points and make sure Microsoft hears about you so they can tell the world how to fix the issue they cannot figure out themselves.

Let the games begin!

Cheers,

Esteban Blanco, MCP, MCSE, MCTS, MCITP
Event Type:	Information

Event Source:	ASP.NET 2.0.50727.0

Event Category:	None

Event ID:	1023

Date:		4/7/2009

Time:		1:28:47 PM

User:		N/A

Computer:	DALI05WPYTEST

Description:

Restarting W3SVC
 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-------------------------------------------------------------------------------------------------------------------

Event Type:	Information

Event Source:	ASP.NET 2.0.50727.0

Event Category:	None

Event ID:	1025

Date:		4/7/2009

Time:		1:28:50 PM

User:		N/A

Computer:	DALI05WPYTEST

Description:

Finish restarting W3SVC
 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Open in new window

0
Comment
Question by:DAMAdmin
  • 6
  • 3
10 Comments
 
LVL 1

Author Comment

by:DAMAdmin
Comment Utility
Why is this a neglected question?  I think that the zones and tags are correct.  This is a very hard question in my opinion that would take possibly a Microsoft engineer to resolve.  If someone out there has seen this problem and knows how to fix it, awesome.  This is why I posted the question.
0
 
LVL 1

Accepted Solution

by:
DAMAdmin earned 0 total points
Comment Utility

Ok everyone,

I have found the fix for this. Microsoft and I worked on the issue and have a solution the we both came up with. Attached is a word document where it explains the process step-by-step. I am attaching the hotfixes for x86 and x64 versions. I suggest you contact Microsoft and get the hotfix from them using KB article 953343 in case these hotfixes attached do not match your environment.  Rename the .txt to .exe and .vbs.
DISCLOSURE:
DO NOT apply this to your production environment BEFORE testing it. You assume all responsibility by using this document attached. The document and this fix may not apply to you.

Instructions-to-prevent-IIS-rese.doc
ASPNETMapping-norestart2.0.txt
NDP20SP1-KB953343-x86.txt
NDP20SP1-KB953343-IA64.txt
0
 
LVL 51

Expert Comment

by:tedbilly
Comment Utility
I will receive no points for this comment and have nothing to gain.  I'm simply voicing an opinion.  I wouldn't even allow any of my developers to spend time on it.  It's probably why no one answered the question.  I cannot even think of a valid business case for considering this an issue.

http://thedailywtf.com/Articles/The_Complicator_0x27_s_Gloves.aspx

0
 
LVL 1

Author Comment

by:DAMAdmin
Comment Utility
Tedbilly,
Some people feel this to be true.  Neither Microsoft nor my management feel this way as I spoke to the person who actually wrote the code at Microsoft and he said that this was an issue (obviously not good enough for you).  In our environment this is a big deal.  Huge deal I should say.  We have 350 clients with websites.  When we change to .NET 2.0, IIS restarts and that brings everyone down and causes an outage that not only will cause a headache for management but it will also cause us to loose money.

This post is only for people that are having this issue and need a resolution.  Knowledgebase if you please.

I appreciate you saying that this is not even a business case and putting this post down.  There is always someone out there that will treat a colleague like this.  Your comment in my mind, just like you said this is not an issue, it's unnecessary and frankly I have no respect for people like you.

Moderator, if you feel this post that I have been working on is not "worthy" of being in this community, then delete it.  Mr. Wizard over here feels that way.

Regards,

Esteban Blanco, MCP, MCSE, MCTS, MCIPT
0
 
LVL 51

Expert Comment

by:tedbilly
Comment Utility
I didn't mean to offend, I wanted to start a meaningful discussion about whether or not this was a good practice.

For example, if I was one of your clients and was forced to upgrade to ASP.NET 2.0 I'd be concerned as well.  Considering that IIS is capable of running both ASP.NET 1.1 and ASP.NET 2.0 on the same server simultaneously was that scenario even considered?
0
Better Security Awareness With Threat Intelligence

See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

 
LVL 1

Author Comment

by:DAMAdmin
Comment Utility
Yes.  Thank you for the kind words.  What happens is that we are launching new clients (some of them) with .NET 2.0.  When I build a web that calls for .NET 2.0, after applying the setting it resets IIS on that web or app server.  Clients that are in 1.1 get affected off course.  My question to Microsoft was "is this a feature"?  They said at first that yes, it is a feature and that is why the hotfix exists for situations like mine.  The hotfix not working is what prompted me to open this discussion.  I was wondering if anyone had the same problem and if they had a resolution or work around.  When I talked to the developer that built the code for that hotfix, he and his manager told me that the hotfix doesn't work.  I posted all the stuff needed for this to work so folks in the same situation as mine can get the work around.

For us is a necessity.  We learned the hard way when I created the same website on 8 app servers and one by one was dropping, creating an outage for our clients.  I was tasked to find a solution to the problem and this is what Microsoft and I came up with.

I honestly wish that we didn't have to do this as this will slow down the process of website builds.  I am glad that there is a work around and Microsoft plans to release another hotfix at some point that will address this issue.  Most people would think that 1.1 would work for them but we have those clients wanting the platform to be 2.0.  I hope that makes more sense.
0
 
LVL 51

Expert Comment

by:tedbilly
Comment Utility
Hmm, actually that last comment was very helpful.  It gave me a far different understanding of the problem.  We haven't experienced this issue.  I'm running many web servers mostly with Windows 2003.  I have about 100 internal web sites all with different versions of ASP.NET.  We've upgraded a bunch of them from ASP.NET 1.1 to ASP.NET 2.0 without experiencing this problem.
0
 
LVL 1

Author Comment

by:DAMAdmin
Comment Utility
Man I wish we didn't have this problem.  It makes life a lot harder believe me.  Implementing this "solution" that Microsoft gave me is not going to be easy because we have to coordinate the heck out of it to prevent outages.
0
 
LVL 4

Expert Comment

by:bhermer
Comment Utility
firstly, thankyou for this, I have been tearing my hair out, I have been progmatically adding sites to IIS, and everytime I did this it bounced the whole IIS instance!

For anyone finding this who is looking for a NET solution here it is

            Dim proc As New Process()
            proc.StartInfo.WorkingDirectory = Environment.SystemDirectory & "\..\microsoft.net\framework\" & AspNetVersion
            proc.StartInfo.FileName = Environment.SystemDirectory & "\..\microsoft.net\framework\" & AspNetVersion & "\aspnet_regiis.exe"
            proc.StartInfo.Arguments = "-s W3SVC/" & WebSite & "/root/" & AppName & " -norestart"
            proc.StartInfo.UseShellExecute = False
            proc.StartInfo.CreateNoWindow = True
            proc.StartInfo.RedirectStandardOutput = True

            proc.EnableRaisingEvents = False

            proc.Start()
            Threading.Thread.Sleep(3000)

            Dim sResponse As String = proc.StandardOutput.ReadToEnd()

            If InStr(sResponse.ToLower, "finished registering") = 0 Then
                LastError = "Unable to register application with asp.net version " & AspNetVersion
                Return False
            End If
            CODE HERE TO STOP THE APP_POOL
            CODE HERE TO RESTART THE APP_POOL

0
 
LVL 1

Author Comment

by:DAMAdmin
Comment Utility
I am glad I was able to help someone in the community and give them a solid solution to their problem.
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Suggested Solutions

Running classic asp applications under Windows Server 2008 R2 (x64) and IIS 7 is not as easy as one may think. It took me a while to figure it out while getting error 8002801d a few times. After you install the OS you will need to install the fol…
Real-time is more about the business, not the technology. In day-to-day life, to make real-time decisions like buying or investing, business needs the latest information(e.g. Gold Rate/Stock Rate). Unlike traditional days, you need not wait for a fe…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
This video shows how to remove a single email address from the Outlook 2010 Auto Suggestion memory. NOTE: For Outlook 2016 and 2013 perform the exact same steps. Open a new email: Click the New email button in Outlook. Start typing the address: …

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now