Post reply

The client was unable to reuse a session with SPID XX, which had been reset for connection pooling. The failure ID is 46.

  • November 27, 2018 at 7:36 am

    #373164

    Receiving below error on SQL 2012 SP2 always on. 

    The client was unable to reuse a session with SPID XX, 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.
    Error: 18056, Severity: 20, State: 46.

    Login failed for user 'XXX'. Reason: Failed to open the database 'XXX' configured in the login object while revalidating the login on the connection. 
    Error: 18456, Severity: 14, State: 46.

    Prakash B

  • March 19, 2019 at 4:28 am

    #2024874

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

    Can someboady help on this

  • March 19, 2019 at 12:34 pm

    #2024931

    mahavirin - Tuesday, March 19, 2019 4:28 AM

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

    Can someboady help on this

    There isn't any one thing which addresses that error. It depends on other errors, if there are any. In some cases it can be ignored as explained in this article:
    Error 18056 can be unwanted noise in certain scenarios

    In other cases, you just have to do more digging, looking at sys.dm_os_ring_buffers. This article has more information -
    Breaking Down 18056

    Sue

Viewing 3 posts - 1 through 2 (of 2 total)

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