This is *way* outside what I normally have to deal with. Yeah, I've got some websites, but they're on shared hosting and I don't have admin rights to the servers, and hey, they just work ... and that's a good thing :)
As I mentioned in my latest CrystalReports post, I had trouble with a new web app on a brand new state-of-our-art Windows 2003 IIS 6.0 web server. The app runs in (also state-of-our-art) VS2005 no problem, but I thought it would be nice at this point in the cycle to get it on the server, to test from there as well, and since I was hassling IT over other things, it seemed like a good time to ask for an alias for this.
I had initially been told that the server did NOT have .NET 1.1 on it. But... when I fired up the IIS Manager (after I FINALLY got admin rights), the tool allowed me to select either 1.1 or 2.0, so hey... let's just put up the legacy code and I'll deal with the other later, so I went with 1.1.
So now at the end of the process, I got the alias to my new app. When I tried to run my .NET 2.0 app however, it fell over... it was giving me "404 - Page Not Found" errors. I dorked around with that for some unknown quantity of time doing the 'insanity thing' .. you know... continuing to do the same thing repeatedly, hoping for different results? ... but alas, nothing worked. I compared all the properties, all the user permissions, everything in sight between a running .NET 1.1 app and a non-running .NET 2.0 app.
I also noted that in the add/remove programs, .NET 2.0 was there, but there was no .NET 2.0 entry in the controlpanel admins area, but there WAS one for .Net 1.1 ... so that was curious.
Finally I blew the whistle on myself and did a shout out to my local .NET group, AZGroups. Didn't take long before Robert Miller and Jonas Bush replied and said "Depending on the install order, you may have to re-register the .Net 2.0 framework to IIS."
Being out of my comfort zone, I googled that and found this page, of which the most important part for me was the registration line:
C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i -enable
I ran that, and everybody's up and happy and I'm glad I don't have to mess with it anymore. I'm listing this here as much for my reference as anyone else's :)
Stay in the 'Light!
Twitter SLNews | Join me @ SilverlightCream | SL Web Articles | SL2 Web Articles | My Articles | My Tutorials | My Tooltips | My SL2 Articles | My SL2 ToolTips | SilverlightCream
posted @ Thursday, May 08, 2008 9:57 AM