- Remove From My Forums
-
Question
-
Hi
When I run a query like below against one remote SQL Server then it works fine and returns the required data;
SELECT * FROM [ODBC;Driver=SQL Server;SERVER=Server1.com;DATABASE=MyDatabase;UID=MyUser;PWD=MyPass].MyTable
However when I run the same query against a second remote SQL Server it gives me below 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 can otherwise access the second SQL Server fine. So it would seem there is something minor missing in the second server configuration that blocks running the query in this way. What is it I need to do on the problematic SQL Server to have me run the query
fine?Many Thanks
Regards
-
Edited by
Tuesday, February 7, 2012 4:34 AM
-
Edited by
Answers
-
«Invalid instance» seems to indicate you are trying use the default instance but you should specify a specific instance. For example not «Server=myMachine» but «Server=myMachineSQL2008». If you use SSMS to browse for servers, it will show all servers
and their instance names.
-Tom. Microsoft Access MVP
-
Marked as answer by
Y a h y a
Tuesday, February 7, 2012 7:10 PM
-
Marked as answer by
I have a Windows SBS 2003 Server, Service Pack 2, 2gb ram and 200gb disk.
I have installed MS SQL Server 2000 with its latest Service Pack 4 and left in tact its standard «MSSQL Desktop Engine (SBSMonitoriing)» and «MSSSQL Desktop Engine (Sharepoint)» installation that came with SBS 2003 Server install.
I have search the .experts-exchange and found a question («SQL Server Login error when attempting ODBC connection») my exact error message:
Connection failed:
SQLState: ‘01000’
SQL Server Error: 14
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Invalid Instance()).
Connection failed:
SQLState: ‘08001’
SQL Server Error: 14
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Invalid connection.
I have defined an Alias as it recommended but, still no conection.
I have created the ODBC from within the Server and works fine. I can connect to my SQL.
I’ve tried the following at the workstation:
1. Ping ServerName, tested ok
2. Ping server IP address, tested ok
3. In ODBC, in the «Create a New Data Source..», I place the server IP address, and still no connect
4. Tested command-line «Telnet ServerName 1433», and I get a blank screen,
where I type anything and is also blank (dont know what that means, but thats the result)
5. Verified that the server name and the machine name are the same; tested ok
6. Disable all firewall in the server and the workstation, still no connect
7. Disable all antivirus & antispyware, still no connect
8. Uninstalled SQL 2000, rebooted server, deleted all folders related to SQL2000 and reinstall
**************
Moved to MS SQL Server / Database Zones
250 points added
jason1178 Community Advisor
**************
I’m trying to connect my access front-end to the SQL Server backend.
It was working when SQL Server was on my computer but now i’m trying to connect to a server
So when I create the DSN file with access
- I chose SQL-Server driver ( I have also tried with SQL-Server native 10.0 )
- I enter the server name that I copied from SQL Management Studio so there’s no typo there
- I chose the NT authentication
Then I have this error
In the properties, I tried with TCP/IP with the default port 1433 and I also tried with the name pipes
I made sure that the checkbox to allow remote connection is checked
If I try to connect with management studio I got this error
I can see the server when I browse on the network
I’m trying this troubleshotting but i’m stuck with the telnet command. It says Could not open connection to host on 1433
I also tried with no port and i got the same error on port 23
Any ideas?
Thank you
asked Nov 21, 2012 at 20:24
MarcMarc
16.1k20 gold badges73 silver badges118 bronze badges
5
To create a new Data source to SQL Server, do the following steps:
-
In host computer/server go to Sql server management studio —> open Security Section on left hand —> right click on Login, select New Login and then create a new account for your database which you want to connect to.
-
Check the TCP/IP Protocol is Enable. go to All programs —> Microsoft SQL server 2008 —> Configuration Tools —> open Sql server configuration manager. On the left hand select client protocols (based on your operating system 32/64 bit). On the right hand, check TCP/IP Protocol be Enabled.
-
In Remote computer/server, open Data source administrator. Control panel —> Administrative tools —> Data sources (ODBC).
-
In User DSN or System DSN , click Add button and select Sql Server driver and then press Finish.
-
Enter Name.
-
Enter Server, note that: if you want to enter host computer address, you should enter that`s IP address without «\». eg. 192.168.1.5 and press Next.
-
Select With SQL Server authentication using a login ID and password entered by the user.
-
At the bellow enter your login ID and password which you created on first step. and then click Next.
-
If shown Database is your database, click Next and then Finish.
answered May 25, 2016 at 7:45
VahidVahid
912 silver badges3 bronze badges
- Windows firewall blocks the sql server. Even if you open the 1433 port from exceptions, in the client machine it sets the connection point to dynamic port. Add also the sql server to the exceptions.
«C:Program FilesMicrosoft SQL ServerMSSQL11.MSSQLSERVERMSSQLBinnSqlservr.exe»
More info
- This page helped me to solve the problem. Especially
or if you feel brave, locate the alias in the registry and delete it
there.HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSSQLServerClientConnectTo
answered Jul 8, 2017 at 8:05
HysenHysen
113 bronze badges
I had the same error which was coming and dont need to worry about this error, just restart the server and restart the SQL services. This issue comes when there is low disk space issue and system will go into hung state and then the sql services will stop automatically.
answered Jun 26, 2014 at 6:56
Received SQLSTATE 01000 in the following error message below:
SQL Agent — Jobs Failed: The SQL Agent Job «LiteSpeed Backup Full» has failed with the message «The job failed. The Job was invoked by User X. The last step to run was step 1 (Step1). NOTE: Failed to notify via email. — Executed as user: X. LiteSpeed(R) for SQL Server Version 6.5.0.1460 Copyright 2011 Quest Software, Inc. [SQLSTATE 01000] (Message 1) LiteSpeed for SQL Server could not open backup file: (N:BACKUP2filename.BAK). The previous system message is the reason for the failure. [SQLSTATE 42000] (Error 60405). The step failed.»
In my case this was related to permission on drive N following an SQL Server failover on an Active/Passive SQL cluster.
All SQL resources where failed over to the seconary resouce and back to the preferred node following maintenance. When the Quest LiteSpeed job then executed on the preferred node it was clear the previous permissions for SQL server user X had been lost on drive N and SQLSTATE 10100 was reported.
Simply added the permissions again to the backup destination drive and the issue was resolved.
Hope that helps someone.
Windows 2008 Enterprise
SQL Server 2008 Active/Passive cluster.
answered May 26, 2015 at 7:41
scott_lotusscott_lotus
3,15322 gold badges51 silver badges69 bronze badges
Cannot connect to the SQL database after rebuilding the Symantec Endpoint Protection Manager. SQLState: ‘01000’ and ‘08001’ are returned.
calendar_today
Updated On:
Products
Endpoint Protection
Issue/Introduction
You are unable to connect to the SQL database after rebuilding the Symantec Endpoint Protection Manager.
SQLState: ‘01000’ and ‘08001’ are returned when you test the connection from ODBC
As a result of not being able to connect to the database you will also get messages with the error «Unable to communicate with the reporting component» after logging in to the SEPM.
The following error message is returned when testing connection to the DB from ODBC.
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.
Cause
There are two possibilities:
- The instance name that is configured is not correct for the SEP Database
- The instance name is correct, but «Dynamically Determine port» option is checked
Resolution
To check the On the Symantec Endpoint Protection Manager, proceed to Start> Administrative Tools> Data Sources (ODBC).
- Proceed to the System DSN tab within the ODBC Data Source Administrator.
- Double-click on SymantecEndpointSecurityDSN.
- Confirm that the appropriate SQL Server (and instance) is specified in the Server box, and click on Next.
- Click on Client Configuration.
- Uncheck the Dynamically determine port box.
- Click on OK.
- Select the «Test Connection» button to confirm the configuration is correct.
- Restart the Symantec Endpoint Protection Manager.
Attachments
Feedback
thumb_up
Yes
thumb_down
No
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 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.012SQLEXPRESS 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 want. So I’m not sure what to do. I know the SQL Server exists, works, and an ODBC connection can be set up properly; I’m just not sure what it is I’ve got wrong in my connection settings that’s throwing these errors. Based on the latter error I listed, it would seem that it can connect to the server, but simply cannot find the instance (since I didn’t specify one that time). So does that mean I just need to use some different syntax to specify the IP along with an instance name? What do I do? Thanks in advance.