Error: 18056, Severity: 20, State: 29.

Question

Error: 18056, Severity: 20, State: 29.

kvishu83

SSC Eights!

Points: 848
More actions
November 21, 2016 at 10:48 am

#323115

Error: The client was unable to reuse a session with SPID 554, 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.
I have SQL 2014 SP1 clustered server, the sql log file is filling up with above messages for every 5 minutes, the next message everytime it writes is "Distributed transaction completed. Either enlist this session in a new transaction or the NULL transaction.".
I did gone through many forums and all they relate to upgrade/install SP CU on SQL 2008R2, but mine is SQL 2014 SP1. I don't see any spikes on resources, among 768GB RAM, we set max memory for SQL is 720GB.
When I browse sys.dm_os_ring_buffers, most of the records comes up with 'LoginTimers" as RecordType.
Any help would be appreciated.
Thanks
Vishwanath
November 23, 2016 at 9:22 pm

This was removed by the editor as SPAM

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

goher2000 SSCertifiable Points: 5479 More actions · Answer 1

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/f11537a5-8dc9-40a8-b2e4-17874685b074/sql-server-2008-r2-error-18056-severity-20-state29?forum=sqldatabaseengine

johnwalker10 SSCrazy Eights Points: 9124 More actions · Answer 2

Did you check out this link: https://blogs.msdn.microsoft.com/psssql/2010/08/03/how-it-works-error-18056-the-client-was-unable-to-reuse-a-session-with-spid-which-had-been-reset-for-connection-pooling/[/url]

kvishu83 SSC Eights! Points: 848 More actions · Answer 3

MAX DOP : 6

Cost Threshold for Parallelism: 15

select * from sys.dm_os_wait_stats where wait_type = 'threadpool';

wait_typewaiting_tasks_countwait_time_msmax_wait_time_mssignal_wait_time_ms

THREADPOOL303468614170

siavash.golchoobian Newbie Points: 1 More actions · Answer 4

This error maybe occurred because of "Common Criteria Compliance" feature was enabled on the server.

To resolve this error:

1-Disable "Common Criteria Compliance":

sp_configure 'show advanced options', 1;
GO
RECONFIGURE;
GO
sp_configure 'common criteria compliance enabled', 0;
GO
RECONFIGURE WITH OVERRIDE;
GO

2-Then Restart your machine