When Runtime Errors Become Inappropriate
(Jun 04 2009 - 05:44:59 AM
by Timothy Khouri
) - [print blog
So I got an email yesterday from the Microsoft Partner Program reminding me that it's time to re-enroll BEAM 4D (the company that I work for). The email was friendly, as usual, and even provided a direct link for me to get right to the re-enrollment process.
Seeing as I was given the task to get the company certified in the program, I took it upon myself to click the link and fill out the form. What I found on the other side of the link surprised me a little.
Now don't get me wrong - runtime errors are not uncommon, and I don't think *anyone* is impervious to them. So I figured I'd wait a day and check back. Surely MS has been alerted of this error (as I refreshed several times) and by now they have diagnosed the problem and fixed it!... well, I'm still getting the error!
This lead me to posting this quick blog snippet. Since ASP.NET makes it very easy to put up a friendly looking "oops, we got an error" page... and since Microsoft developed ASP.NET... and since the MS Partner Program is all about associating yourself with highly skilled professionals... ... ... shouldn't I *not* be seeing the standard "hey, this is my first ASP.NET site" error message?
Well, at least the customErrors tag isn't set to "Off" (although it would be fun to see what the error is).
DISCLAIMER and ALL-FAIRNESS-CLAUSE
In all fairness, I've seen error messages on lots of large corporations sites. And to be even more fair, not every site/product associated with Microsoft is going to be the most dominant thing in the world.
I love Microsoft probably more than the normal fanboy, but it's always fun to screen shot these events and log them in memory (aka, a random blog on the internet).