Odbc Error 08001 Native Error 17
Contents |
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 sqlstate 08001 sql server error 17 Us Learn more about Stack Overflow the company Business Learn more about hiring
Sql Server Error 10060
developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question
Sql Server Error 6
and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are
Sqlstate 08001 Sql Server Error 2
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 calling MYSERVER, running Microsoft SQL Server Express 2005. Right on this server itself, I've got an ODBC connection set up pointing connection failed sqlstate 01000 sql server error 53 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 Driver][DBNETLIB]SQL Server does not exist or access denied. If I try the same thing, but change the "server" from 123.456.789.012\SQLEXPRESS to just plain old 123.456.789.012, I get a different error: Connection failed: SQLState: '01000' SQL Server Error: 14 [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Invalid Instance())
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: SQL Server Error 53 and SQL Server Error 17 SQL Server > connection failed sqlstate 08001 Getting started with SQL Server Question 3 Sign in to vote SQL connection failed sqlstate 01000 sql server error 2 server 2000 with remote clients at 3 locations. Sites had been connected via leased line. We switched everything to odbc connection to sql server failed internet/VPN. Everything works, but a several times a day, the clients receive this error: Microsoft SQL Server LoginConnection failed:SQL State: '01000'SQL Server Error: 53[Microsoft][ODBC SQL Server Driver][DBNETLIB]Connection open(connect ( ) )Connection http://serverfault.com/questions/82007/how-do-i-get-this-sql-server-odbc-connection-working failed:SQL State: '08001'SQL Server Error: 17 If they exit and log back in, then it's OK. Here's what has changed: New ISP at HQ and remote sites with new static IPs. New firewalls/VPN setup. VPNs setup to alloow all traffic between sites. Internal IP addresses/computer names did not change. Only exception is the HQ gateway is different, but all network settings were updated https://social.technet.microsoft.com/Forums/en-US/27684811-1a59-4273-b7ed-3cc990b4f20a/sql-server-error-53-and-sql-server-error-17?forum=sqlgetstarted to reflect that. I have all of the remote firewalls pinging the HQ firewall every 30 seconds and have not seen any hint of a problem in the firewall logs. Seems to be isolated to SQL. None of the SQL server or client configs were touched. I know little about SQL. What do the errors above mean and does anyone have any ideas? THANKS!
Saturday, September 22, 2007 1:44 AM Reply | Quote Answers 7 Sign in to vote Hi All, This is the Solution on Following Error. Connection failedSQL State '01000'SQL Server error 53[microsoft][ODBC SQL Server Driver][DBNETLIB]Connection OpenConnection failedSQL State '08001SQL Error 17[microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. I have also faced this problem with MSSQL Server 2005 Express Edition then i check connectivity from ODBC i give the solution pls go step by step Start => Control Pane => Open Administrative Tools => Data Sources (ODBC) u get window with tabs Go Tab - User DSN => Click on ADD => opemed window => Create New Data Source => SQL Nativehere for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and http://stackoverflow.com/questions/13405208/diagnosing-connection-to-sql-server 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 6.2 million programmers, just like you, helping each other. Join them; it only takes sql server 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 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 sql server error 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 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.