November 30, 2015 at 8:26 am
Trying to run a BCP command and get the following error:
Error = [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [53].
SQLState = 08001, NativeError = 53
Error = [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connecti
ons.
SQLState = S1T00, NativeError = 0
Error = [Microsoft][SQL Native Client]Login timeout expired
NULL
I have gone through all the possible solutions on Google/ forums but cannot get this fixed. So far I have:
Ticked 'Allow remote connections' to this server
Enabled TCP/IP
Set IP2 to internal IP address of server
IPAll - cleared entry in TCP dynamic ports and put in 1433 into TCP Port
Enabled access to port within Windows Firewall even though the firewall is OFF
cannot think of anything else to try - any help would be really appreciated
November 30, 2015 at 10:02 am
November 30, 2015 at 10:20 am
andyc209 (11/30/2015)
Trying to run a BCP command and get the following error:Error = [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [53].
SQLState = 08001, NativeError = 53
Error = [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connecti
ons.
SQLState = S1T00, NativeError = 0
Error = [Microsoft][SQL Native Client]Login timeout expired
NULL
I have gone through all the possible solutions on Google/ forums but cannot get this fixed. So far I have:
Are you connecting to a named instance?
Are you running the query remotely?
This message usually appears when the instance you're trying to connect doesn't exist or is unreachable.
andyc209 (11/30/2015)
Ticked 'Allow remote connections' to this serverEnabled TCP/IP
Set IP2 to internal IP address of server
These are set dynamically, based on the TCP adapters on the server, don't touch them
andyc209 (11/30/2015)
IPAll - cleared entry in TCP dynamic ports and put in 1433 into TCP PortEnabled access to port within Windows Firewall even though the firewall is OFF
cannot think of anything else to try - any help would be really appreciated
Supply more detail about the connection you're using and don't believe everything you read on google
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
November 30, 2015 at 11:03 am
Thanks for the input - I am running this on a local machine - no accessing remote machines. I have installed an instance on a widows server 2008 machine and am running this command on the same box
November 30, 2015 at 10:42 pm
Verify that, the IP Address is set to the computer's IP address on the local subnet and make sure that TCP Dynamic Ports is blank
December 1, 2015 at 12:32 am
All done - IP address is he same and the ports bit is blank - really stuck on this one
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply