blocks|key|2975547|text|如果您尝试使用"SQL+Server身份验证“进行连接，则可能需要修改您的服务器身份验证：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2975548|在对象资源管理器中的Microsoft+SQL+Server+Management+Studio中：|2975549|+SQL右键单击服务器，然后单击“Properties|offset|length|style|CODE|2975550|Go+to+Security”页面，然后单击“|ordered-list-item|2975551|”下的“Server+authentication+choose+SQL+Server+and+Windows+Authentication+mode”单选按钮|2975552|单击“OK|2975553|Restart+SQL+Services”|2975554|2975555|entityMap^0|0|0|H|A|0|6|8|0|4|L|X|16|0|3|2|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@$F|Y|G|Z|H|I]]|9|@]|A|$]]|$1|J|3|K|5|L|7|10|8|@$F|11|G|12|H|I]]|9|@]|A|$]]|$1|M|3|N|5|L|7|13|8|@$F|14|G|15|H|I]|$F|16|G|17|H|I]]|9|@]|A|$]]|$1|O|3|P|5|L|7|18|8|@$F|19|G|1A|H|I]]|9|@]|A|$]]|$1|Q|3|R|5|L|7|1B|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|U|$]]

If you're trying to connect using "SQL Server Authentication" then you may want to modify your server authentication: 

Within the Microsoft SQL Server Management Studio in the object explorer:

<ol>
<li>Right click on the server and click <code>Properties</code></li>
<li>Go to the <code>Security</code> page</li>
<li>Under <code>Server authentication</code> choose the <code>SQL Server and Windows Authentication mode</code> radio button</li>
<li>Click <code>OK</code></li>
<li>Restart SQL Services</li>
</ol>

blocks|key|2762659|text|请查看这篇来自数据平台团队的博客文章。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2762660|http://blogs.msdn.com/b/sql_protocols/archive/2006/02/21/536201.aspx|offset|length|2762661|您确实需要查看错误消息的状态部分，以找到问题的根本原因。|2762662|2,+5+=+Invalid+userid
6+=+Attempt+to+use+a+Windows+login+name+with+SQL+Authentication
7+=+Login+disabled+and+password+mismatch
8+=+Password+mismatch
9+=+Invalid+password
11,+12+=+Valid+login+but+server+access+failure
13+=+SQL+Server+service+paused
18+=+Change+password+required|code-block|syntax|javascript|2762663|之后，谷歌如何解决这个问题。|2762664|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1W|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|11|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|12|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|C]]]]

Check out this blog article from the data platform team.

<a href="http://blogs.msdn.com/b/sql_protocols/archive/2006/02/21/536201.aspx">http://blogs.msdn.com/b/sql_protocols/archive/2006/02/21/536201.aspx</a>

You really need to look at the state part of the error message to find the root cause of the issue.

<pre><code>2, 5 = Invalid userid
6 = Attempt to use a Windows login name with SQL Authentication
7 = Login disabled and password mismatch
8 = Password mismatch
9 = Invalid password
11, 12 = Valid login but server access failure
13 = SQL Server service paused
18 = Change password required
</code></pre>

Afterwards, Google how to fix the issue.

blocks|key|164541|text|在打开之前，右击并选择“以管理员身份运行”。这为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|164542|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Before opening, right-click and choose 'Run as Administrator'. This solved the problem for me.

blocks|key|2762938|text|我曾经面对过这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2762939|请看附图，|2762940|步骤1:转到服务器属性|2762941|第2步:转到安全|2762942|步骤3:将服务器身份验证更改为SQL+server和WindowsAuthenication模式。|2762943|并重新启动您的Sql服务器。|2762944|​|2762945|📷|atomic|offset|length|2762946|2762947|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/1e01b806a52313d29d4d29910aa802eb.png|imageAlt^0|0|0|0|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|14|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|18|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|19|8|@]|9|@$Q|1A|R|1B|1|1C]]|A|$]]|$1|S|3|M|5|6|7|1D|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10|11|-4]]]]

I have faced this issue.

Please look at the attached image,

Step 1: Go to server property 

