Here is the quirky error that has caused a resources crunch on a SQL instance, Error : Process ID -2 is not a valid process ID . The actual issue occurred during an update to a table that has been used by Online application to update the action log, intially the DBAs have thought it is a blocking problem and trying to catch up the SPID to kill with no success. As the existence of that process was on a minimum time and hard to catch hold, also another practice is to refer to SQL Server error log to...(
read more)
Read the complete post at http://sqlserver-qa.net/blogs/tools/archive/2009/06/11/sql-server-error-msg-6101-level-16-state-1-line-1-process-id-2-is-not-a-valid-process-id-choose-a-number-between-1-and-2048.aspx