Article ID: 2894326 - View products that this article applies to.
Consider the following scenario:
In this scenario, the application may be unable to connect to the database. Additionally, you find errors that resemble the following in the SQL Server error log:
Note This problem does not occur the first time that a connection to a contained database occurs. However, the problem does occur on all successive attempts.
datetime Logon Error: 18456, Severity: 14, State: 5.
datetime Logon Login failed for user 'SID'. Reason: Could not find a login matching the name provided [Client:]
datetime spid# Error: 18056, Severity: 20, State: 5.
datetime spid# The client was unable to reuse a session with SPID #, which had been reset for connection pooling. The failure ID is #. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
The issue was first fixed in the following cumulative update of SQL Server.
Cumulative Update 1 for SQL
|kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2894326|