Ошибка sql server 10061

TITLE: Connect to Server ------------------------------
  • 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

  • Remove From My Forums
  • Question

  • Hi,

    I have been using this database server for the past couple of years. I was working on some reports and closed it yesterday. Once I tried to open SQLserver and tried connecting to database engine and I get the below error. However I am bale to connect fine
    to Analysis server. Can you please help?

    Here is the error:

    TITLE: Connect to Server
    ——————————

    Cannot connect to pname-xpSQLSERVER.

    ——————————
    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)

    • Changed type

      Thursday, August 15, 2013 12:26 PM
      Question

Answers

  • You can tell whether the SQL Server is started, and both start and stop the service using the Windows services console (services.msc). Just be careful NOT to use services.msc to change the accounts used by SQL Server. That will not work.

    How to Troubleshoot Connecting
    to the SQL Server Database Engine
      


    Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

    • Marked as answer by
      Allen Li — MSFT
      Thursday, August 15, 2013 12:27 PM

  • Remove From My Forums
  • Question

  • Hi,

    I have been using this database server for the past couple of years. I was working on some reports and closed it yesterday. Once I tried to open SQLserver and tried connecting to database engine and I get the below error. However I am bale to connect fine
    to Analysis server. Can you please help?

    Here is the error:

    TITLE: Connect to Server
    ——————————

    Cannot connect to pname-xpSQLSERVER.

    ——————————
    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)

    • Changed type

      Thursday, August 15, 2013 12:26 PM
      Question

Answers

  • You can tell whether the SQL Server is started, and both start and stop the service using the Windows services console (services.msc). Just be careful NOT to use services.msc to change the accounts used by SQL Server. That will not work.

    How to Troubleshoot Connecting
    to the SQL Server Database Engine
      


    Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

    • Marked as answer by
      Allen Li — MSFT
      Thursday, August 15, 2013 12:27 PM

  • Remove From My Forums
  • Вопрос

  • Hi,

    I have been using this database server for the past couple of years. I was working on some reports and closed it yesterday. Once I tried to open SQLserver and tried connecting to database engine and I get the below error. However I am bale to connect fine
    to Analysis server. Can you please help?

    Here is the error:

    TITLE: Connect to Server
    ——————————

    Cannot connect to pname-xpSQLSERVER.

    ——————————
    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)

    • Изменен тип

      15 августа 2013 г. 12:26
      Question

Ответы

  • You can tell whether the SQL Server is started, and both start and stop the service using the Windows services console (services.msc). Just be careful NOT to use services.msc to change the accounts used by SQL Server. That will not work.

    How to Troubleshoot Connecting
    to the SQL Server Database Engine
      


    Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

    • Помечено в качестве ответа
      Allen Li — MSFT
      15 августа 2013 г. 12:27

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

  1. I chose SQL-Server driver ( I have also tried with SQL-Server native 10.0 )
  2. I enter the server name that I copied from SQL Management Studio so there’s no typo there
  3. I chose the NT authentication

Then I have this error

enter image description here

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

enter image description here

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

Marc's user avatar

MarcMarc

15.9k20 gold badges73 silver badges118 bronze badges

5

To create a new Data source to SQL Server, do the following steps:

  1. 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.

  2. 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.

  3. In Remote computer/server, open Data source administrator. Control panel —> Administrative tools —> Data sources (ODBC).

  4. In User DSN or System DSN , click Add button and select Sql Server driver and then press Finish.

  5. Enter Name.

  6. 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.

  7. Select With SQL Server authentication using a login ID and password entered by the user.

  8. At the bellow enter your login ID and password which you created on first step. and then click Next.

  9. If shown Database is your database, click Next and then Finish.

answered May 25, 2016 at 7:45

Vahid's user avatar

VahidVahid

912 silver badges3 bronze badges

  1. 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

  1. 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

Hysen's user avatar

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

krish's user avatar

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_lotus's user avatar

scott_lotusscott_lotus

3,14521 gold badges50 silver badges69 bronze badges

Понравилась статья? Поделить с друзьями:
  • Ошибка sql error 1146
  • Ошибка stalker coc exe
  • Ошибка steering fault рено сценик 2
  • Ошибка sql 9004
  • Ошибка stack overflow это