blocks|key|2932014|text|默认情况下，服务器设置为仅Windows身份验证。没有任何通知，错误的来源是，所以很难找出它。即使您创建了一个仅使用SQL身份验证用户，SQL+Management+studio也不会发出警报。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2932015|所以答案是：从Windows切换到SQL+Authentication|offset|length|style|BOLD|2932016|右键单击服务器名称并选择properties;|CODE|2932017|Select+security选项卡；启用|unordered-list-item|2932018|security|ordered-list-item|2932019|+SQL+|2932020|服务。|2932021|2932022|2932023|您现在可以使用您的登录名/密码进行连接。|2932024|以下是微软的指导：https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/change-server-authentication-mode?view=sql-server-ver15|2932025|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/change-server-authentication-mode?view=sql-server-ver15^0|0|6|T|0|C|A|0|7|8|0|0|8|0|0|0|0|0|0|9|3I|0|0^^$0|@$1|2|3|4|5|6|7|18|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|19|8|@$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1C|8|@$D|1D|E|1E|F|J]]|9|@]|A|$]]|$1|K|3|L|5|M|7|1F|8|@$D|1G|E|1H|F|J]]|9|@]|A|$]]|$1|N|3|O|5|P|7|1I|8|@$D|1J|E|1K|F|J]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1L|8|@]|9|@]|A|$]]|$1|S|3|T|5|P|7|1M|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|1N|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1P|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1Q|8|@]|9|@$D|1R|E|1S|1|1T]]|A|$]]|$1|10|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]]|11|$12|$5|13|14|15|A|$16|17]]]]

The server was set to Windows Authentication only by default. There isn't any notification, that the origin of the errors is that, so it's hard to figure it out. The SQL Management studio dont alert, even if you create a user with SQL Authentication only.
So the answer is: Switch from Windows to SQL Authentication:
<ol>
<li>Right click on the server name and select <code>properties</code>;</li>
<li>Select <code>security</code> tab;</li>
<li>Enable the <code>SQL Server and Windows Authentication mode</code>;</li>
<li>Restart the SQL Server service.</li>
</ol>
You can now connect with your login/password.
Here are the directions by Microsoft: <a href="https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/change-server-authentication-mode?view=sql-server-ver15" rel="noreferrer">https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/change-server-authentication-mode?view=sql-server-ver15</a>

blocks|key|2719489|text|要解决此问题，请使用Windows身份验证连接到SQL+Management+Studio，然后右键单击服务器节点“属性”->“安全性”，并启用SQL+server和Windows身份验证模式。如果您使用的是“sa”，请确保帐户已启用。为此，打开登录和查看状态下的'sa‘。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2719490|​|2719491|📷|atomic|offset|length|2719492|2719493|如果此操作不起作用，则可能需要重新安装SQL+Server|2719494|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/22bc060f8e22d2ea4730ff14f4240727.png|imageAlt^0|0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@$G|X|H|Y|1|Z]]|A|$]]|$1|I|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

To solve this, connect to SQL Management Studio using Windows Authentication, then right-click on server node Properties->Security and enable SQL Server and Windows Authentication mode. If you're using 'sa' make sure the account is enabled. To do this open 'sa' under Logins and view Status.

<img src="https://i.stack.imgur.com/ROfSH.png" alt="enable sa admin">

If this didn't work, you may need to reinstall SQL Server

blocks|key|145930|text|您还可以尝试转到服务并重新启动Sql+server实例。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|145931|📷|atomic|offset|length|145932|​|145933|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/cf46b68860018a08d0b304b3edae717c.png|imageAlt^0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@$E|T|F|U|1|V]]|A|$]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P|Q|-4]]]]

Also you can try to go to services and restart your Sql server instance<a href="https://i.stack.imgur.com/BvKPF.png" rel="noreferrer"><img src="https://i.stack.imgur.com/BvKPF.png" alt="enter image description here"></a>