Step 2: Go to Security 

Step 3: Change server authentication as SQL server and WindowsAuthenication mode

and restart your Sql server.

<a href="https://i.stack.imgur.com/aG4Rl.png" rel="noreferrer"><img src="https://i.stack.imgur.com/aG4Rl.png" alt="enter image description here"></a>

blocks|key|2762795|text|如果"state“为"1”，请首先查看错误的详细信息。确保在SQL+server+/+Properties+/+Security下为SQL和Windows身份验证设置数据库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2762796|有关其他状态，请参阅上面的答案...|2762797|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

first see the details of the error 
if "state" is "1"
Ensure the database is set for both SQL and Windows authentication under SQL server / Properties / Security.

for other state see the above answers ....

blocks|key|164644|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|164645|检查您中是否启用了混合模式身份验证在server->security|ordered-list-item|164646|create中创建登录帐户在数据库|164647|中为该登录帐户创建用户，然后通过右键单击实例并选择restart|164648|来重新启动服务器|164649|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|L|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|M|7|@]|8|@]|9|$]]|$1|D|3|E|4|C|6|N|7|@]|8|@]|9|$]]|$1|F|3|G|4|C|6|O|7|@]|8|@]|9|$]]|$1|H|3|I|4|5|6|P|7|@]|8|@]|9|$]]|$1|J|3|-4|4|5|6|Q|7|@]|8|@]|9|$]]]|K|$]]

<ol>
<li>Check whether mixed mode authentication is enabled in you server->properties</li>
<li>Then create a login in the server->security</li>
<li>create an user for that login in your database</li>
<li>Then restart your server by right clicking the instance and select restart</li>
</ol>

blocks|key|164651|text|如果更改登录用户凭据或添加新的登录用户，则在需要登录后，必须重新启动SQL+Server服务。为此，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|164652|转到-->服务|164653|📷|atomic|offset|length|164654|​|164655|然后转到SQL+Server(MSSQLSERVER)并停止并重新启动|164656|现在试着登录，我希望你能。|164657|谢谢|164658|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/b9bf815bace8528ed479653f952c4a91.jpeg|imageAlt^0|0|0|0|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|11|8|@]|9|@$G|12|H|13|1|14]]|A|$]]|$1|I|3|J|5|6|7|15|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|16|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|17|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|18|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X|Y|-4]]]]

If you change a login user credential or add new login user then after you need to log in then you will have to restart the SQL Server Service. for that 

GO to--> Services
<a href="https://i.stack.imgur.com/hNXvJ.jpg" rel="noreferrer"><img src="https://i.stack.imgur.com/hNXvJ.jpg" alt="gray color row"></a>

Then go to SQL Server(MSSQLSERVER) and stop and start again

Now try to log in, I hope You can.

Thanks

blocks|key|2763189|text|只是发生在我身上，结果与这里列出的所有其他案例都不同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2763190|我碰巧在同一个集群中托管了两个虚拟服务器，每个服务器都有自己的IP地址。主机将其中一台服务器配置为SQL+Server，将另一台服务器配置为Web服务器。但是，SQL+Server已在这两个系统上安装并运行。主机忘记提到哪个是SQL，哪个是Web，所以我假设第一个是Web，第二个是SQL。|2763191|当我连接到(我认为是)+SQL+Server并尝试通过SSMS连接时，选择Windows身份验证，我得到了这个问题中提到的错误。我仔细检查了所有的设置，包括SQL+Server网络配置、MSSQLSERVER的协议：|2763192|2763193|blockquote|2763194|2763195|📷|atomic|offset|length|2763196|双击TCP/IP将显示以下内容：|2763197|2763198|2763199|2763200|2763201|IP地址是另一个虚拟服务器的IP地址！这最终让我意识到我只是在服务器之间搞混了，而且在第二台服务器上都工作得很好。|2763202|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/9a91841be1cdf94d9d42191011eab5e9.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/cde152555309b5ac644cb9f4a7d3add1.png^0|0|0|0|0|0|0|0|1|0|0|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|18|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|19|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|G|3|-4|5|H|7|1B|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1D|8|@]|9|@$M|1E|N|1F|1|1G]]|A|$]]|$1|O|3|P|5|6|7|1H|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|R|3|-4|5|H|7|1J|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]|$1|T|3|K|5|L|7|1L|8|@]|9|@$M|1M|N|1N|1|1O]]|A|$]]|$1|U|3|V|5|6|7|1P|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13|14|-4]]|15|$5|Z|10|11|A|$12|16|14|-4]]]]

