Ok, say that 5 times real fast :)
The things a person finds themselves involved in while trying to grub through the day and leave enough brain cells functional for Silverlight before crashing out...
At my client's facility, we had a server with our web apps and other folks' apps that not only was past it's prime (aren't we all), but the lease was up. Let's not ignore the fact that we had another server with our Oracle database on it go down the same path close enough behind that we switched them the same day.
So now all this goodness lives on a Virtual server somewhere in the sky. I and at least one other person have admin rights to the server, because nobody in IT would lay claim to enough info to be able to take care of what I needed.
I've labored through Crystal Reports issues and all kinds of stuff, but bottom line is right now I have 3 .NET 1.1 apps living out on that server and one test 'Merge' app that is a .NET 2.0 version of two of the 1.1 ones that I'm merging.
Everything has been running, and seemingly without issue for almost a month I think. I'm the only one running the 'Merge', but there's one other app that lives out on that server that I am not familiar with.
Today I tried to run some feature on one of the 1.1 apps, and it fell down... weird because it hasn't changed. So I debugged into it heavily, and could not find anything amiss. Out to the server, bring up the IIS manager and start comparing to one that works: the Merge.
Whoa... my .NET 1.1 apps are set in the ASP.NET tab as being 2.0! ... hmmm... I didn't do that, but I do know that the other team's app is 2.0 -- I stored that in the back of my head, and switched my two back to 1.1
So that got me past that point, and I went about configuring more funtionality in the 'Merge', and decided to publish to see if there are any difficulties and WHAM! ... it wouldn't run... no yellow marked errors, just a banner saying that the application won't be running, and check the log. I did, and found the message in the Title.
Off to Google... first page was in Blogspot -- and that gave me the IT banner about games and social networking, pron, yadda yadda... sigh... next... ultimately I found this great site and one of my main reasons for blogging about this:
How to run ASP.NET 2.0 and ASP.NET 1.1 side-by-side
Gotta love it when the 'state-of-our-art' in this place is bailed out by an article written April 8, 2006... LOL
So not knowing for sure if the other admin had actually modified my app to be 2.0, I went ahead and made myself 2 new AppPools, one for 1.1 and one for 2.0 then switched all 3 1.1 apps of mine to the 1.1 App Pool, and the 'Merge' to the 2.0 app pool. I'll assume that wherever the other admin is running, he can straighten it out if I've messed him up. I didn't change the default though, so I think he's ok, and since he's the only one running on the default, maybe a start/stop cycle would fix it anyway.
I know all of mine are fine, so that's cool, and another mystery solved !
-Dave
posted @ Wednesday, May 21, 2008 4:39 PM