blocks|key|143591|text|所以，我最近也有了这个，为了集成安全性，我的问题实际上很容易解决，但主要是因为我忘记了将"Trusted_Connection=True"添加到我的连接字符串中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|143592|我知道这可能看起来相当明显，但它让我花了大约20分钟，直到我意识到我从connectionstrings.com复制了我的连接字符串格式，连接字符串的一部分丢失了。|143593|很简单，我觉得有点愚蠢，但这就是我的答案。|143594|entityMap|0|LINK|mutability|MUTABLE|url|https://www.connectionstrings.com/sqlconnection/^0|18|P|0|Z|L|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|@]|D|@$9|V|A|W|1|X]]|E|$]]|$1|H|3|I|5|6|7|Y|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]]]

So, I had this recently also, for integrated security, It turns out that my issue was actually fairly simple to fix but mainly because I had forgotten to add "Trusted_Connection=True" to my connection string. 

I know that may seem fairly obvious but it had me going for 20 minutes or so until I realised that I had copied my connection string format from <a href="https://www.connectionstrings.com/sqlconnection/" rel="noreferrer">connectionstrings.com</a> and that portion of the connection string was missing.

Simple and I feel a bit daft, but it was the answer for me.

blocks|key|142262|text|此错误的另一个原因可能是数据库名称不正确或不存在。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|142263|强制TCP/IP连接(通过提供127.0.0.1而不是localhost或.)可以揭示错误的真正原因。在我的例子中，连接字符串中指定的数据库名称不正确。|offset|length|style|CODE|142264|所以，下面是清单：|142265|142266|确保在配置管理器中启用了命名管道(不要忘记重新启动服务器)。|unordered-list-item|BOLD|142267|确保您要连接的数据库存在。|142268|确保启用了SQL+身份验证(或混合模式)。|142269|142270|entityMap^0|0|F|9|R|9|11|1|0|0|0|C|4|0|0|5|4|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@$D|X|E|Y|F|G]|$D|Z|E|10|F|G]|$D|11|E|12|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|13|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|14|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|15|8|@$D|16|E|17|F|N]]|9|@]|A|$]]|$1|O|3|P|5|M|7|18|8|@]|9|@]|A|$]]|$1|Q|3|R|5|M|7|19|8|@$D|1A|E|1B|F|N]]|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|$]]

Another reason for this error could be incorrect or non-existent database name.

Forcing the TCP/IP connection (by providing <code>127.0.0.1</code> instead of <code>localhost</code> or <code>.</code>) can reveal the real reason for the error. In my case, the database name specified in connection string was incorrect.

So, here is the checklist:

<ul>
<li>Make sure Named Pipe is enabled in configuration manager (don't forget to restart the server).</li>
<li>Make sure the database you are connecting to exists.</li>
<li>Make sure SQL Server Authentication (or Mixed Mode) is enabled.</li>
</ul>

blocks|key|144620|text|请把这个也检查一下|type|unstyled|depth|inlineStyleRanges|entityRanges|data|144621|📷|atomic|offset|length|144622|还要签入配置TCP/IP，启用名称PipeLine和共享内存|144623|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/007d92c5b9ec0e1c14888206781fcec7.jpeg|imageAlt^0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@$E|T|F|U|1|V]]|A|$]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P|Q|-4]]]]

Please check this also <a href="https://i.stack.imgur.com/p9zBM.jpg" rel="noreferrer"><img src="https://i.stack.imgur.com/p9zBM.jpg" alt="enter image description here"></a> Also check in configuration TCP/IP,Names PipeLine and shared memory enabled

