Error 08001 Microsoft Odbc Sql Server Driver Dbnetlib Invalid Connection
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 error 01000 microsoft odbc sql server driver dbnetlib connectionopen (connect()) the company Business Learn more about hiring developers or posting ads with us Server microsoft odbc sql server driver dbnetlib connectionopen (invalid instance()) Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. microsoft sql server error 17 odbc state 08001 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 voted up and rise to the top How do I get
Sqlstate 08001 Sql Server Error 17
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 at itself, and that already works perfectly. I log in using SQL Server Authentication (not Windows authentication), odbc connection to sql server failed 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()). 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,
360 games PC games odbc connection failed sql server 2008 Windows games Windows phone games Entertainment All Entertainment
Connection Failed Sqlstate 01000 Sql Server Error 14
Movies & TV Music Business & Education Business Students & educators
Sql State 08001 Error 17
Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet http://serverfault.com/questions/82007/how-do-i-get-this-sql-server-odbc-connection-working 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/195566 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
sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that http://www.dbforums.com/showthread.php?1694901-ODBC-to-SQL-server you want to visit from the selection below. Results 1 to 12 of 12 https://support.symantec.com/en_US/article.TECH123551.html Thread: ODBC to SQL server Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 07-16-13,13:34 #1 Darkmatter5 View Profile View Forum Posts Registered User Join Date Aug 2012 Posts 12 Unanswered: ODBC to SQL server I am trying to setup an sql server ODBC data source for Access. The server I'm trying to connect to is 2008 R2. I have SQL Server Management Studio installed on the computer where I'm trying to make the ODBC Data Source from. I can connect the the remote 2008 server through Management Studio, but in the ODBC wizard I do the following: "Machine Data Source" tab, click "New" Select "User Data Source", click "Next >" Select "SQL Server", click "Next microsoft odbc sql >" Click "Finish" Name: remote Description: remote Server: type the server name ie "sql.somewhere.com" Select "With SQL Server authentication using a login ID and password entered by the user." Login ID: sa Password: my password Click "Next >" I get the following 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. I have looked all over the net trying to figure this out and I'm just lost. Any help is greatly appreciated! Reply With Quote 07-16-13,14:52 #2 MCrowley View Profile View Forum Posts Registered User Join Date Jan 2003 Location Massachusetts Posts 5,794 Provided Answers: 11 You may want to use a System ODBC, rather than a User ODBC. The difference is that the User ODBC is tied to one user account on the machine. For the server name in the ODBC settings, are you typing in the exact same server name as in SQL Management Studio? Is there a firewall on this machine? If so, is there an exception in the rules (inbound) for the SQL Server Management Studio program? If so, then it would be able to pass through the firewall, but ODBC would not. Reply With Quote 07-16-13,14:57 #3 Darkmatter5 View Profile View Foru
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' Cannot connect to the SQL database after rebuilding the Symantec Endpoint Protection Manager. SQLState: '01000' and '08001' are returned. TECH123551 January 11th, 2011 http://www.symantec.com/docs/TECH123551 Support / Cannot connect to the SQL database after rebuilding the Symantec Endpoint Protection Manager. SQLState: '01000' and '08001' are returned. Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Products Subscribe to this Article Manage your Subscriptions Search Again Situation You are unable to connect to the SQL database after rebuilding the Symantec Endpoint Pro