Error 28000 Sql Server 2000
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: ODBC Error: SQLState 28000 & Server Error 18452 SQL Server sql server error 28000 login failed for user > SQL Server Data Access Question 0 Sign in to vote sqlstate 28000 sql server error 18456 We have an application that connects to SQL 2005 thru ODBC with the following string: driver=SQL Server;server=server1;database=db2005;uid=serveruser;pwd=pwd1; When sqlstate 28000 sql server error 18452 our administrators login on the workstation the application works well. But when ordinary users login they get the following error. (We only have 1 domain) SQLState: 28000 SQL Server Error: sql state 28000 sql server error 18456 18452 Login failed for user ". The user is not associated with a trusted SQL Server connection. Then the standard SQL Server Login window pops up asking for the Login ID and Password. On the window the 'Use Trusted Connection' is checked and the name of the user on the workstation appears on the LoginID. What we do is uncheck the
Connection Failed Sqlstate 28000 Sql Server Error 18456
'Use Trusted Connection' then login using the credentials above. Need help on this one please. Thanks. Monday, October 09, 2006 10:17 PM Reply | Quote Answers 0 Sign in to vote Try sp_adduser to make sure that the login is identified as trusted by SQL Server. Link for sp_adduser : http://msdn2.microsoft.com/en-us/library/ms181422.aspx Wednesday, October 11, 2006 2:19 AM Reply | Quote Moderator All replies 1 Sign in to vote Check whether server is configured to allow mixed authentication modes (SQL Server and Windows) (or) only Windows Authentication mode. You can do this by opening SQL Server Management Studio - Right Click on Server - Choose Properties - Security Proposed as answer by ca-bluebird Saturday, January 09, 2010 6:38 AM Tuesday, October 10, 2006 3:01 AM Reply | Quote Moderator 0 Sign in to vote Checked the setting, it is on SQL Server ad Windows auth mode. Tuesday, October 10, 2006 3:39 AM Reply | Quote 0 Sign in to vote Try sp_adduser to make sure that the login is identified as trusted by SQL Server. Link for sp_adduser : http://msdn2.microsoft.com/en-us/library
360 games PC games
Sql State 28000 Error 18456
Windows games Windows phone games Entertainment All Entertainment sql state 28000 error code 18456 Movies & TV Music Business & Education Business Students & educators sqlstate=28000 db2 Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet https://social.msdn.microsoft.com/Forums/sqlserver/en-US/36df4673-c3ec-4e30-bbdf-69a8690fd28b/odbc-error-sqlstate-28000-server-error-18452?forum=sqldataaccess Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/555332 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack http://dba.stackexchange.com/questions/29992/odbc-data-source-sql-server-connection-login-failed-for-user Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database http://stackoverflow.com/questions/8767290/sql-server-2000-odbc-not-associated-with-a-trusted-sql-server-connection professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer sql server The best answers are voted up and rise to the top ODBC Data Source SQL Server Connection - Login Failed For User up vote 11 down vote favorite 2 I have moved my database from an SQL 2005 to a server with SQL 2008. I am now trying to create an ODBC Data Source. I am using "With SQL Server authentication using a login ID and password entered by the user" and 28000 sql server have entered my Login and password. The Login is visible in SQL Server Management Studio under Security-> Logins. The login also contains the exact properties of the same login in my old server. When I hit next after entering the username and password I get: Connection failed: SQLState: '28000' SQL Server Error: 18456 [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'myUser'. After reading this: http://support.microsoft.com/kb/555332 I realized that the server properties were set to "Windows Authentication Mode" only, but even after changing to "SQL Server and Windows Authentication Mode" I am still having problems connecting. I can connect with my Windows account though. sql-server-2008 sql-server-2005 odbc logins share|improve this question edited Dec 7 '12 at 18:08 asked Dec 7 '12 at 16:11 jpsnow72 246139 Just a note. When you change the Server Authentication from Windows Authentication to Mixed Mode. You'll need to manually enable the SA login if you want it available. Personally I would keep it disabled in your case since you have access through your Windows acount. –Brandon leach Dec 7 '12 at 23:04 add a comment| 1 Answer 1 active oldest votes up vote 9 down vote accepted My answer... From my comments: The issue was that the server was set to "Windows Authentication Mode" only. To
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up SQL Server 2000 / ODBC - Not associated with a trusted SQL Server connection up vote 0 down vote favorite 1 I get this error: ERROR [28000] [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. Here's my code (C#), I'm running this on a local and on a remote machine: using (OdbcConnection connection = new OdbcConnection("dsn=mydsn")) { connection.ConnectionTimeout = 50000; OdbcCommand command = new OdbcCommand("select * from users", connection); command.CommandTimeout = 50000; connection.Open(); OdbcDataReader reader = command.ExecuteReader(); } DSN details: name: mydsn SQL login: mylogin database: Test SQL Server Configuration: security: sql server and windows authentication mode Whenever I try to use use the login to Management Studio, everything works fine, I can execute queries. sql-server-2000 odbc share|improve this question edited Jan 7 '12 at 8:42 marc_s 452k938641029 asked Jan 7 '12 at 4:11 dpp 8,2002065121 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote Check the SQL client network utility and list the possible client protocols. At least two should be enabled (by default): TCP/IP Named Pipes I got rid of this error as soon as I've put TCP/IP first, named pipes second after switching to Windows Authentication only. However, you may notice, that "trusted SQL Server Connection" usually refers to Windows Authentication only. If I were you, I would ch