Connection Error: SQLState: '01000' SQL Server Error: 10061

Question

I am trying to connect my access interface to SQL Server.

It worked when SQL Server was on my computer, but now I'm trying to connect to the server

Therefore, when I create a DSN file with access

• I chose the SQL-Server driver (I also tried with the native SQL-Server 10.0)
• I enter the server name that I copied from SQL Management Studio so that there are no typos
• I chose NT authentication

Then I have this error

In properties, I tried with TCP/IP with port 1433 by default, and I also tried with pipe names

I made sure that the check box for remote connection is checked

If I try to connect to the management studio, I got this error

I see the server when I browse the network

I try this troubleshotting, but I'm stuck on the telnet team. It says Could not open connection to host on 1433

I also tried without port, and I got the same error on port 23

Any ideas?

thanks

Answer 1

This solved my problem.

I thought that when the TCP port is empty, it means that the default port value is 1433, but not ...

Answer 2

I had the same error that was coming and you do not need to worry about this error, just restart the server and restart the SQL services. This problem occurs when there is a problem with disk space and the system goes into a freeze state, and then sql services automatically stop.

Answer 3

Received SQLSTATE 01000 in the following error message below:

SQL Agent - Failure: SQL Agent "LiteSpeed ​​Backup Full" failed with the message "Job failed. The initiator was called by user X. The last step to start was step 1 (step 1). NOTE: Failed to report Email - Performed 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 was unable to open the backup file : (N: \ BACKUP2 \ filename .BAK). The previous system message caused the failure. [SQLSTATE 42000] (Error 60405). The step could not be completed. "

In my case, this was due to permission to drive N after SQL Server crashed in an Active / Passive SQL cluster.

All SQL resources in which the seconary session failed to complete and return to the preferred node after maintenance. When the Quest LiteSpeed ​​job was run on the preferred node, it was clear that previous permissions for the SQL server SQL user were lost on drive N and SQLSTATE 10100. It is reported that

Simply added permissions again to the backup destination disk, and the problem was resolved.

Hope this helps someone.

Windows 2008 Enterprise

Active / Passive Cluster SQL Server 2008.

Answer 4

To create a new data source for SQL Server, follow these steps:

• In the host computer / server, go to Sql server management studio → open the security section on the left → right-click on the login name, select “New Login”, and then create a new account for your database, connect to.

• Check if TCP / IP is enabled. go to All Programs → Microsoft SQL Server 2008 → Configuration Tools → open Sql Server Configuration Manager. On the left side, select client protocols (based on your 32/64 bit operating system). On the right side, check the TCP / IP protocol.

• In the remote computer / server, open the data source administrator. Control Panel → Administrative Tools → Data Sources (ODBC).

• In a custom DSN or system DSN, click the Add button and select the Sql Server driver, and then click Finish.

• Enter your name.

• Enter the server, please note that: if you want to enter the address of the host computer, you must enter its IP address without "\\". eg. 192.168.1.5 and click "Next."

• Select Using SQL Server Authentication Using the Login ID and Password Entered by the User.

• Enter your username and password below that you created in the first step. and then click "Next."

• If the database is shown - this is your database, click Next and then Finish.

Answer 5

• Windows Firewall is blocking sql server. Even if you open port 1433 from the exceptions, on the client machine it sets the connection point to the dynamic port. Add also sql server to exceptions.

"C: \ Program Files \ Microsoft SQL Server \ MSSQL11.MSSQLSERVER \ MSSQL \ Binn \ Sqlservr.exe"

Additional Information

2. This page helped me solve the problem. Special

or if you feel brave, find the alias in the registry and delete it there.

HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ MSSQLServer \ Client \ ConnectTo \