Error 10061 while connecting sql server 2008

Question

0.00/5 (No votes)

See more:

I am trying to connect sql server 2008 R2. But it gives

A network related or instance specific error has occurred while establishing a connection to the server. The server was not found or was inaccessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (Microsoft SQL Server, Error: 10061)

I enabled Client Protocols from Configuration Manager .Still Not Working. Please Help.
Thanks In Advance

Posted 27-Feb-14 19:59pm

pradnyaa

Updated 27-Feb-14 20:05pm

v2

Add a Solution

Comments

Vedat Ozan Oner 28-Feb-14 2:07am

have you tried connecting with ssms?

pradnyaa 28-Feb-14 2:33am

Yes but still the same

Tejas Vaishnav 28-Feb-14 2:08am

the error message it self shows that, your sqlserver is not available or inaccessible. so please check that, your sql server instance name is correct or not? if it is correct then check, sql browsing service is running or not and tcp/ip protocol is enable for sql browsing over network or not?

pradnyaa 28-Feb-14 2:21am

Sql Server Agent is not running rest all services are running.
But when I tried to start it gives an error that the request failed or service did not respond in timely fashion. WHat do I do now?

Bernhard Hiller 28-Feb-14 2:32am

Did you try to access it from the computer where the service is running, or from a different computer?

pradnyaa 28-Feb-14 2:34am

No its in the same computer

Vedat Ozan Oner 28-Feb-14 2:51am

are you sure about the instance name? for example, when I try to connect to default instance (localhost), I'm receiving the same error since there exists no default. But when I connect to the named instance (localhost\sqlexpress), it is ok. moreover, you can try 'Windows Authentication' instead of server authentication.

pradnyaa 28-Feb-14 4:23am

Not working .I even tried using the IP address but stil the same. Once the service is stopped it does not start.

Vedat Ozan Oner 28-Feb-14 5:03am

assuming that you are talking about 'SQL Server' service, it makes sense not to be able to connect it. see event viewer (eventvwr) logs, sql server logs (which can be found in service startup parameters) to understand what happens with the service. without finding the actual cause, you cannot start the service (or you must be lucky which contradicts with Murphy).

pradnyaa 28-Feb-14 6:06am

Failed to initialize SQLSQM timer. One of the following can be the source of the problem: registry doesn't contain all necessary information, server instance name can not be retrieved correctly, failure during timer creation, etc.

This is the error in event log file

Vedat Ozan Oner 28-Feb-14 6:17am

now, you can google it :)

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Maciej Los · Answer 1 · 2014-02-28T06:42:00

Sounds like windows firewall locks tcp/ip connection to the sql server: Configure the Windows Firewall to Allow SQL Server Access[^]

BTW, check these too:
How to: Enable the TCP/IP Protocol for a Database Instance[^]
Configure a Server to Listen on an Alternate Pipe (SQL Server Configuration Manager)[^]
Named Pipes vs. TCP/IP Sockets[^]