Lately I've been seeing errors in the SQL Server Log.
Code:3930 Description:"The current transaction cannot be committed and cannot support operations that write to the log file. Roll back the transaction."
Using SQL Profiler, how can I find the exact statement that is causing this error? Which column in SQL Profiler fills the "Message" column in the SQL Error log? Unfortunately, we are only getting this in production, so I will need to run a trace there with the lightest weight trace possible. What do you folks recommend to capture the offending code?