Just happened to me, and turned out to be different than all other cases listed here.

I happen to have two virtual servers hosted in the same cluster, each with it own IP address. The host configured one of the servers to be the SQL Server, and the other to be the Web server. However, SQL Server is installed and running on both. The host forgot to mention which of the servers is the SQL and which is the Web, so I just assumed the first is Web, second is SQL.

When I connected to the (what I thought is) SQL Server and tried to connect via SSMS, choosing Windows Authentication, I got the error mentioned in this question. After pulling lots of hairs, I went over all the setting, including SQL Server Network Configuration, Protocols for MSSQLSERVER:

<blockquote>
 <a href="https://i.stack.imgur.com/z272N.png" rel="noreferrer"><img src="https://i.stack.imgur.com/z272N.png" alt="screenshot of TCP/IP configuration"></a>
</blockquote>

Double clicking the TCP/IP gave me this:

<blockquote>
 <a href="https://i.stack.imgur.com/QlEyL.png" rel="noreferrer"><img src="https://i.stack.imgur.com/QlEyL.png" alt="TCP/IP properties, showing wrong IP address"></a>
</blockquote>

The IP address was of the other virtual server! This finally made me realize I simply confused between the servers, and all worked well on the second server.

blocks|key|166756|text|右键单击用户，转到属性，将默认数据库更改为master这是图像的屏幕打印，其中显示了如果出现错误19456，则必须检查的内容。有时它缺省为用户没有权限的数据库|type|unstyled|depth|inlineStyleRanges|entityRanges|data|166757|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Right Click the User, go to properties, change the default database to master
This is the screen print of the image which shows what you have to check if you have the error 19456. Sometimes it default to a database which the user doesn't have permission

