asked
What can cause Error: 18056 Severity:20 State:29 ?
Hi All, I have been researching this error: > Error: 18056 Severity:20 State:29 The > client was unable to reuse a session > with SPID xx, which had been reset for > connection pooling. I can not find any real concise information, so I thought I would come to the fountain of knowledge that is AskSSC. I am sure there are numerous answers to this question so specifically I would like to know; How to recreate this error at will? How connection pooling works ? (at a high level, if you can/want to go lower please do :)) How to prevent it from occuring in future ? Below is so information about my SQL Server: > **Microsoft SQL Server 2008 (SP2) - 10.0.4311.0 (X64) May 11 2011 14:27:15 Copyright (c) 1988-2008 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) (VM)** > Output from [sp_configure][1] is attached because I am having difficulty presenting it nicely in the question. Thanks all and if this has been asked and answered elsewhere please feel free to abuse me but I did have a good look before posting, MMB [1]: /storage/temp/405-sp_configure.txt
I don't know how to create this at will, but it was a problem I was running into a lot with a 2008 machine. Spending tons of time, I actually tracked it down to an out of date driver on the client side. Nothing on the server. Check there first.
@Grant Fritchey Thanks for the pointer. Will get some profiler data and attempt to track down the client. Will post back with findings.
In our environemt it seems this message is a result of availability issues with our domain controllers. Still would like to understand why DC availability results in the above error and why it is not reported for all clients and just select ones. #none_the_wiser :|
8 People are following this question.
