Not sure if this is the best place to ask, but here goes:
I have a SQL Server Alert set up for Fatal error 20 on our production server. If there is a fatal error of 20, I get emailed. Ocassionally, this happens, and I get the following message:
The client was unable to reuse a session with SPID 118, which had been reset for connection pooling. The failure ID is 29. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before
this error message.
Of course, the SPID is usually different...
My problem is, I can't track down any other information about this error. There's nothing else in the SQL logs, or the Windows application logs. I would like to use profiler, but the error only happens every couple days, and I don't really want
the overhead of running profiler all the time. If I run a trace on our production server without using the profiler GUI, and store the output to a file on a different server, what would be the impact on our production server?
Any help is much appreciated!Clint
View Complete Post