blocks|key|166776|text|18456错误状态列表|type|unstyled|depth|inlineStyleRanges|entityRanges|data|166777|错误状态错误描述|166778|SQL+server状态2和状态5无效的用户13+Authentication|166779|State状态6尝试使用禁用了password|unordered-list-item|166780|
|166781|State+failure|166782|166783|State+7登录且密码不匹配的|166784|166785|登录名|166786|166787|状态8密码不匹配|166788|166789|状态9无效的password|166790|166791|State+11和状态12有效登录，但服务器访问SQL+|166792|166793|服务已暂停|166794|
<代码>H115状态18更改所需密码<代码>H216F217|166795|潜在的原因下面是一个原因列表和一些简短的解释：|166796|未启用Windows身份验证：如果您是第一次在SQL+Server实例上使用SQL+Login，则通常会出现错误18456，因为服务器可能设置为(仅限)身份验证模式。|offset|length|style|BOLD|166797|如何修复？检查此SQL+Server+and+Windows+Authentication+Mode+page.|166798|无效的userID:+SQL+Server在您尝试获取的服务器上找不到指定的UserID。最常见的原因是此userID未被授予对服务器的访问权限，但这也可能是一个简单的拼写错误，或者您无意中试图连接到不同的服务器(如果您使用多个服务器，则通常如此)|166799|无效密码：密码错误或只是打字错误。请记住，此用户名在不同的服务器上可以有不同的密码。|166800|不太常见的错误：+userID可能在服务器上被禁用。为SQL身份验证提供了Windows登录(更改为Windows身份验证。如果您使用SSMS，则可能必须以不同的用户身份运行才能使用此选项)。密码可能已过期，可能还有其他几个原因…。如果你知道任何其他的，请告诉我。|166801|18456状态1解释：通常Microsoft+SQL+Server会给出错误状态1，这实际上并不意味着什么，除了你有18456错误。状态1用于隐藏实际状态，以保护系统，这对我来说是有意义的。下面是包含所有不同状态的列表，有关检索准确状态的更多信息，请访问Understanding+"login+failed"+(Error+18456)+error+messages+in+SQL+Server+2005|166802|希望这能有所帮助|166803|entityMap|0|LINK|mutability|MUTABLE|url|https://katieandemil.academy/error-18456-sql-server-and-windows-authentication-mode|1|http://blogs.msdn.com/b/sql_protocols/archive/2006/02/21/536201.aspx^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|24|7|0|0|1K|8|1C|0|0|0|3G|0|0|16|0|0|8|0|0|B|3J|24|1|0|0^^$0|@$1|2|3|4|5|6|7|20|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|21|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|22|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|23|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|24|8|@]|9|@]|A|$]]|$1|K|3|L|5|H|7|25|8|@]|9|@]|A|$]]|$1|M|3|J|5|6|7|26|8|@]|9|@]|A|$]]|$1|N|3|O|5|H|7|27|8|@]|9|@]|A|$]]|$1|P|3|J|5|6|7|28|8|@]|9|@]|A|$]]|$1|Q|3|R|5|H|7|29|8|@]|9|@]|A|$]]|$1|S|3|J|5|6|7|2A|8|@]|9|@]|A|$]]|$1|T|3|U|5|H|7|2B|8|@]|9|@]|A|$]]|$1|V|3|J|5|6|7|2C|8|@]|9|@]|A|$]]|$1|W|3|X|5|H|7|2D|8|@]|9|@]|A|$]]|$1|Y|3|J|5|6|7|2E|8|@]|9|@]|A|$]]|$1|Z|3|10|5|H|7|2F|8|@]|9|@]|A|$]]|$1|11|3|J|5|6|7|2G|8|@]|9|@]|A|$]]|$1|12|3|13|5|H|7|2H|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|2I|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|2J|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|2K|8|@$1A|2L|1B|2M|1C|1D]]|9|@]|A|$]]|$1|1E|3|1F|5|6|7|2N|8|@$1A|2O|1B|2P|1C|1D]]|9|@$1A|2Q|1B|2R|1|2S]]|A|$]]|$1|1G|3|1H|5|6|7|2T|8|@$1A|2U|1B|2V|1C|1D]]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|2W|8|@$1A|2X|1B|2Y|1C|1D]]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|2Z|8|@$1A|30|1B|31|1C|1D]]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|32|8|@$1A|33|1B|34|1C|1D]]|9|@$1A|35|1B|36|1|37]]|A|$]]|$1|1O|3|1P|5|6|7|38|8|@]|9|@]|A|$]]|$1|1Q|3|-4|5|6|7|39|8|@]|9|@]|A|$]]]|1R|$1S|$5|1T|1U|1V|A|$1W|1X]]|1Y|$5|1T|1U|1V|A|$1W|1Z]]]]

18456 Error State List

ERROR STATE ERROR DESCRIPTION

<ul>
<li>State 2 and State 5 Invalid userid</li>
<li>State 6 Attempt to use a Windows login name with SQL Authentication</li>
<li>State 7 Login disabled and password mismatch</li>
<li>State 8 Password mismatch</li>
<li>State 9 Invalid password</li>
<li>State 11 and State 12 Valid login but server access failure</li>
<li>State 13 SQL Server service paused</li>
<li>State 18 Change password required</li>
</ul>

Potential causes
Below is a list of reasons and some brief explanation what to do:

SQL Authentication not enabled: If you use SQL Login for the first time on SQL Server instance than very often error 18456 occurs because server might be set in Windows Authentication mode (only).

How to fix? Check this <a href="https://katieandemil.academy/error-18456-sql-server-and-windows-authentication-mode" rel="nofollow noreferrer">SQL Server and Windows Authentication Mode page.</a>

Invalid userID: SQL Server is not able to find the specified UserID on the server you are trying to get. The most common cause is that this userID hasn’t been granted access on the server but this could be also a simple typo or you accidentally are trying to connect to different server (Typical if you use more than one server)