blocks|key|143569|text|如果尝试使用SQL凭据登录，还可以尝试在注册表中更改SQL+Server的LoginMode，以同时允许SQL+Server和Windows身份验证。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|143570|SQL+|143571|打开regedit|unordered-list-item|143572|
|143573|转到SQL实例键(根据实例名称的不同而有所不同)：Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft+SQL+Server\MSSQL14.SQLEXPRESS\MSSQLServer\|143574|143575|Set+LoginMode+to+2|143576|143577|​|143578|📷|atomic|offset|length|143579|143580|143581|重新启动SQL服务和SQL+Server+Management+Studio，然后重试。|ordered-list-item|143582|143583|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/eb3b7c50d45d2292574df8e1e83db597.png|imageAlt^0|0|0|0|0|0|0|0|0|0|0|1|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1C|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|1D|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|1E|8|@]|9|@]|A|$]]|$1|K|3|H|5|6|7|1F|8|@]|9|@]|A|$]]|$1|L|3|M|5|F|7|1G|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1I|8|@]|9|@]|A|$]]|$1|Q|3|R|5|S|7|1J|8|@]|9|@$T|1K|U|1L|1|1M]]|A|$]]|$1|V|3|P|5|6|7|1N|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|X|3|Y|5|Z|7|1P|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|11|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]]|12|$13|$5|14|15|16|A|$17|18|19|-4]]]]

If you are trying to login with SQL credentials, you can also try changing the LoginMode for SQL Server in the registry to allow both SQL Server and Windows Authentication.

<ol>
<li>Open regedit</li>
<li>Go to the SQL instance key (may vary depending on your instance name):
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQLServer\</li>
<li>Set LoginMode to 2</li>
</ol>

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

<ol start="4">
<li>Restart SQL service and SQL Server Management Studio and try again.</li>
</ol>

blocks|key|142367|text|我第二次面对这个问题，之前所有的回答都失败了，幸运的是，下面的请求完成了工作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|142368|Alter+login+[user]+with+CHECK_POLICY+=+OFF
go

Alter+login+[user]+with+CHECK_POLICY+=+ON
go|code-block|syntax|javascript|142369|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I face this issue for the second time and all previous answers failed, fortunately the following request do the job:

<pre><code>Alter login [user] with CHECK_POLICY = OFF
go

Alter login [user] with CHECK_POLICY = ON
go
</code></pre>

blocks|key|145946|text|对于我来说，我的登录用户的密码过期了，我得到了相同的异常。然后，我使用Windows身份验证模式登录，并更改关联用户的密码，这就解决了我的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|145947|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|$]]

For me the password expired for my login user, and i got the same exception.
Then i login with Windows Authentication mode and change the password for the associated user, and it solved my problem.

blocks|key|2719597|text|是的，这个错误可能是“一些失败的东西，祝你好运，弄清楚是什么”--在我的例子中，它是一个错误的用户名。SQL+Server+2019+RC1。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2719598|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|$]]

Yup, this error might as well be "something failed, good luck figuring out what" - In my case it was a wrong username. SQL Server 2019 RC1.

blocks|key|2932214|text|也有这个错误，原因很简单，但不明显:不正确的密码。不确定为什么我没有在新安装的SQL+2016服务器上看到“登录失败”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2932215|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|$]]

Had this error too, the cause was simple, but not obvious: incorrect password. Not sure why I didn't get just "Login failed" from freshly installed SQL 2016 server.

blocks|key|2932149|text|我也有同样的问题：“成功地与服务器建立了连接，但是在登录过程中发生了一个错误。(提供者:共享内存提供者，错误:0-管道的另一端没有进程。)”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2932150|我的连接是：|2932151|server=POS06\SQLEXPRESS；AttachDbFilename=C:...\Datas.mdf;Initial+Catalog=+Datas；User+ID=+sa；Pwd=12345；Connect+Timeout=10；|2932152|但我的SQL是POS06\MSQL2014|2932153|将连接字符串更改为|2932154|server=POS06\MSQL2014；AttachDbFilename=C:...\Datas.mdf;Initial+Catalog=+Datas；User+ID=+sa；Pwd=12345；Connect+Timeout=10；|2932155|啊，真灵。|2932156|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

