Error 28000 Microsoft Odbc Sql Server
Contents |
360 games PC games error 28000 microsoft odbc sql server driver Windows games Windows phone games Entertainment All Entertainment error 28000 microsoft odbc sql server driver sql server login failed for user Movies & TV Music Business & Education Business Students & educators
Ms Sql Server Odbc
Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
Ms Sql Server Odbc Driver For Linux
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 ms sql server odbc connection string 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
Ms Sql Server 2005 Odbc Driver
Stack Overflow the company Business Learn more about hiring developers or posting ads with connection failed sqlstate 28000 sql server error 18456 us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for microsoft odbc driver 11 for sql server login failed for user database 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 https://support.microsoft.com/en-us/kb/963853 can answer 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 http://dba.stackexchange.com/questions/29992/odbc-data-source-sql-server-connection-login-failed-for-user the user" and 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 "Wind
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://stackoverflow.com/questions/1355203/dsn-tests-ok-but-login-failure-trying-to-use-the-dsn-to-sql-server-2005 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 DSN tests ok, but login failure trying to use the DSN to SQL Server 2005 up sql server vote 4 down vote favorite I'm writing a small ASP.NET application in a hosted environment (meaning I don't own the server). Using the hosting provider's webtools, I created a DSN that specifies the Driver, the Server, the UID, the PWD, and the Database. When I test the connection, it tests out fine. However, when I load my web page with the code: OdbcConnection DB = new OdbcConnection("DSN=MyDSNName"); DB.Open(); I get the ms sql server error: ERROR [28000] [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ''. I know I'm using the correct DSN name because when I change to "DSN=NonExistentDSN" I get a different error. I don't understand why the logon works when I test it but not when I use it in code. Since I don't own the server, some of the usual troubleshooting tools aren't available to me, but I'd appreciate any feedback the community has. asp.net sql-server odbc share|improve this question edited Aug 31 '09 at 11:49 Welbog 41.6k682102 asked Aug 30 '09 at 23:25 The Demigeek 2581821 add a comment| 1 Answer 1 active oldest votes up vote 4 down vote accepted Perhaps the DSN does not retain the password. Have you tried to supply login credentials? OdbcConnection DB = new OdbcConnection("DSN=MyDSNName;UID=login;PWD=password;"); DB.Open(); share|improve this answer answered Aug 30 '09 at 23:28 Yannick Motton 16.7k42946 1 Huh. That worked. Interesting. I wonder why. Of course, it totally defeats the purpose... the whole reason I chose to go with a DSN is so that I wouldn't have to code UID and PWD in the page code. Oh well, at least it's working now. –The Demigeek Aug 30 '09 at 23:55 add a comment| Your Answer draft saved draft discarded