Invalid password: Wrong password or just a typo. Remember that this username can have different passwords on different servers.

less common errors: The userID might be disabled on the server. Windows login was provided for SQL Authentication (change to Windows Authentication. If you use SSMS you might have to run as different user to use this option). Password might have expired and probably several other reasons…. If you know of any other ones let me know.

18456 state 1 explanations: Usually Microsoft SQL Server will give you error state 1 which actually does not mean anything apart from that you have 18456 error. State 1 is used to hide actual state in order to protect the system, which to me makes sense. Below is a list with all different states and for more information about retrieving accurate states visit <a href="http://blogs.msdn.com/b/sql_protocols/archive/2006/02/21/536201.aspx" rel="nofollow noreferrer">Understanding "login failed" (Error 18456) error messages in SQL Server 2005</a>

Hope that helps

blocks|key|168700|text|只是一次更新，如果其他任何人在正确配置的登录名中出现错误，以下是解决方案：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|168701|如果您尝试使用"SQL+Server身份验证“进行连接，则可能需要修改您的服务器身份验证：|168702|在对象资源管理器中的Microsoft+SQL+Server+Management+Studio中：|168703|右键单击服务器，然后单击属性|168704|转到安全页面|168705|在服务器身份验证下，选择SQL+Server和Windows身份验证模式单选按钮|168706|单击确定|168707|重新启动SQL服务|168708|entityMap^0|0|11|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Y|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|10|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|11|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|12|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|13|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|14|8|@]|D|@]|E|$]]|$1|T|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|U|$]]

Just an update, here is the solution if anyone else has there error with a properly configured login:
If you're trying to connect using &quot;SQL Server Authentication&quot; then you may want to modify your server authentication:
Within the Microsoft SQL Server Management Studio in the object explorer:
Right click on the server and click Properties
Go to the Security page
Under Server authentication choose the SQL Server and Windows Authentication mode radio button
Click OK
Restart SQL Services

blocks|key|2975863|text|首先转到开始栏，然后搜索本地服务，然后单击“查看本地服务”，然后它将打开服务窗口，然后转到SQL+Server(MSSQLSERVER)，右击它并单击停止，然后再次右击它并单击启动。现在您可以登录并将您的用户名设置为“sa”，密码为您赢得的密码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2975864|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

First go to start bar then search local services
Then click on "view local services" 
Then it will open service window then go to SQL Server(MSSQLSERVER) right click on it and click on stop and then again right click on it and click start. Now you can able to login and put your user name as 'sa' and password is your won password.

blocks|key|2763001|text|此外，您也可以使用windows身份验证登录，然后运行以下查询来启用它：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2763002|ALTER+LOGIN+sa+ENABLE+;++
GO++
ALTER+LOGIN+sa+WITH+PASSWORD+=+'<enterStrongPasswordHere>'+;++
GO|code-block|syntax|javascript|2763003|来源：https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/change-server-authentication-mode|offset|length|2763004|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/change-server-authentication-mode^0|0|0|3|2W|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

Also you can just login with windows authentication and run the following query to enable it:

<pre><code>ALTER LOGIN sa ENABLE ; 
GO 
ALTER LOGIN sa WITH PASSWORD = '&lt;enterStrongPasswordHere&gt;' ; 
GO
</code></pre>

Source: <a href="https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/change-server-authentication-mode" rel="nofollow noreferrer">https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/change-server-authentication-mode</a>

blocks|key|165759|text|请检查您是否已连接到网络这是否是域成员PC。此外，请确保您不是在双家庭PC上，因为您的路由可能会因网络度量而不正确。当我无法连接到域时，我遇到了这个问题。SQL+windows身份验证切换到本地PC帐户，但将其注册为SQL身份验证。一旦我禁用了无线适配器并重新启动，Windows集成就切换回域帐户并正常进行身份验证。我已经设置了混合模式，就像你已经做的一样，所以前面的帖子不适用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|165760|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Please check to see if you are connected to the network if this is a domain member PC. Also, make sure you are not on a dual home PC as your routes may be incorrect due to network metrics. I had this issue when I could not connect to the domain the SQL windows authentication switched to the local PC account but registered it as a SQL authentication. Once I disabled my wireless adapter and rebooted, the Windows integration switched back to the domain account and authenticated fine. I had already set up Mixed mode as you had already done as well so the previous posts do not apply.

