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

    Întrebare

  • Hi All,

    I am getting fowling error on Windows 2008 R2 Server/SQL 2008 R2 Service Pack 1 (Build 7601). Server is production for last eight month never had any error. This first time we had error and all user went down until whole server rebooted. It didnt failed on Mirror server. Any resolution /help/ suggestion is appreciated.

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

    2012-04-20 06:20:08.42 spid235     The client was unable to reuse a session with SPID 235, 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.
    2012-04-20 06:20:08.42 spid231     Error: 18056, Severity: 20, State: 29.
    2012-04-20 06:20:08.42 spid231     The client was unable to reuse a session with SPID 231, 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.
    2012-04-20 06:20:13.88 spid140     Error: 18056, Severity: 20, State: 29.
    2012-04-20 06:20:13.88 spid140     The client was unable to reuse a session with SPID 140, 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.
    2012-04-20 06:20:47.41 spid175     Error: 18056, Severity: 20, State: 29.
    2012-04-20 06:20:47.41 spid175     The client was unable to reuse a session with SPID 175, 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.
    2012-04-20 06:20:49.68 spid93      Error: 18056, Severity: 20, State: 29.
    2012-04-20 06:20:49.68 spid93      The client was unable to reuse a session with SPID 93, 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.
    2012-04-20 06:21:31.87 Logon       Error: 18456, Severity: 14, State: 46.
    2012-04-20 06:21:31.87 Logon       Login failed for user 'sems'. Reason: Failed to open the database configured in the login object while revalidating the login on the connection. [CLIENT: 192.168.10.39]
    2012-04-20 06:21:31.87 spid140     Error: 18056, Severity: 20, State: 46.
    2012-04-20 06:21:31.87 spid140     The client was unable to reuse a session with SPID 140, 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.
    2012-04-20 06:23:18.83 Logon       Error: 18456, Severity: 14, State: 51.
    2012-04-20 06:23:18.83 Logon       Login failed for user 'sems'. Reason: Failed to send an environment change notification to a log shipping partner node while revalidating the login. [CLIENT: 192.168.10.38]
    2012-04-20 06:23:18.83 spid198     Error: 18056, Severity: 20, State: 51.
    2012-04-20 06:23:18.83 spid198     The client was unable to reuse a session with SPID 198, which had been reset for connection pooling. The failure ID is 51. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
    2012-04-20 06:23:53.32 Logon       Error: 18456, Severity: 14, State: 51.
    2012-04-20 06:23:53.32 Logon       Login failed for user 'sems'. Reason: Failed to send an environment change notification to a log shipping partner node while revalidating the login. [CLIENT: 192.168.10.38]
    2012-04-20 06:23:53.32 spid136     Error: 18056, Severity: 20, State: 51.
    2012-04-20 06:23:53.32 spid136     The client was unable to reuse a session with SPID 136, which had been reset for connection pooling. The failure ID is 51. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
    2012-04-20 06:24:19.48 Logon       Error: 18456, Severity: 14, State: 51.
    2012-04-20 06:24:19.48 Logon       Login failed for user 'sems'. Reason: Failed to send an environment change notification to a log shipping partner node while revalidating the login. [CLIENT: 192.168.10.39]
    2012-04-20 06:24:19.48 Logon       Error: 18456, Severity: 14, State: 51.

    Many Thanks

    Rupesh

    1 mai 2012 10:08

Toate mesajele