Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3018
  • Last Modified:

SQL Server error 18056

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
tmalmond
Asked:
tmalmond
  • 2
  • 2
1 Solution
 
RaithZCommented:
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
 
tmalmondAuthor Commented:
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
 
RaithZCommented:
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
 
tmalmondAuthor Commented:
the authentication error was causing the issue.
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now