|Message:||Login failed for user ‘%.*ls’. The login is a SQL Server login and cannot be used with Windows authentication.%.*ls|
The user attempted to login with credentials that cannot be validated. Possible causes are:
Similar problems can cause the less-specific error 18456.
If you are trying to connect using SQL Server Authentication, verify that SQL Server is configured in Mixed Authentication Mode.
If you are trying to connect using SQL Server Authentication, verify that the SQL Server login exists.
If you are trying to connect using Windows Authentication, verify that you are properly logged into the correct domain.
|Message:||Login failed for user ‘%ls’. Reason: Not associated with a trusted SQL Server connection.|
|If the user listed in the message is a SQL account name, this message generally indicates that this SQL Server instance is configured to only accept Windows-authenticated connections (Windows Authentication mode), but the connection attempt was made with a SQL Server-authenticated login.
If the user listed in the message is NULL, there was a problem with the Windows Authentication passed to SQL Server. The problem could be due to many factors, including incorrect name resolution, an out of sync domain controller, no available domain controllers, SSPI problems, or policies or permissions settings that prohibit connections.
If the error occurs when one computer is attempting to delegate Windows-authenticated permissions to another server, this error may indicate that the Windows delegation, often called a double-hop, is not properly configured within the domain. A common example of a double-hop is a linked server query where the client connects to an instance of SQL Server, and that instance tries to delegate the Windows permissions to an instance of SQL Server on another computer.
|If the user listed in the message is a SQL account name, you must either:
For more information about Windows Authentication, see Microsoft Knowledge Base article 269587.
If the user listed in the message is NULL:
For more information about cached credentials, see Microsoft Knowledge Base article 242536.
Additional information gathering steps that can help to narrow down the problem: