Microsoft Sql Server Error 17 Odbc State 08001
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 Us Learn more about Stack Overflow the company Business sql state 08001 sql server error 17 Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges connection failed sqlstate 01000 sql server error 10060 Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a connection failed sqlstate 01000 sql server error 53 minute: Sign up Here's how 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 sqlstate 08001 sql server error 2 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 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
Connection Failed Sqlstate 01000 Sql Server Error 2
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()). Connection failed: SQLState: '08001' SQL Server Error: 14 [Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid connection. Now I know what you're thinking. You might be thinking, "duh, you probably didn't open the firewall for port 1433, dummy." Except I did, and I verified this, as I can successfully run: telnet 123.456.789.012 1433 ...from the command line all I w
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a
Connection Failed Sqlstate 08001 Sql Server Error -1
Full Time Job Ways to Get Help Expand Search Submit Close Search Login sql server error 6 Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Unable sql state 01000 to Create ODBC Connection SQLState '08001' SQL Server 17 Want to Advertise Here? Solved Unable to Create ODBC Connection SQLState '08001' SQL Server 17 Posted on 2012-05-19 MS SQL Server 2008 1 http://serverfault.com/questions/82007/how-do-i-get-this-sql-server-odbc-connection-working Verified Solution 2 Comments 19,354 Views Last Modified: 2012-05-19 Thank you for looking at my question, Had a new server installed yesterday running MS SQL Server 2008 on SBS 2011. Databases have been restored successfully - can see tables, views etc. I tried to create on ODBC connection on the server and get: Connection Failed: SQLState: '01000' SQL Server Error: 2 [Microsoft][ODBC SQL Server Driver][DBNetLib]ConnectionOpen https://www.experts-exchange.com/questions/27723846/Unable-to-Create-ODBC-Connection-SQLState-'08001'-SQL-Server-17.html (Connect()) Connection Failed: SQLState: '08001' SQL Server Error: 17 [Microsoft][ODBC SQL Server Driver][DBNetLib]SQL Server does not exist or access denied I don't know where to start looking - please help 0 Question by:Crxfrd Facebook Twitter LinkedIn Google LVL 6 Best Solution byInderjeetjaggi Disable firewall From Start > All programs > Microsoft SQL server > Configuration Tools > SQL server Configuration manager Expand SQL server network Configuration > Select Protocol for (Ur SQL server) Go to Solution 2 Comments LVL 6 Overall: Level 6 MS SQL Server 2008 1 Message Accepted Solution by:Inderjeetjaggi2012-05-19 Disable firewall From Start > All programs > Microsoft SQL server > Configuration Tools > SQL server Configuration manager Expand SQL server network Configuration > Select Protocol for (Ur SQL server) Right hand pane Enable TCP\IP Restart SQL service and try 0 Message Author Closing Comment by:Crxfrd2012-05-19 Thank you Inderjeetjaggi, a real help - if I could award > 500 points I would 0 Write Comment First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. Comment Submit Your Comment By clicking you are agreeing to Experts E
the previous tutorial. After clicking Next on the SQL login information screen, ODBC manager will try to connect to http://dba.fyicenter.com/faq/sql_server_2/Getting_Connection_failed_Error_on_DSN_Creation.html the SQL Server with the login information you provided. After a period of waiting time, you may get error message box saying that: Connection failed: SQLState: '01000' SQL Server Error: 53 [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. See sql server the picture below: Three possible reasons for the failing: Wrong server name - You provided an incorrect server name. SQL Server not configured to take a network connection - You need to check the SQL Server configuration. Wrong login name or password - You provided incorrect login name or password. The first and third sql server error reasons are easy to validate and correct. The second reason requires further investigation. Continue with the next tutorial to configure your SQL Server to take a network connection. (Continued on next topic...) What Is Open Database Communication (ODBC)? How To Add a New DSN with the ODBC Driver for SQL Server? How To Define the Name and Server for a new DSN? How To Provide Login Information for a New ODBC DSN? Why Are You Getting Errors When Creating a New ODBC DSN? What Are the Requirements on SQL Server Network Connections? How To Start SQL Server Browser Service? How To Enable TCP/IP Protocol on a SQL Server? How To Verify the Port Number of the SQL Server? How To Configure ODBC DSN with Different Port Numbers? How To Configure and Test ODBC DSN Settings? How To Connect MS Access to SQL Servers through ODBC? How Can Windows Applications Connect to SQL Servers via ODBC?
Related Articles: More... Other Tutorials/FAQs: More... Related Resources: More... Selected Jobs: More...