blocks|key|166839|text|对我来说，这是错误的登录和密码。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|166840|entityMap^0|7|3|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

For me, it was wrong login and password.

blocks|key|168540|text|我相信，如果您尝试以Active+Directory中定义的用户身份登录，但试图在登录屏幕中使用"SQL+Server身份验证“，则可能会发生这种情况。我不知道如何使用NTLM/Windows身份验证指定不同的用户:当我单击Windows身份验证下拉菜单时，用户名和密码被清除，并且我只能以我自己的身份登录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|168541|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I believe this can happen if you are trying to log in with a user that is defined in Active Directory, but attempt using "SQL Server Authentication" in the login screen. I do not know how to specify a different user with NTLM/Windows Authentication: When I click the Windows Authentication dropdown, the username and password is blanked out, and I can only log in as myself.

blocks|key|168574|text|在我的案例中，多次错误的尝试锁定了我曾尝试运行以下查询的account.To+do，它起作用了:+ALTER+LOGIN+WITH+PASSWORD=+UNLOCK，并确保通过右键单击Sql+Server+->属性将特定用户的选项“强制密码安全”设置为取消选中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|168575|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case multiple wrong attempts locked the account.To do that I had tried running the below query and it worked:
ALTER LOGIN WITH PASSWORD= UNLOCK
And make sure to set the option "Enforce Password Security" option for specific user to be unchecked by right click on Sql Server -> Properties.

blocks|key|2763082|text|SQL+Server连接故障排除|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2763083|以防您无法使用SQL身份验证进行连接，并且您已经尝试了其他解决方案。|2763084|您可以尝试以下操作：|2763085|检查连通性|2763086|2763087|禁用防火墙。|unordered-list-item|2763088|在1434上运行PortQry并检查答案。|2763089|2763090|检查状态|2763091|2763092|尝试与SSMS或sqlcmd连接并检查消息。|2763093|状态1很少记录在案，但这只是意味着您无权了解真实状态。|2763094|查看SQL+server目录中的日志文件以了解状态。|2763095|2763096|国家5|2763097|这是什么？我的登录名不存在？它就在那里，我可以在SSMS中看到它。怎么会这样呢？|2763098|2763099|最有可能的解释是最有可能是正确的。|blockquote|2763100|2763101|2763102|登录的状态|2763103|2763104|Destroy，重新创建，启用。|2763105|重置密码。|2763106|2763107|或者..。|2763108|“你没有看对地方”或者“你看到的不是你想的那样”。|2763109|Local+DB和SQLEXPRESS冲突|2763110|如果您使用带有Windows身份验证的SSMS进行连接，并且您的实例名为SQLEXPRESS，那么您可能正在查看LocalDb，而不是正确的服务器。所以你刚刚在LocalDb上创建了你的登录。|offset|length|style|BOLD|2763111|当您使用SSMS通过SQL+Server身份验证进行连接时，它将尝试连接到SQLEXPRESS真实服务器，而您喜爱的登录还不存在。|2763112|附加说明：如果您没有忘记一些奇怪的连接字符串，请查看connection+parameters选项卡。|2763113|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|1K|7|0|0|0|5|0^^$0|@$1|2|3|4|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|20|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|21|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|22|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|23|8|@]|9|@]|A|$]]|$1|L|3|M|5|K|7|24|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|25|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|26|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|27|8|@]|9|@]|A|$]]|$1|R|3|S|5|K|7|28|8|@]|9|@]|A|$]]|$1|T|3|U|5|K|7|29|8|@]|9|@]|A|$]]|$1|V|3|W|5|K|7|2A|8|@]|9|@]|A|$]]|$1|X|3|-4|5|6|7|2B|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|2C|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|2D|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|2E|8|@]|9|@]|A|$]]|$1|13|3|14|5|15|7|2F|8|@]|9|@]|A|$]]|$1|16|3|-4|5|6|7|2G|8|@]|9|@]|A|$]]|$1|17|3|-4|5|6|7|2H|8|@]|9|@]|A|$]]|$1|18|3|19|5|6|7|2I|8|@]|9|@]|A|$]]|$1|1A|3|-4|5|6|7|2J|8|@]|9|@]|A|$]]|$1|1B|3|1C|5|K|7|2K|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|K|7|2L|8|@]|9|@]|A|$]]|$1|1F|3|-4|5|6|7|2M|8|@]|9|@]|A|$]]|$1|1G|3|1H|5|6|7|2N|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|2O|8|@]|9|@]|A|$]]|$1|1K|3|1L|5|6|7|2P|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|2Q|8|@$1O|2R|1P|2S|1Q|1R]]|9|@]|A|$]]|$1|1S|3|1T|5|6|7|2T|8|@]|9|@]|A|$]]|$1|1U|3|1V|5|6|7|2U|8|@$1O|2V|1P|2W|1Q|1R]]|9|@]|A|$]]|$1|1W|3|-4|5|6|7|2X|8|@]|9|@]|A|$]]]|1X|$]]

