• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 340
  • Last Modified:

SQL 2008 express connection errors 10061 and 17

over the weekend one of the SQL database become inaccessible

when we try to connect to the SQL instance we get the errors  below

it comes up with SQL state 01000
SQL server 10061
on the tcpip interface

also SQL State error 08001
SQL server error 17

if we test the SQL instance on the SQL server were it resides it works fine .

help would be appreciated
0
Alan Duck
Asked:
Alan Duck
  • 5
  • 5
1 Solution
 
HugoHiaslCommented:
The first thing I would check is if the protocols are still enabled in the server configuration.

Use the Sql Server Configuration Manager in "Configuration Tools" on the server and see if TCP/IP is enabled in the menu "SQL Server network Configuration" for the given instance.
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Hi

You have a connection issue, please check,

In SQL server configuration manager->  Is TCP/IP enabled?
Next, does the firewall have an exception for port 1433 to allow inbound connections
Last, On the server, right click server in SQL (properties) and check if there is a checkbox at 'allow remote connections'
0
 
Alan DuckAuthor Commented:
Have check the above
TCP/IP is enabled
have installed portn 1433 in to the firewall
and have checked that allow remote conections is ticked
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
Patrick BogersDatacenter platform engineer LindowsCommented:
Next to TCP/IP is NamedPipes enabled and running?

What happens on the client if you run:      telnet serverip 1433
0
 
Alan DuckAuthor Commented:
Running the above telnet serverip 1433 failed to connect
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Then i assume you have some firewall or port issue somewhere.
I tested it against a running DB server and the screen went black (as expected)

Try to disable the firewall as a whole (and other firewalling software like Symantec Endpoint or MalwareButes)
If this doesnt resolve the issue i begin to think your SQL server is no longer listening to port 1433.
0
 
Alan DuckAuthor Commented:
the error says it cannot open connection to the sql ip address on port 1433 failed to connect
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
It should indicate

dbserver
0
 
Alan DuckAuthor Commented:
has the Firewall is controlled by the domain this may take a little time but we can try this
if you run connection tests on the SQL server to the SQL datadabe they do work fine which suggest that the SQL  is working
0
 
Patrick BogersDatacenter platform engineer LindowsCommented:
Yes, and not being able to telnet tells you port 1433 is not available or prohibited.
0
 
Alan DuckAuthor Commented:
I shall run tests on the ports
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now