I have the same proplem
"A connection was successfully established with the server, but then an error occurred
during the login process. (provider: Shared Memory Provider, error: 0 - No process is
on the other end of the pipe.)"

My connection is:

server=POS06\SQLEXPRESS; AttachDbFilename=C:...\Datas.mdf;Initial Catalog= Datas; User ID= sa; Pwd=12345; Connect Timeout=10; 

But My SQL is POS06\MSQL2014 

Change the connection string to 

server=POS06\MSQL2014 ; AttachDbFilename=C:...\Datas.mdf;Initial Catalog= Datas; User ID= sa; Pwd=12345; Connect Timeout=10; 

it worked.

blocks|key|142438|text|始终尝试使用这些凭据登录SQL+Management+Studio。这可能会揭示一些您在运行时无法在代码中获得的更多细节。我检查了SQL+%2B+Windows身份验证，重启了服务器，但仍然没有成功。在尝试使用SQL管理登录后，我得到以下提示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|142439|​|142440|📷|atomic|offset|length|142441|142442|不知怎么的，密码已经过期了，尽管登录是在几分钟前创建的。无论如何，新的密码设置，连接字符串更新，一切都很好。|142443|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/a4fce04de681027da133545ae06d6871.png|imageAlt^0|0|0|0|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@$G|X|H|Y|1|Z]]|A|$]]|$1|I|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S|T|-4]]]]

Always try to log in using those credentials with SQL Management Studio. This might reveal some more details that you don't get at runtime in your code.
I had checked the SQL + Windows authentication, restarted the server but still no luck.
After trying to log in using SQL Management, I got this prompt:
<a href="https://i.stack.imgur.com/KFmwG.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/KFmwG.png" alt="screenshot" /></a>
Somehow the password had expired although the login was created just minutes before. Anyway, new password set, connection string updated and all's fine.

blocks|key|2719567|text|确保您已在Security->+Logins中指定了用户，如果没有，请添加该用户，然后重试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2719568|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|$]]

make sure that you have specified user in Security-> Logins, if no - add it and try again.

blocks|key|145949|text|按照另一个答案进行操作，如果仍然不能正常工作，请重新启动计算机以有效地重新启动Windows上的SQL+Server服务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|145950|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|$]]

Follow the other answer, and if it's still not working, restart your computer to effectively restart the SQL Server service on Windows.

blocks|key|2932254|text|在我的例子中，数据库被恢复了，并且它已经有了用于连接的用户。我必须删除数据库中的用户，并为登录重新创建用户映射。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2932255|2932256|删除用户|ordered-list-item|2932257|2932258|DROP+USER+MyUser|2932259|如果用户拥有任何模式，则可能会失败。在删除用户之前，必须将这些has分配给dbo。使用下面的第一个查询获取用户拥有的模式，然后使用第二个查询更改这些模式的所有者(HangFire是从上一个查询获得的模式)。|2932260|select+*+from+information_schema.schemata+where+schema_owner+=+'MyUser'
ALTER+AUTHORIZATION+ON+SCHEMA::[HangFire]+TO+[dbo]+++++|code-block|syntax|javascript|2932261|用户的|2932262|更新用户映射。在management+studio中，转到安全->登录->打开user+->，转到user+mapping选项卡->，启用数据库并授予相应的角色。|2932263|2932264|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Y|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|12|8|@]|9|@]|A|$N|O]]|$1|P|3|Q|5|6|7|13|8|@]|9|@]|A|$]]|$1|R|3|S|5|E|7|14|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|V|$]]

