February 4, 2013 at 7:32 pm
February 5, 2013 at 12:43 am
I get the same error only in the context of a stack dump or login failure. Eg:
Using 'dbghelp.dll' version '4.0.5'
The client was unable to reuse a session with SPID 52, which had been reset for connection pooling. The failure ID is 46. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
***Unable to get thread context for spid 0
* *******************************************************************************
*
* BEGIN STACK DUMP:
* 12/05/12 14:03:06 spid 6388
*
* Non-yielding Scheduler
*
* *******************************************************************************
Stack Signature for the dump is 0x00000000000001AE
External dump process return code 0x20000001.
External dump process returned no errors.
Process 0:0:0 (0x19cc) Worker 0x000000001BE801A0 appears to be non-yielding on Scheduler 1. Thread creation time: 12986879138906. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%. System Idle 88%. Interval: 70308 ms.
Are there any other errors reported?
March 6, 2013 at 1:00 am
Hi, This is cause by the extended events monitoring for Sharepoint 2012
In SQL2012, you can find this Sharepoint diagnostics session under the extended events tab.
March 7, 2013 at 8:09 pm
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply