We recently set up a SQL Server 2012 Always On cluster.
Now we are receiving the following login error randomly throughout the day:
Login failed for user 'S-1-9-3-1964395612-1151207475-2536745398-1881170461.'. Reason: Could not find a login matching the name provided. [CLIENT: X.X.X.X]
I can't find any reason for this, in fact the same application that throws the error will usually load with just a refresh of the web page. This error is usually followed by:
The client was unable to reuse a session with SPID XXX, which had been reset for connection pooling. The failure ID is 5. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.
In the SQL Error logs I also see:
Error 18456, Severity 14, State 8
Error 18056, Severity 14, State 5
They seem to be related, but I can't pin down the exact cause for the error. All of the apps specify the database name in the connection string and have the correct username and password.
I did find something very similar to the problem we're seeing posted here:
According to this article it's a bug, but I haven't really been able to verify that. Plus if it was reported almost a year ago why wouldn't have already been fixed?
The error seems to occur at random and only when I am using the database user that has been "converted" to a contained user. I have other databases that are not part of the cluster and they seem to be 100% free of this error. In every case we've tracked so far the application throwing the error can be re-launched/refreshed and the error goes away.
Can anyone help me resolve this issue?
Thanks,
Eric