Debugging my tummy problem.
Posted
Thu, Apr 26 2007 18:54
by
yoda
FIX: The ThreadPoolMgr::WorkerThreadStart process may become locked in a loop condition in a .NET Framework 2.0-based application, and CPU utilization may increase to 100 percent:
http://support.microsoft.com/kb/926594/en-us
FIX: A .NET Framework 2.0 application that runs under a user account context when no user profile is associated with the user account context may crash, or you may receive an access violation error message:
http://support.microsoft.com/kb/913384/en-us
So far we've tried doing that to my tummy but we still have a bit of CPU spike. So now we've called in the doctors to look at me. We did a IIS crash dump. We had already installed the debugging tools on me (placing them at c:\debuggers like all good debuggers do) and then we did a Cscript Adplus.vbs -crash -iis to get it to dump. We called the Hospital (Microsoft) and they've set up an outpatient triage (FTP site to upload my event log and the event dump files) and we'll see what the Doctor says.
Last night one of my blog handlers... the blonde one... rebooted me right as I was in the middle of one of Nick's scripts causing my database to have to recover. Sometimes rebooting is not the answer and we do that too much around here..ya know?