Quantcast
Viewing all articles
Browse latest Browse all 15889

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

I've read so many threads about this error and tried many of things which none of them have resolved my issue.

Date5/29/2013 2:29:10 PM
LogSQL Server (Current - 5/29/2013 2:29:00 PM)

Sourcespid2228

Message
The client was unable to reuse a session with SPID 2228, 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.Sourcespid2228

Message
Error: 18056, Severity: 20, State: 46.

Error before the first one.

Date5/29/2013 2:29:10 PM
LogSQL Server (Current - 5/29/2013 2:29:00 PM)

SourceLogon

Message
Login failed for user 'sa'. Reason: Failed to open the database configured in the login object while revalidating the login on the connection. [CLIENT: 192.168.1.242]

When this error happens all users connected to the database get an error and are unable to log in for about 2-3 minutes. The error happens 1-2 times a day around the same time.

Below is the error generated from the the application being used to connect to SQL.

Error        : -2147467259  [DBNETLIB][ConnectionWrite (send()).]General network error. Check your network documentation.
Source       : Microsoft OLE DB Provider for SQL Server

This started happening once we got a new server and restored the database to it.

Windows Server 2008 R2 Enterprise - SP1

CPU E5-4640 @ 2.40Ghz x4

192 GB Ram

SQL Server 2008 R2 - Version: 10.50.4279.0

Things I have tried...

1. Setting "Max Degree of Parallelism" from 0 to 8

2. "Max server memory" to "184320"

3. Changed the power options from "Balanced" to "High Performance"

4. Installed the latest service packs for both windows and SQL.

I'm at a loss to what could be causing this issue. 



Viewing all articles
Browse latest Browse all 15889

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>