<h1>SQL Server connection troubleshoot</h1>

In case you are not able to connect with SQL Authentication and you've tried the other solutions. 

You may try the following:

<h2>Check connectivity</h2>

<ul>
<li>Disable Firewall.</li>
<li>Run PortQry on 1434 and check the answer.</li>
</ul>

<h2>Check the state</h2>

<ul>
<li>Try to connect with SSMS or sqlcmd and check the message.</li>
<li>State 1 is rarely documented but it just mean you don't have the right to know the true state.</li>
<li>Look at the log file in the directory of SQL server to know what is the state.</li>
</ul>

<h1>The State 5</h1>

What ? my login doesn't exist ? it's right there, I can see it in SSMS. How can it be ? 

<blockquote>
 The most likely explanation is the most likely to be the right one.
</blockquote>

<h2>The state of the login</h2>

<ul>
<li>Destroy, recreate it, enable it.</li>
<li>reset the password.</li>
</ul>

Or...

"You don't look at the right place" or "what you see is not what you think".

<h3>The Local DB and SQLEXPRESS conflict</h3>

If you connect with SSMS with Windows authentication, and your instance is named SQLEXPRESS, you are probably looking at the LocalDb and not the right server. So you just created your login on LocalDb.

When you connect through SQL Server authentication with SSMS, it will try to connect to SQLEXPRESS real server where your beloved login doesn't exist yet.

Additional note: Check in the connection parameters tab if you've not forgotten some strange connection string there.

blocks|key|2763128|text|另一个适用于我的解决方案。serever->security->logins->new+logins->General->创建您的用户名作为登录名，然后单击sql+server身份验证添加密码。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2763129|取消选中password+uncheck复选框。这将会起作用。|2763130|记住将服务器属性->Security从Server+authentication更改为SQL+Server+and+Windows+Authentication+mode|2763131|entityMap^0|D|1C|0|0|J|L|17|16|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|K|$]]

Another worked solution for me.
<code>serever-&gt;security-&gt;logins-&gt;new logins-&gt;General-&gt;</code>create your user name as login name,Click sql server authentication add passwords

uncheck the password verification three checkboxes .
This will work.

Remeber to change the server properties ->Security from <code>Server authentication</code> to <code>SQL Server and Windows Authentication mode</code>

blocks|key|165878|text|您可以在linux+for+mssql中更改sa帐户的密码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|165879|sudo+/opt/mssql/bin/mssql-conf设置|offset|length|style|BOLD|165880|The+license+terms+for+this+product+can+be+downloaded+from
+http://go.microsoft.com/fwlink/?LinkId=746388+Jump+Jump
and+found+in+/usr/share/doc/mssql-server/LICENSE.TXT.
Do+you+accept+the+license+terms?+[Yes/No]:yes
++Setting+up+Microsoft+SQL+Server
Enter+the+new+SQL+Server+system+administrator+password:++--Enter+strong+password
Confirm+the+new+SQL+Server+system+administrator+password:+--Enter+strong+password
+starting+Microsoft+SQL+Server...
+Enabling+Microsoft+SQL+Server+to+run+at+boot...
Setup+completed+successfully.|code-block|syntax|javascript|165881|entityMap^0|0|0|W|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|S|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

