The user is not associated with a trusted SQL Server Connection
来源:互联网 发布:化学品msds制作软件 编辑:程序博客网 时间:2024/06/14 21:22
Source:http://decipherinfosys.wordpress.com/2008/11/14/the-user-is-not-associated-with-a-trusted-sql-server-connection/
support.microsoft.com/kb/889615
If you have worked with SQL Server for some time, you must have faced this error at some time or the other:
This error can come due to a couple of reasons. The most common reason is that the instance that you are trying to connect to has been set up as one with only Windows Only Authentication rather than Windows and SQL Server Authentication. You can check that easily by either by SSMS (SQL Server Management Studio) or in the registry settings as well (in case you do not have the client tools loaded up on the instance where you are getting this error and you inherited this set up from someone).
In SSMS, after you log in using your Windows Authentication, right click on the server and choose “Properties” and then go to the Security page and change the “Server Authentication” to be “SQL Server and Windows Authentication mode” as shown in the image below:
Once that is done, you will need to re-start the MSSQLServer service in order for the changes to take place.
The place where it gets stored in the registry is:
HKLM/Software/Microsoft/Microsoft SQL Server/MSSQL.2005/MSSQLServer
LoginMode - if it is 1, then it is Windows mode and if it is 2, it is mixed mode (Windows and SQL Server).
Now, other times you can also get this error with a blank user name i.e:
Login failed for user ”. The user is not associated with a trusted SQL Server connection
You can get that error in a couple of scenarios:
1) If the server name has a space after it’s name, example: in the connection string you have specified: servername ,1433 i.e. that extra space after the servername (the instance name).
2) Not being able to resolve the Windows account that is trying to connect to the SQL Server instance. Here are some scenarios that we have seen at client sites when this happens:
a) When using Windows authentication and the machine from where the connection is being made, instead of using a domain account, a local account on that machine is being used for making the connection to the SQL Server instance. This is obviously because the domain controller and SQL Server cannot recognize the local account on other machines.
b) In the case of web applications, the account that runs IIS does not have access to SQL Server. You have to impersonate a domain user account in ASP.Net for this. This KB article covers this in detail.
c) Another common reason is when communication is being made across domains which do not have a trust relationship set up between them.
d) We have also seen this in scenarios where because of heavy network load, communication between SQL Server and the Domain Controller is hindered.
- Login failed for user 'username'. The user is not associated with a trusted SQL Server connection
- java 连接 mssql2005 The user is not associated with a trusted SQL Server connection.
- The user is not associated with a trusted SQL Server Connection
- Trouble shooting:login failed for user 'sa' ,the user is not associated with a trusted SQL Server
- Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection. [SQLSTATE 28000] (Error 18452). The st
- Login failed for user 'Tester'. Reason: Not associated with a trusted SQL Server connection.
- Login failed for user ''.Reason:Not associated with a trusted SQL Server connection.
- Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
- "Not associated with a trusted SQL Server connection"解决方法
- Access Denied: Either the SOM service on the machine is not started or the user attempting this connection is not a member of th
- msxml6.dll (0x80072EFD) A connection with the server could not be established
- msxml3.dll 错误 '80072efd' A connection with the server could not be established
- msxml3.dll 错误 '80072efd' A connection with the server could not be established
- Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection
- 理解SQL Server 2000的信任连接(Trusted connection)
- svnsync: E230001: Server certificate verification failed issuer is not trusted
- Fixed -- Could not open a connection to SQL Server
- Could not open a connection to SQL Server [2]
- 水晶报表网络资源
- DedeCms关键词记录单,DedeCms长尾关键词记录单自动生成代码
- DedeCms关键词记录单,DedeCms长尾关键词记录单自动生成代码
- 人生之最心得
- 完全备份oracle数据库,再导出到另一服务器(linux下),bmc的数据系统
- The user is not associated with a trusted SQL Server Connection
- Acid3 及 Sunspider 测试
- Web开发必知的八种隔离级别
- 广告牌即时生成器
- oracle 增量备份恢复策略(基础知识)
- oracle 数据字典视图之 DICT / DICTIONARY
- browserrecon project
- mysql4升级到mysql5乱码问题解决方案
- Linux下启动Oracle服务和监听程序(基础知识)