Solved

SQL Server error 18056

Posted on 2014-01-10
4
2,576 Views
Last Modified: 2014-01-18
I recently installed Mcafee EPO 5.0.1 on SQL server 2008r2 and get the following error:

The client was unable to reuse a session with SPID 59, which had been reset for connection pooling. The failure ID is 23. 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 no idea what is causing this. Seems to be  many blogs describing it, no specific answers. Other databases on the server seem to run fine. is just epo database that is effected.
0
Comment
Question by:tmalmond
  • 2
  • 2
4 Comments
 
LVL 6

Expert Comment

by:RaithZ
ID: 39771549
There isn't likely a specific answer since that is a generic error and it indicates that you should look earlier in the logs for the cause.  Are there any errors or failures before this message?
0
 

Author Comment

by:tmalmond
ID: 39771580
Not that I can see. Here are the log entries just prior to the error.

01/10/2014 08:28:18,Server,Unknown,The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/TCS-WS1.TCS.LOCAL:1433 ] for the SQL Server service.
01/10/2014 08:28:18,Server,Unknown,The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/TCS-WS1.TCS.LOCAL ] for the SQL Server service.
01/10/2014 08:28:17,spid6s,Unknown,SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
01/10/2014 08:28:17,spid6s,Unknown,SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
01/10/2014 08:28:17,spid59,Unknown,The client was unable to reuse a session with SPID 59<c/> which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
01/10/2014 08:28:17,spid59,Unknown,Error: 18056<c/> Severity: 20<c/> State: 23.
01/10/2014 08:28:17,Logon,Unknown,Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Access to server validation failed while revalidating the login on the connection. [CLIENT: <local machine>]
01/10/2014 08:28:17,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 23.
01/10/2014 08:28:17,spid11s,Unknown,Service Broker manager has shut down.
01/10/2014 08:28:17,spid72,Unknown,The client was unable to reuse a session with SPID 72<c/> which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
01/10/2014 08:28:17,spid72,Unknown,Error: 18056<c/> Severity: 20<c/> State: 23.
01/10/2014 08:28:17,spid55,Unknown,The client was unable to reuse a session with SPID 55<c/> which had been reset for connection pooling. The failure ID is 23. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
01/10/2014 08:28:17,spid55,Unknown,Error: 18056<c/> Severity: 20<c/> State: 23.
01/10/2014 08:28:17,Logon,Unknown,Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Access to server validation failed while revalidating the login on the connection. [CLIENT: <local machine>]
01/10/2014 08:28:17,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 23.
01/10/2014 08:28:17,Logon,Unknown,Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Access to server validation failed while revalidating the login on the connection. [CLIENT: <local machine>]
01/10/2014 08:28:17,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 23.
01/10/2014 08:28:15,spid51,Unknown,FILESTREAM: effective level = 0<c/> configured level = 0<c/> file system access share name = 'MSSQLSERVER'.
01/10/2014 08:28:15,spid51,Unknown,Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
01/10/2014 08:28:15,spid51,Unknown,FILESTREAM: effective level = 0<c/> configured level = 0<c/> file system access share name = 'MSSQLSERVER'.
01/10/2014 08:28:15,spid51,Unknown,Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install.
01/10/2014 08:28:15,spid51,Unknown,FILESTREAM: effective level = 0<c/> configured level = 0<c/> file system access share name = 'MSSQLSERVER'.
0
 
LVL 6

Accepted Solution

by:
RaithZ earned 500 total points
ID: 39771995
That looks like SQL server is being shut down and thats when this error is being generated.

Also at the same time there is an authentication failure for the System account ,which could also be the cause of the error.
0
 

Author Closing Comment

by:tmalmond
ID: 39791178
the authentication error was causing the issue.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Use this article to create a batch file to backup a Microsoft SQL Server database to a Windows folder.  The folder can be on the local hard drive or on a network share.  This batch file will query the SQL server to get the current date & time and wi…
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

679 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question