you can do in linux for mssql
 change password for sa account

sudo /opt/mssql/bin/mssql-conf setup

<pre><code>The license terms for this product can be downloaded from
 http://go.microsoft.com/fwlink/?LinkId=746388 Jump Jump
and found in /usr/share/doc/mssql-server/LICENSE.TXT.
Do you accept the license terms? [Yes/No]:yes
 Setting up Microsoft SQL Server
Enter the new SQL Server system administrator password: --Enter strong password
Confirm the new SQL Server system administrator password: --Enter strong password
 starting Microsoft SQL Server...
 Enabling Microsoft SQL Server to run at boot...
Setup completed successfully.
</code></pre>

blocks|key|2763236|text|在我的SQL实例下创建一个新的sysadmin用户后，我得到了这个错误。我的管理员用户是在特定的域MyOrganization/useradmin下创建的|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2763237|在断开连接的环境中使用useradmin允许您使用SQL+Server身份验证创建其他用户，但只要您尝试登录，就会得到|2763238|2763239|+Microsoft+SQL+Server错误:+18456|blockquote|2763240|2763241|2763242|若要解决此问题，请尝试再次连接到您的组织网络，并在您连接时创建用户，然后您可以断开连接并正常工作。|2763243|entityMap^0|1D|O|0|B|9|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|X|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|Y|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|10|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|11|8|@]|D|@]|E|$]]|$1|P|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|Q|$]]

I got this error after creating a new sysadmin user under my SQL instance. 
My admin user was created under a specific domain
MyOrganization/useradmin

Using useradmin on a disconnected environment allows you to create other users using SQL Server authentication, but as soon as you try to login you get

<blockquote>
 Microsoft SQL Server Error: 18456
</blockquote>

To fix the problem, try to connect again to your Organization network and create the user while you are connected and then you can get disconnected and will work.

blocks|key|165909|text|我也遇到过同样的问题。如果您看到它，请运行以下查询：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|165910|DBCC+FREEPROCCACHE

DBCC+DROPCLEANBUFFERS|code-block|syntax|javascript|165911|然后显示18456错误代码。|165912|重新连接SQL+server后再次运行相同的查询。它会工作得很好。|165913|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I have faced the same issue. In case you see it, run this query:
<pre class="lang-sql prettyprint-override"><code>DBCC FREEPROCCACHE

DBCC DROPCLEANBUFFERS
</code></pre>
then it shows a 18456 error code.
Do one thing again run same query after reconnecting SQL server. It will work fine.

blocks|key|2976184|text|单击“选项”，然后在“连接属性”下，在“连接到数据库：”旁边指定目录/数据库名称。我得到了这个错误，因为它被设置为，并且我需要指定dbname。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2976185|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Click on &quot;Options&quot; and under &quot;Connection Properties&quot; specify the catalog/database name next to &quot;Connect to database:&quot;. I got the error because this was set to &lt;default&gt; and I needed to specify the dbname.

I am getting this error while trying to connect to the SQL Server.

<blockquote>
 Microsoft SQL Server Error: 18456
</blockquote>

Can anybody tell me what the error code means?

Login to Microsoft SQL Server Error: 18456

虚拟服务器

身份验证

日志文件

SQL Server

数据库

服务器

防火墙

Windows

路由

我在尝试连接到SQL Server时遇到此错误。 Microsoft SQL Server错误: 18456谁能告诉我错误代码是什么意思？

问登录到Microsoft SQL Server错误: 18456
EN

回答 23

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问登录到Microsoft SQL Server错误: 18456EN

回答 23

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问登录到Microsoft SQL Server错误: 18456
EN