SQL Server 2008 错误 233
我正在使用以下 SQL 脚本在 SQL Server 2008 中创建新登录名：
CREATE LOGIN [xyz] WITH PASSWORD='xyz',
DEFAULT_DATABASE=[master], DEFAULT_LANGUAGE=[us_english],
CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF
它成功创建了新登录名。但是当我尝试使用 SQL Server Management Studio 登录时，它失败并显示：
已成功与服务器建立连接，但在登录过程中发生错误。 （提供程序：共享内存提供程序，错误：0 - 管道的另一端没有进程。）（Microsoft SQL Server，错误：233）
出了什么问题？我该如何解决这个问题？
I'm creating new login in SQL Server 2008 with following sql script:
CREATE LOGIN [xyz] WITH PASSWORD='xyz',
DEFAULT_DATABASE=[master], DEFAULT_LANGUAGE=[us_english],
CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF
It creates new login successfully. But when I try to login with it using SQL Server Management Studio it fails saying:
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)
What's wrong? How do I solve this issue?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（14）
这是我的做法，也许它也适合你。
使用 Windows 身份验证登录 Microsoft SQL Server 2012。
右键单击对象资源管理器中的服务器名称，然后单击“属性”
在新选项卡中单击“安全性”
选择“SQL Server 和 Windows 身份验证”
“确定”
关闭 SQL Server Management Studio。
start+run
写入services.msc
在那里搜索SQL并重新启动所有服务。
这对我有用。
Here is how I done it, maybe it works for you too.
login Microsoft SQL Server 2012 with windows authentication.
right-click onto the server name in Object Explorer and click Properties
In the new tab click Security
select SQL Server and Windows Authentication
Ok
Close the SQL server management studio.
start+run
write services.msc
search for SQL there and restart all services.
that works for me.
您也可能在未启用 SQL Server 身份验证的情况下尝试使用它。要解决此问题，请在 SQL Server Management Studio 中右键单击服务器实例上的“属性”，然后更新安全设置以包括“SQL Server 和 Windows 身份验证模式”。
It's also possible that you're trying to use SQL Server Authentication without having enabled it. To fix this, right-click Properties on your server instance in SQL Server Management Studio, and update the security settings to include "SQL Server and Windows Authentication mode".
看起来您正在尝试使用命名管道进行连接，但 SQL Server 没有侦听该协议。 请参阅 MSDN。
MSDN 建议的两个修复是：
服务器配置管理器
使用命名启用远程连接
管道。
客户端计算机上的管理员，移动
TCP 在命名管道之前
协议顺序列表。
Looks like you're trying to connect using named pipes, but SQL Server is not listening on that protocol. See MSDN.
The two fixes MSDN suggests are:
Server Configuration Manager to
enable remote connections using named
pipes.
Manager on the client computer, move
TCP before named pipes in the
protocol order list.
我有一个类似的问题：
1. 以主用户或 Windows 身份验证用户身份登录。
2.右键点击数据库-->属性-->安全-->
3. 单击单选按钮将 Windows 身份验证模式更改为“SQL Server 和 Windows 身份验证模式”。 （如果不是）
4.重启服务器
I had a similar issue:
1. log in as the master user or windows authenticated user.
2. right click on the database --> properties --> security -->
3. change Windows Authentication mode to "SQL server and windows authentication mode" by clicking on the radio button. (if it is not)
4. restart the server
当我第一次在本地计算机上安装 SQL Server 2014 时，我遇到了同样的问题。
就我而言，解决方案是设置正确的默认数据库。
I had the same issue when i first setup SQL Server 2014 on my local machine.
In my case the solution was to set a correct defualt database.
在 SQL Server 中以管理员身份登录
前往证券>>登录>> 转到属性
选择您的用户名并从状态>> 取消选中用户帐户锁定复选框
更改用户的密码
重新启动 sql server 并使用您的用户名登录。
Login with Administrator in SQL Server
Go to Securities >> Logins >> select your user name and go to properties
From Status >> uncheck user account lock check box
Change password for the user
Restart the sql server and login with your username.
我遇到了同样的错误。
我已按照下面提到的步骤解决了该错误：
我希望这会对某人有所帮助
I was facing the same error.
I've resolved the error by following below mentioned steps:
I hope this will help someone
这可能不是连接问题。检查您的默认数据库以及它是否在线。当默认数据库脱机或不存在时，更常见的情况是出现此问题。如果您的默认数据库不是 master ，最好选中此选项。
This is might not be a connection issue . Check your default database and if that is online . More commonly this issues seen when the default database will be offline or not exists . If your default database other than master ,better check this option.
我有办法解决这个问题。
bingo sql 验证实例打开.. :)
实际上，通过这种方式，我们欺骗了 sql 验证实例，因为它试图找到一个已经运行的实例.. 为我工作.. 祝你好运
I got a way to go around the problem.
bingo the sql authenticated instance open .. :)
Actually in this way we cheat the sql authenticated instance as it tries to find an already running instance.. worked fr me.. good luck
我尝试了大部分解决方案，但无法解决它，直到我发现 此 URL 表示执行以下操作：
打开 SQL Server Management Studio 并运行这些查询：
我们收到此错误的原因问题是用户连接数被重置为 1，因此只有一个用户能够连接到 SQL Server。
只是一个简单的查询就可以了。我希望这也对其他人有用。
I tried most of the solution but was not able to solve it until I found this URL which says to do the following:
Open SQL Server Management Studio and run the these queries:
The reason why we got this error is that the user connections was reset to 1, so only one user was able to connect with the SQL server.
just a simple query worked for. I hope this will work for others as well.
我没有使用脚本风格，但是通过GUI登录我遇到了相同的错误代码。我输入了错误的
用户名，这就是为什么我收到Sql Server，错误：233。为了解决此问题，您应该输入以下信息：
服务器名称：
MachineName\SQLEXPRESS身份验证：
SqlServer 身份验证用户名：
分配的用户名或简单的sa密码：
xyzpqr注意：这里我写的上述数据仅用于演示目的，实际数据是您的机器和数据。软件的属性。
I have not used the script style, but login through GUI I encountered the same error code. I had entered wrong
user nameand this is why I was getting theSql Server, Error: 233.In order to resolve this, you should input the following information:
Server Name:
MachineName\SQLEXPRESSAuthentication:
SqlServer AuthenticationUser Name:
Assigned user-nameor simplysaPassword:
xyzpqrNOTE: Here I have wrote above data for demo purpose only, actual data is your machine & software's properties.
根据： https://msdn.microsoft.com/en-us/library /bb326280.aspx
转到 -->远程设置
进入
“远程协助”中的“远程”选项卡，勾选“允许远程协助连接到这台计算机”，点击“高级”按钮并勾选“允许...< /strong>”，并在“邀请”中设置“30天”，
然后在“远程桌面”部分
勾选“允许远程连接到此计算机”
According to: https://msdn.microsoft.com/en-us/library/bb326280.aspx
Go to --> Remot setting
Go to "Remote" tab
in "Remote Assistance", Tick "Allow Remote Assistance connection to this computer", Click the "Advance" button and tick the "Allow..." and in the "Invitation" set the "30 days"
Then in the "Remote Desktop" part
Just tick "Allow remote connection to this computer"
按照此处的示例进行操作后仍然无法登录，我发现我的 sa 登录被禁用。以下内容让我进入：
After following the examples here and still not getting in, I found that my sa login was disabled. The following got me in:
“已成功与服务器建立连接，但登录过程中出现错误。”
当我在 Docker 中使用 sqllocaldb 时，我遇到了这个问题。问题是 Docker 映像没有分配足够的内存。增加内存实际上解决了问题。
"A connection was successfully established with the server, but then an error occurred during the login process."
I was getting this problem from sqllocaldb when used from within Docker. The problem was the Docker image was not allocated enough memory. Increasing the memory actually fixed the problem.