Here's one you hope you never see. "The Scheduler 0 appears to be hung". On SQL Server 2000, there's no fix, and there's not much
you can do about it. My favorite part is that it logs the SPID involved (SPID 63 in my case) but it doesn't log what the SPID was doing. Given that my server was locked up so tight I couldn't even get in locally using command-line ISQL, I have no idea what caused the problem. Excellent diagnostic help there!