| title | MSSQLSERVER_18452 | Microsoft Docs | ||
|---|---|---|---|
| ms.custom | |||
| ms.date | 04/04/2017 | ||
| ms.prod | sql | ||
| ms.reviewer | |||
| ms.technology | supportability | ||
| ms.topic | language-reference | ||
| helpviewer_keywords |
|
||
| ms.assetid | 21da332c-e81d-4dee-a9d2-95598911b3be | ||
| author | MashaMSFT | ||
| ms.author | mathoma |
[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md]
| Product Name | SQL Server |
| Event ID | 18452 |
| Event Source | MSSQLSERVER |
| Component | SQLEngine |
| Symbolic Name | LOGON_INVALID_CONNECT |
| Message Text | 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:
-
The login may be a [!INCLUDEssNoVersion] login but the server only accepts Windows Authentication.
-
You are trying to connect using [!INCLUDEssNoVersion] Authentication but the login used does not exist on [!INCLUDEssNoVersion].
-
The login may use Windows Authentication but the login is an unrecognized Windows principal. An unrecognized Windows principal means that the login cannot be verified by Windows. This could be because the Windows login is from an untrusted domain.
Similar problems can cause the less-specific error 18456.
If you are trying to connect using [!INCLUDEssNoVersion] Authentication, verify that [!INCLUDEssNoVersion] is configured in Mixed Authentication Mode.
If you are trying to connect using [!INCLUDEssNoVersion] Authentication, verify that the [!INCLUDEssNoVersion] login exists.
If you are trying to connect using Windows Authentication, verify that you are properly logged into the correct domain.