Unnecessary Reboot Warning with .NET 2.0
I want to post this so that maybe I can educate everyone regarding an unnecessary reboot with .NET 2.0 Framework. Below is a snippet from www.asp.net forums post that I had been working on. In part of my troubleshooting, since other bizarre things had been happening (like IIS running the code with 1.1 Framework, even though IIS specifically had it as 2.0 application) was to reinstall the .NET 2.0 Framework. As expected it actually pulled up an installation wizard with the Repair and Uninstall options. I figured I'd save a step and just did a Repair. I was interrupted at the end and just quickly clicked OK. After then realizing the screen had a Checkbox that said "Reboot Now". Luckily this was just a development server, had it been a non-load balanced production server (please tell me that's not your environment) it could have caused an outage.
What I find so strange is that the .NET 2.0 Framework install and uninstall typically just needs to restart IIS, not REBOOT. So, please take this as a warning. Maybe someone can provide a logical reason for the reboot, when it's normally not necessary.
http://forums.asp.net/thread/1297442.aspx
Posted: 11-15-2006, 4:54 PM
Unrecognized attribute 'xmlns' error.
I am also experiencing the same issue.
A week ago, I installed 2.0 Framework on dev webserver that already had 1.1 on it.
Deployed my new 2.0 application, set IIS to ASP.NET 2.0 and everything worked fine.
Just today, started getting errors. First was this error: Unrecognized Attribute 'xmlns'
I noticed from the error page that it was using the 1.1 Framework even though IIS says 2.0.
I ran aspnet_regiis -i and that moved me past this error on to:
allowDefinition='MachineToApplication' beyond application level
Ironically, I also have already followed the steps mentioned above, in removing the Application, recreating the Application using it's own application pool.
I will post back once I determine the final solution.
Posted: 11-28-2006, 10:30 PM
Okay. Luckily this was a dev server so it wasn't high priority. Whew. Production continued to work fine.
It was setting the website as an application in IIS. Duh.
Which of course I had already done. The problem was due to the fact that my predecessor had set the server up under two different websites. One with an alias "intranetdev" and the other with the machine name. The intranetdev was working, but the machine name wasn't. I finally discovered this and that's what led me to the immediate solution. Of course, now, I will be verifying with my predecessor (luckily they're still around) and figure out why they heck they set up two websites.
File under: ASP.NET 2.0 IIS
David Walker has over 15 years experience in application development with over 50% of that employed as a consultant with companies such as: Texaco, Bank of Oklahoma, Winner Communications (ESPN.com) and IBM Global Services. At the age of 14, he began his application development ambitions with a Commodore 64, BASIC, and a 300 baud modem. Even at that early age, he primarily focused on two specific application types: multi-user communities and database applications.
His hunger to learn as much as possible about development lead him through courses such as DBase III, DBase IV, Pascal, C, C++, Java, and several in UNIX. He started his development career first doing heavy processing with Access and VBA, then moved on to VB 3, Oracle, and Delphi. Visual Basic was one environment that remained constant for many years, including his very first .NET projects performed in Visual Basic.NET.
After working several years on very high end internal Corporate applications, the consultant company he was working for, sought out his ideas for actual software products that could be packaged and sold. He had already developed several prototypes of a dynamic portal application, before portals even became popular, so this became the logic decision and he became the Director of Product Development. Under his direction, a team of developers and graphic artists, took a skinning approach before that become popular, and completed the core portal application, and continued on to developer 15+ add-on modules, including things such as: Help Desk Ticket Systems, Change Control, Records Management, Human Resources, and many more applications. Eventually, it spun off into it's own separate company as KnowledgeGEAR, a complete intranet in the box solution.
Having worked as a consultant, he has had a experience with a very wide range of applications and architectures, at one time, even converting several Fox Pro and GW-Basic applications to VB 6 and ASP. His early training of Unix and the C language and years of experience with JavaScript, lead him very quickly to C#, where he has remained focused ever since.
He is the current President of the
Tulsa Developers .NET user group.. He has been an MCP since 2003 and MCAD and MCSD since 2005. He is currently pursuing his MCDBA and then on to MCSE.