SQL混合认证模式
所以我有一个混合身份验证模式的数据库。我有一个可以连接到它的软件。我从大约一月份开始就使用这个软件，没有出现任何问题。我向该数据库添加一个表。当我尝试通过查询访问此表时，我收到“登录失败”消息。登录来自不受信任的域 这很奇怪，因为我的连接字符串是 connectionString="Data Source=JOET-HP\SQLEXPRESS;Initial Catalog=AmazonProShip; User Id= Shipper; Password=Shipping1;< /代码> 有没有人遇到过这个并找到解决方案？
So I have a database with mixed authentication mode. I have a piece of software that connects to it. I was using this software since about January with no problems. I add a table to this database. When I try to access this table by a query I get Log In Failed. The log in is from an untrusted domain This is odd because my connection string is connectionString="Data Source=JOET-HP\SQLEXPRESS;Initial Catalog=AmazonProShip; User Id= Shipper; Password=Shipping1;
Has any encounter this and found a solution?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您最近是否应用了 SQL Server 更新（直接或通过 Windows 更新间接应用）？有一个已知问题，混合模式有时会更改为仅 Windows 身份验证。
如果您有 Management Studio（也许 Express 也有此功能），您可以通过右键单击对象资源管理器中的服务器名称，选择“属性”，移至“安全”来检查/更新它 - 这是第一个单选选项。
如果您没有 Management Studio，则需要为您的实例找到正确的 LoginMode 注册表子项（可能是 HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Microsoft SQL Server > MSSQL10.SQLEXPRESS > MSSQLServer）并将值更改为 2 （如果还不是 2，请先停止 SQL Server，更改该值，关闭注册表，然后重新启动 SQL Server）。
Did you recently apply SQL Server updates (directly, or indirectly through Windows update)? There is a known issue where mixed mode occasionally gets changed to Windows auth only.
If you have Management Studio (and maybe Express has this functionality as well), you can check / update it by right-clicking the server name in Object Explorer, selecting Properties, moving to Security - it's the first radio option.
If you don't have Management Studio, you need to find the right LoginMode registry subkey for your instance (probably HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Microsoft SQL Server > MSSQL10.SQLEXPRESS > MSSQLServer) and change the value to 2 (if it is not already 2, stop SQL Server first, change the value, close the registry, and restart SQL Server).