In my case the database was restored and it already had the user used for the connection. I had to drop the user in the database and recreate the user-mapping for the login.
<ol>
<li>Drop the user
<pre><code>DROP USER [MyUser]
</code></pre>
</li>
</ol>
It might fail if the user owns any schemas. Those has to assigned to dbo before dropping the user. Get the schemas owned by the user using first query below and then alter the owner of those schemas using second query (HangFire is the schema obtained from previous query).
<pre><code>select * from information_schema.schemata where schema_owner = 'MyUser'
ALTER AUTHORIZATION ON SCHEMA::[HangFire] TO [dbo] 
</code></pre>
<ol start="2">
<li>Update user mapping for the user. In management studio go to Security-&gt; Login -&gt; Open the user -&gt; Go to user mapping tab -&gt; Enable the database and grant appropriate role.</li>
</ol>

blocks|key|2932269|text|在我的例子中:为用户分配一个sysadmin角色。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2932270|2932271|以windows身份验证的用户身份登录|ordered-list-item|2932272|转到:安全->登录->右键单击用户->将服务器角色分配为sysadmin|2932273|2932274|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|L|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|M|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|N|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|J|$]]

In my case: Assign a sysadmin role to the user.
<ol>
<li>Login as windows authenticated user</li>
<li>Go to: Security-&gt;Login-&gt;Right click user-&gt;Assign server role as sysadmin</li>
</ol>

blocks|key|2932298|text|在我的例子中，通过VPN远程登录工作得很好。但从安装了sql+server的服务器连接时失败。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2932299|事实证明，实例名不是默认的，例如。SQLEXPRESS。因此，它需要在连接时明确指定。|2932300|​|2932301|📷|atomic|offset|length|2932302|2932303|2932304|2932305|2932306|服务器名称：.例如。".\I01“|2932307|如果我是远程连接，我不需要这样做，只需使用、|2932308|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/c30b41051c13df2326e0c52ff3e9837f.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/e2d22ab9f7252c7d6633b78f11b5c0d6.png^0|0|0|0|0|1|0|0|0|0|0|1|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|14|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|15|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|16|8|@]|9|@$I|17|J|18|1|19]]|A|$]]|$1|K|3|E|5|6|7|1A|8|@]|9|@]|A|$]]|$1|L|3|E|5|6|7|1B|8|@]|9|@]|A|$]]|$1|M|3|G|5|H|7|1C|8|@]|9|@$I|1D|J|1E|1|1F]]|A|$]]|$1|N|3|E|5|6|7|1G|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1H|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1I|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|Z|10|-4]]|11|$5|V|W|X|A|$Y|12|10|-4]]]]

In my case, login works fine remotely, via VPN. But connecting from the server where sql server was installed, it failed.
Turns out, the instance name is not the default eg. SQLEXPRESS. Hence, it needs to be explictly specified when connecting.
<a href="https://i.stack.imgur.com/I7qk3.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/I7qk3.png" alt="enter image description here" /></a>
<a href="https://i.stack.imgur.com/XGwQn.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/XGwQn.png" alt="enter image description here" /></a>
Server name: .&lt;instance_name&gt;
eg. &quot;.\I01&quot;
I don't have to do this if I'm connecting remotely, just &lt;server_hostname&gt;,&lt;port_number&gt;

I've got this error:

<pre><code>A connection was successfully established with the server, but then an error occurred
during the login process. (provider: Shared Memory Provider, error: 0 - No process is
on the other end of the pipe.)

(Microsoft SQL Server, Error: 233)
</code></pre>

I know, there are similar questions on this site, and the answer is, to enable TCP/IP and pipes.
But I enabled both, and still doesn't work:

<img src="https://i.stack.imgur.com/vwXgL.png" alt="MSSQL error">

I am using Microsoft SQL Server 2012 and the user has full permissions.

No process is on the other end of the pipe (SQL Server 2012)

身份验证

SQL Server

数据库

服务器

Windows

我得到了这个错误：A connection was successfully established with the server, but then an error occurredduring the login process. (provider: Shared Memory Provider, error: 0 - No process ison the other end of t

问管道的另一端没有进程(SQL Server 2012)
EN

回答 18

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问管道的另一端没有进程(SQL Server 2012)EN

回答 18

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问管道的另一端没有进程(SQL Server 2012)
EN