Permalink
Cannot retrieve contributors at this time
| title | description | ms.service | ms.reviewer | ms.subservice | ms.topic | f1_keywords | helpviewer_keywords | author | ms.author | ms.custom | ms.date |
|---|---|---|---|---|---|---|---|---|---|---|---|
|
MSSQLSERVER_10061 |
The server did not respond to the client request in SQL Server. See an explanation of the error and possible resolutions. |
sql |
supportability |
reference |
10061 |
10061 (Database Engine error) |
MashaMSFT |
mathoma |
04/04/2017 |
MSSQLSERVER_10061
[!INCLUDE SQL Server Azure SQL Database Azure SQL Managed Instance]
Details
| Attribute | Value |
|---|---|
| Product Name | SQL Server |
| Event ID | 10061 |
| Event Source | MSSQLSERVER |
| Component | SQLEngine |
| Symbolic Name | |
| Message Text | An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not 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) |
Explanation
The server did not respond to the client request. This error could occur because the server is not started.
User Action
Make sure that the server is started.
See Also
Manage the Database Engine Services
Configure Client Protocols
Network Protocols and Network Libraries
Client Network Configuration
Configure Client Protocols
Enable or Disable a Server Network Protocol
- Remove From My Forums
-
Question
-
TITLE: Connect to Server
——————————Cannot connect to RPSINGH-HPRP.
——————————
ADDITIONAL INFORMATION:A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. 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)——————————
Answers
-
This Error may occur due to many reasons like:<o:p></o:p>
1- The SQL instance you are trying to connect it stopped, then you need to check the service is up and running<o:p></o:p>
2- There is a network problem between your SQL client (e.g.: SQL Server Management Studio or SQL Server Business Intelligence Studio)
and the target SQL instance, then you may need to contact your network admin to check.<o:p></o:p>3- The Server performance and the memory status in order to accept extra connections as Mr. Alex had mentioned below, then you have to check the
Windows performance counter Memory: Pagessec in order to know whether there is a memory bottleneck or not, in the normal case you will find that the value for this counter between 0 and 10<o:p></o:p>Waiting for your outcome :)<o:p></o:p>
-
Marked as answer by
Monday, February 27, 2012 2:30 AM
-
Marked as answer by
UPDATE:
I took the laptop to work and one of the networking guys got it working.
———————————————————————————————————————
I usually use my PC to connect to my schools (Capella University online) SQL database to do my web app assignments. I will be on vacation for a couple of weeks and am loading everything onto my laptop so I can stay on target with class.
I keep getting the same error:
TITLE: Connect to Server
——————————
Cannot connect to vle3.capella.edu,2541
——————————
ADDITIONAL INFORMATION:
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 connections. (provider: TCP Provider, error: 0 — No connection could be made because the target machine actively refused it.) (Microsoft SQL Server, Error: 10061)
I have went to the forum in the link specified and done all the steps to add the sqlser and sqlbrowser exceptions to the firewall, tried the telnet which does not work, made sure the remote settings in the surface configuration manager were on both TCP and pipes are on. I have this set the same way on my PC and I connect fine is there something special I need to do on my laptop. I thought it was because I was doing it based on a wifi connection but I put the DSL on it and I get the same errors.
Thanks in advance for yoru assistance.
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
15.9k20 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,13521 gold badges49 silver badges69 bronze badges
- Remove From My Forums
-
Question
-
I am stuck with some error in MS SQL 2005. I am not able to access it. It is giving me network related error 10061. I have tried to enable TCP protocol under that instance. But it is giving me error. it is not starting. I also check the SQL
Server Surface Area Configuration>select that instance> Database Engine > Remote Connections. under that try to select last radio
butten i.e both TCP and name Pipes. but it also gives me error. Please provide me the solution for the same.-
Changed type
Monday, August 26, 2013 11:43 AM
More a question rather then a discussion -
Moved by
Olaf HelperMVP
Monday, August 26, 2013 11:44 AM
Moved from «SQL Database Engine» to a more related forum for a better response.
-
Changed type
- Remove From My Forums
-
Question
-
I am stuck with some error in MS SQL 2005. I am not able to access it. It is giving me network related error 10061. I have tried to enable TCP protocol under that instance. But it is giving me error. it is not starting. I also check the SQL
Server Surface Area Configuration>select that instance> Database Engine > Remote Connections. under that try to select last radio
butten i.e both TCP and name Pipes. but it also gives me error. Please provide me the solution for the same.-
Changed type
Monday, August 26, 2013 11:43 AM
More a question rather then a discussion -
Moved by
Olaf HelperMVP
Monday, August 26, 2013 11:44 AM
Moved from «SQL Database Engine» to a more related forum for a better response.
-
Changed type