Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Ravikumarc
Yak Posting Veteran
51 Posts |
 Posted - 2011-05-26 : 16:16:37
|
| Dear All,Please advice on this error message which was found in Sql server error log, Also please let me the route cause and permanent solutions for this issue. I’m using Sql server 2008 R2; Standard Edition (64-bit)MessageError: 18056, Severity: 20, State: 29.Date 5/24/2011 3:39:36 AMLog SQL Server (Current - 5/26/2011 11:00:00 AM)Source spid53MessageThe client was unable to reuse a session with SPID 53, 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.Thanks & RegardsRavi |
|
|
jason.fay
Starting Member
1 Post |
Posted - 2011-07-20 : 13:08:46
|
| I just ran into this issue myself. The ultimate fix for me was to update the Cisco branded Intel Network drivers. We're running SQL Server 2008 R2 on Windows 2008 R2 (Cisco C210 M2 hardware) with the Windows defaults for all drivers.I had been getting the same error you have below about once or twice a week. Recently the frequency of the error was increasing. I started looking at it two days ago as it was occurring about once an hour. Yesterday we were getting notifications several times an hour. Taskmanager and Perfmon cpu counters didn't show me anything. Resource Monitor showed me an interesting pattern where the cpu charts would spike to around 80% and then slowly taper off to 0% only to spike again a few seconds later. This would repeat over and over. I then downloaded Process Monitor to dig into the CPU usage more, and found that the only red flag I was seeing was that CPU Time was over 800 hours for INTERRUPTS and only 350 hours for System Idle. So I knew then that I had a hardware / driver issue that was interrupting the CPU processing.Finally, I downloaded XPERF, a tool included in the Windows SDK's and dug into the DPC charts. In there I saw that Core 0 on CPU 1 was spiking up and down from 100% utilized to 0% utilized. The interupts chart was exhibiting the same pattern. Walking into the stack with the -stackwalk PROFILE flag in XPERF, and downloading the debug symbols let me see that it was NDIS.SYS doing all the interupts and consuming the CPU Time. I then downloaded and installed the latest Intel drivers from Cisco. Everything has been fixed, DPC, Interrupts, and SQL Connectivity are back to normal. |
 |
|
|
|
|
|
|
|
Please Advice "Error:18056, Severity:20, State:29"