Home » SQL Server Error Connection Failed Error 17

SQL Server Error Connection Failed Error 17

SQL Server Error : 17 Details


Connection failed:

SQLState: ‘08001’
SQL Server Error: 17
[DBNETLIB][ConnectionOpen (Connect().]SQL Server does not exist or access denied.

The message ‘SQL Server does not exist or access is denied’ is a generic Microsoft Data Access Components (MDAC) warning indicating that the computer executing Microsoft SQL Server is unavailable.

As part of our Server Management Services for web hosts and online service providers we can help. Contact us:[email protected]

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Go

The parameters for XP_READERRRORLOG are:
1. Value of error log file we would like to read. values are 0 = current, 1 = last one before current, 2 = second last before current etc…
2. Log file type:- 1 or NULL = error log, 2 = SQL Agent log
3. Search string 1:- String one you want to search for
4. Search string 2:- String two you want to search for to further refine the results
5. start time for Search
6. end time for search
7. Sort order for search results:- N’asc’ = ascending, N’desc’ = descending

By default, we have 6 Server Error Logs kept but we can increase the number of SQL Server Error Logs from the default value of six.

For other ways to read and find error log location please our artcile https://sqlserver-dba.co.uk/error-log/sql-server-identify-location-of-the-sql-server-error-log-file.html

Additional information:

Server-side issues: If none of the client PCs can connect to the SQL server, there is a problem on the server side. The following are some of the server-side issues:

  • The SQL server is not installed on the machine that is given in the connection string.
  • The SQL Server service has not been launched.
  • The SQL Server name is distinct from the computer’s name.
  • The database is currently unavailable.
  • Database files are renamed.
  • The database has been transferred to a new server.

Client-side issues: If one or more clients are unable to connect to the SQL Server, the problem is most likely on the client’s end. The following are some of the client-side issues:

  • On the SQL Server, the name of the computer does not exist.
  • If you’re trying to access a SQL Server named occurrence, make sure you use the correct occurrence name.
    Incorrect protocol was used.
  • Because of the presence of any cluster in SQL Server, the network adapters may be wrongly configured or have an inaccurate name.
  • It could just be a result of an MDAC mismatch.

Solution for Resolving the Error

  • Check the firewall settings for the server operating system if the firewall on the server is blocking any inbound connections. However, if it is enabled, double-check that the SQL Server’s port number is open in the firewall. Also, make sure that UDP port 1434 is open (if you are using dynamic ports).
  • Use the SQL Server configuration tools to see if TCP/IP and Named Pipes are enabled or not.
  • Verify that the database is connected and accessible. If this is not the case, then attach the database. Bring the database online if it is currently offline.
  • Make sure the SQL Server service is running. If you’re using a dynamic port, make sure the SQL Server Browser service is running.

Alternate Solutions or other common troubleshooting steps

  1. Restarting SQL Server Service(non production instances only)

  • To Restart, Start or Stop the SQL Server instance by right click on sql server instance in SSMS or in SQL. You may need to open SSMS as administrator to start, stop the instance.

db-mail4

  • Other ways for restarting SQL server Service

  1. From SQL Configuration manager from Start menu
  2. From Services in Windows server
  3. From Cmd using net start and net stop

2.Checking SQL Performance metrics like CPU, Memory

Check SQL Server CPU, Memory usage, longest running queries, deadlocks etc.. using activity monitor or sp_who2.

To view Activity Monitor in SQL Server 2005 and in SQL Server 2008, a user must have VIEW SERVER STATE permission.

2 Different Ways to Open up Activity Monitor in SQL Server 2008 are mentioned below:

Open up Activity Monitor Using Object Explorer

In Object Explorer, right click the SQL Server 2008 Instance and click on Activity Monitor.

Also can be opened from SQL Server 2008 Management Studio’s toolbar, by clicking Activity Monitor

Opening SQL Server Activity Monitor method2

SSMS Activity Monitor by Method2

It shows the graphical display of Processor Time (%), Number of Waiting Tasks, Database I/O (MB/Sec) and the Number of Batch Requests/second.

For information on SQL Server Activity monitor go to https://sqlserver-dba.co.uk/sql-server-administration-basics/activity-monitor

Or using SQL Query analyzer window to run sp_who2 command which is less resource intensive and gives same information as activity monitor.

2.Checking Windows Performance metrics like CPU, Memory, Disk Space etc.

  1. Open task manager to check CPU, Memory usage etc.
  2. Open file explorer to check Disk space on each drive.

 

SQL Server Error Code and solution summary

Connection failed:

SQLState: ‘08001’
SQL Server Error: 17
[DBNETLIB][ConnectionOpen (Connect().]SQL Server does not exist or access denied.

Solutions include

  • Checking the firewall settings
  • SQL Server configuration tools to see if TCP/IP and Named Pipes are enabled or not.
  • Verify that the database is connected and accessible.
  • Make sure the SQL Server service is running.
  • If you’re using a dynamic port, make sure the SQL Server Browser service is running.

Leave a Reply

Your email address will not be published. Required fields are marked *