Post reply

Error: Failed to open the database configured in the login object while revalidating the login on the connection

  • July 24, 2015 at 2:28 am

    #319957

    Hi All

    We've recently migrated some of our SQL Server 2005 databases to a new SQL Server 2008 R2 server. We're leaving the databases in compatibility mode 90 for now.

    However, we're receiving the following errors in the SQL logs every 5 minutes or so:

    Error: 18456, Severity: 14, State: 46.

    Login failed for user 'dbuser'. Reason: Failed to open the database configured in the login object while revalidating the login on the connection. [CLIENT: <client-ip>]

    , immediately followed by:

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

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

    We do see many successful logins by dbuser, but we're a bit concerned by the frequency of these errors.

    The dbuser login has the correct default database set in SQL Server and the connection strings in use (the ones that we know of, at least) in the application do not specify a default database.

    Having done some research, it seems like this may have been an issue in SQL 2005, but was resolved with a hotfix.

    Has anyone had an experience with this error?

    Thanks,

    Innerise

  • July 27, 2015 at 5:35 am

    #1815087

    For anyone else who experiences this specific error (Error: 18056, Severity: 20, State: 46), I managed to find the cause after lots of reading...

    There was a rogue entry in the application's connection string, which had made it's way there in error during the last deployment. This rogue entry was referencing a non-existent database in the 'Initial Catalog' value.

    Once we removed that entry from the connect string, the errors stopped.

    Ta,

    Innerise

  • November 27, 2018 at 7:47 am

    #2014652

    Receiving the same error. Double checked the web config file. There is no rogue entry.

    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

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

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