Odbc Connection Sql Server Error 6
Contents |
360 games PC games sqlstate 08001 sql server error 17 Windows games Windows phone games Entertainment All Entertainment connection failed sqlstate 01000 sql server error 10060 Movies & TV Music Business & Education Business Students & educators
Microsoft Sql Server Login Connection Failed Sqlstate 08001
Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet
Sql Server Error 11001
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 connection failed sqlstate 01000 sql server error 53 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
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the
Connection Failed Sqlstate 01000 Sql Server Error 2
workings and policies of this site About Us Learn more about Stack sqlstate 08001 sql server error 2 Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags odbc connection to sql server failed Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how https://support.microsoft.com/en-us/kb/195566 it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How do I get this SQL Server ODBC Connection working? up vote 25 down vote favorite 7 Note: I've obviously changed the server names and IPs to fictitious ones. Here's what's going on. I've got a server, which I'm http://serverfault.com/questions/82007/how-do-i-get-this-sql-server-odbc-connection-working calling MYSERVER, running Microsoft SQL Server Express 2005. Right on this server itself, I've got an ODBC connection set up pointing at itself, and that already works perfectly. I log in using SQL Server Authentication (not Windows authentication), and it's set up like this: Like I said, that one works. But next, I've got another computer which is on a totally different domain/not on the intranet, that needs to access this same SQL Server hosted on MYSERVER. Because it's on a different domain, it doesn't recognize the name "MYSERVER"; I have to point it at the IP address of MYSERVER, which we'll say is 123.456.789.012. But the ODBC connection doesn't seem to work there. I tried setting it up like this: This doesn't work. When I put in the username and password and press Next, it stalls for a good 10 to 20 seconds, and then finally comes back with the following error: Connection failed: SQLState: '01000' SQL Server Error: 1326 [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). Connection failed: SQLState: '08001' SQL Server Error: 17 [Microsoft][ODBC SQL Server Driv
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 http://stackoverflow.com/questions/13405208/diagnosing-connection-to-sql-server 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 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Diagnosing Connection to SQL Server up vote 1 down vote favorite 1 I'm trying to create an ODBC connection to SQL Server, but when i do, i get error: Connection failed: SQLState: '01000' SQL Server Error: 10060 [Microsoft][ODBC_SQL sql server Server Driver][TCP/IP Sockets] COnnectionOpen (Connect()). Connection failed: SQLState: '08001' SQL Server Error: 17 [Microsoft][ODBC_SQL Server Driver][TCP/IP Sockets] SQL Server does not exist or access denied. Here's what I've tried: not a firewall issue: tried with firewall on SQL Server turned off, and client turned off. Also able to telnet 1433 from client and that works fine. not an access issue: I can login from many different computers, including the SQL Server itself using the account i'm using on client (using SQL Server sql server error authentication) i can ping the hostname and IP address. (i've tried both) The only thing i can think of is that the client computer is windows server 2003, and has various roles setup: File Server Application Server Terminal Server Domain Controller DNS Server I don't know why these services are setup, but for the time being i can't shut them off. Would it be any of these, and if so, is there a way to disable any of the aspects of them, that might be blocking SQL. Any advise truly appreciated! sql-server connection odbc share|improve this question asked Nov 15 '12 at 20:00 russds 47211236 another thing: I'm able to create ODBC connections from other clients fine. It does appear that the problem lies with this particular client, either with the roles setup, or perhaps something else. Thanks! –russds Nov 15 '12 at 20:05 add a comment| 4 Answers 4 active oldest votes up vote 4 down vote accepted Found the issue. For some reason, even though SQL was not in use on the client, it was installed, and by going to All Programs -> Microsoft SQL Server -> Client Network Utility, i found that the protocal TCP/IP was using port 4717. I have no idea why that port was in use, and even further, i'm not sure why it would even matter - I was just setting up an odbc connection, and not using sql server (on the client) at all. E