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:
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.
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.
The issue was first fixed in the following cumulative update of SQL Server.
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Microsoft SQL Server 2012 Developer, Microsoft SQL Server 2012 Enterprise, Microsoft SQL Server 2012 Express, Microsoft SQL Server 2012 Parallel Data Warehouse, Microsoft SQL Server 2012 Standard, Microsoft SQL Server 2014 Developer, Microsoft SQL Server 2014 Enterprise, Microsoft SQL Server 2014 Standard