Ok, I am going to try something a little more dicey with this blog entry, but since I am very PO’d about the subject right now, here goes the fireworks… 😉
Some Context, Please…
For the past several months, some of you have probably been hearing murmurs of a cool IIS utility called Debug Diagnostics Tool, DebugDiag for short. It is one of those classic internal skunk works tools, two years in the making, and built by engineers for engineers to help solve real-world user problems on IIS.
As many of you should know, IIS is basically a really thin but powerful asynchronous IO completion layer sitting on top of HTTP which can execute arbitrary DLLs or EXEs in response to HTTP requests. Ok, the request/response does not even have to be HTTP, and IIS even allows you to insert arbitrary ISAPI DLLs into the request processing pipeline to alter server behavior, but you get the general picture.
Anyways, it is a common occurrence that when you integrate several applications (either custom written or purchased) hosted on top of IIS that SOME sort of conflict is going to happen. The end result is that web applications on your server will either run very slowly, hang/not-respond, crash, or even run for some period of time before crashing/hanging. Now what? How do you troubleshoot this?
I know, I know, most of you think that your developers are heavenly angels that always write perfectly performant and scalable code and does so without defects, while the Evil Empire cannot write any software and as a prime example, IIS just crashes/hangs on its own all the time… but this is my blog entry, so hear me out.
When you see your server hanging, not-responding, or periodically crashing, that is precisely the time when you want to run DebugDiag – to either wait and catch the crash as it happens, or take an inventory of what is going on inside of IIS processes to figure out what is hanging or leaking memory and causing a crash later. This information is often a smoking gun pointing towards the code that is the actual problem… and PSS statistics show that over 90% of their “IIS is crashing/hanging” cases resolve to 3rd party code doing the crashing/hanging. Just something for you to think about…
Now, how does any of this have anything to do with me being PO’d and ranting about something related to DebugDiag? Alright… I’m getting to it already; I just need to set some context.
Chris and Kamal demo’d DebugDiag at TechEd 2005 and will continue to demo it at various MS events because we really want to drive home the point that you can actually help yourself determine what code is the actual culprit with full evidence and engage with their product support, and that most user problems on IIS are not really problems with IIS (thank you, thank you, I really appreciated the phone calls 😉 ).
You see, this is basically goodness all around…
So, Where is DebugDiag?
That’s the million dollar question (literally). Where is DebugDiag? I know that there are various URLs pointing to beta downloads of pre-release versions of DebugDiag, but when is it finally releasing?
Well, I can tell you that the DebugDiag MSI that I built has literally sat on my machine the past 45 days while we hopelessly wrestled with the behemoth that is Windows, trying to jump through all their hoops to release this tool to you… because Microsoft Download Center won’t let us put the MSI up there without a checkbox from someone in Windows, and unfortunately those folks apparently do not want us to ship tools like DebugDiag in between OS releases. We now have many more administrivia hoops to jump through, all of which raise our cost of providing such tools to you, and this is all supposedly in the name of “improving product quality” and “improving customer satisfaction” of Windows.
Yeah, let’s raise customer satisfaction by not giving users any troubleshooting tools so that they cannot figure out what went wrong, and hopefully they will blame someone else. Uh… yeah… right… uh huh, you gotcha. As Raymond Chen recent noted, who do people blame for 3rd party driver BSOD, and where is their customer satisfaction?
For example, we have to pay another party some non-trivial amount of money just to compile our own source code using the exact same system that developers use, just slightly different commandline parameters.
Huh? I’m sorry for being old fashioned, but when I pay a non-trivial amount of money, I expect non-trivial amount of work performed – like writing the MSI installer for DebugDiag or generating the EULA – and not just for someone to sit and push some “build” button on the same compilation system that the same folks in Windows wrote.
I know, we should charge them royalty of the same amount for using the system… or better yet, pay me, and I’ll gladly push the button myself.
Anyways, I think the more fearsome net effect is that from now on, you will find far fewer Windows tools from Microsoft for Windows Vista and beyond – no more Power Toys, no more DebugDiag, no more Resource Kit/Support Tools – because these tools are all technically “illegal” unless they go through the same ship cycle as Windows and achieve “Windows Quality”.
Yeah, like silly administrivia will EVER increase product quality and customer satisfaction.
Oh, this is not the end of this saga by far… I am not sitting in a cubicle, and I am not writing TPS Reports…