SQL Server Does Not Exist Or Access Denied

Have you ever encountered with the issue of” SQL Server does not exist or access denied”?  Then what’s your initiative to fix this out?  Do you know why you are getting these kinds of error.

If no, then don’t worry as the following blog will help you in exploring more about this SQL Server does not exist or access denied error  and ways to resolve it easily.

Practical Scenario:

Today about 1 pm some users started receiving the following error. We had not made any changes, so I am not sure what is going on. The weird part is that at this same time it started using the sql browser with a different port at this same time. Any ideas would be helpful. 

(FOC1400) SQLCODE IS 17 (HEX: 00000011) XOPEN: 08001 : Microsoft OLE DB Provider for SQL Server: [08001] [DBNETLIB][ConnectionO : pen (Connect()).]SQL Server does not exist or access denied. L (FOC1406) SQL OPEN CURSOR ERROR.

source: http://forums.informationbuilders.com/eve/forums/a/tpc/f/7971057331/m/1647017686

What’s This “SQL Server Does Not Exist Or Access Denied” Error Is?

SQL Server Does Not Exist Or Access Denied is common Microsoft Data Access Components (MDAC) message that gives a clear indication that the computer is running

Microsoft SQL Server can’t be contacted. Following are the potential causes of this dbnetlib connectionopen (connect()). sql server does not exist or access denied error message.

Besides that error messages also have similar causes.

SQL Server is unavailable or does not exist.

The specified SQL Server is not found. 

 SQL SERVER connectivity error

Well the above error doesn’t indicate the following:

  • SQL Server Login process failure.
  • To process query, SQL Server doesn’t have that much of permission. 
  • You are unable to use SQL Server authentication because you have only got the permission of  Windows authentication.

Why You Are Getting “SQL Server Does Not Exist Or Access Denied” Error?

Well the following SQL Server does not exist or access denied errors occurs when MDAC (Microsoft Data Access Components) message that shows the PC is running the SQL Server cannot be connected.

Here the possible causes for the occurrence of this error.

  • May be the SQL Server is currently unavailable or doesn’t exist anymore.
  • Remote connection is disabled for SQL instance
  • Port is not added in the firewall exception list
  • May be the IP address of the instance is blocked

How To Fix The “SQL Server does not exist or access denied “error?

Here are some best fixes to troubleshoot dbnetlib connectionopen (connect()). sql server does not exist or access denied error. Take a quick overview of it:

1: Check Whether the SQL Server is running or not

2: SQL Server instance is not available or does not exist

3: Remote connection is not enabled for a SQL Server instance

4: Port is not added in the firewall exception list

5: IP address of the SQL Server Instance is blocked the Firewall

6: connect remote SQL Server using Server Name

7: Allow the instance name to measure the connection information

Let’s discuss all these listed method in brief….!

Method 1: SQL Server is running

The very first thing you need to do is to check that if the sql server is running or not. to check this just type the “services.msc” command in the Run Window.

Method 2: SQL Server instance is not available or does not exist

Make a check for the connection strings and be sure that you are trying to connect the right server and it’s available on the network.

Method 3: Remote connection is not enabled for a SQL Server instance

Check whether the remote connection is enabled or disabled. For this just open the SQL Server Management Studio -> Connect to SQL Server where it get installed using SQL Server Management Studio ->Go to SQL Server instance property and make a check in front of the Allow remote connection to this server option box.

Method 4: Port is not added in the firewall exception list

It is also seen that SQL Server does not exist or access denied error message also encounters when SQL Server remote connection is enabled. But somehow the port is get blocked by the administrator for security purpose.

By default SQL Server instance actually works on port no 1433, so you need to check that the port exception is get added to firewall.

In order to check the port exception, just try the following steps:

    • Start with the Control Panel -> and then open Administrative Tool -> after then select Windows firewall with Advanced Security.
    • From left panel, tap to the Inbound Rules and from right panel select New Rule…
    • In the New Inbound Rule Wizard window, make selection for the Port and after then tap to the Next button.
    • In next tab, enter ‘1433’ in Specific local ports and tap to the Next button.
    • Within the “what action should be taken when a connection matches the specified condition?” Section. You have to make selection for the Allow the connection option and after then tap to the Next option.
    • Make a check for the DomainPrivatePublic under which does this rule apply section? And tap to the Next option.
    • Assign name for this and tap to the finish button.

Method 5: IP address of the SQL Server Instance is blocked the Firewall

If you want to check whether the SQL Server does not exist or access denied 2016 error is occurring because of IP address, ping IP address on the command prompt like

Ping 100.10.10.10 –t

If you are getting response from the server then it means there is no issue with IP Address blockage but if not, they need to add exception.

Method 6: connect remote SQL Server using Server Name

Step 1: First verify, status of your protocol name.

1

After that on the client side you have to make the alias.

Step 2: Now search for the cliconfig.exe present within System32 folder. After getting cliconfig.exe  file, just tap on it.

2

Step 3: Now it’s time to make a TCP/IP alias. So, from the disabled protocols list choose the TCP/IP. After then hit on the Enable button.3

Now you will see that your selected TCP/IP protocol will get added under the section of Enabled protocols by order .

Note: please ensure that the list doesn’t contain any Named Pipe. Suppose if in the list you get any Named Pipes then immediately disable it.

Step 4: Next move to the tab “Alias”. 

4

Step 5: After then hit Add button.

5

Step 6 :  Now in the section of “Server alias” you require to enter the SQL Server database’s Server name.

6

Step 7 : And choose the section TCP/IP present in the option box of Network libraries.

In the same add network library dialog box you will see a connection parameter section. here in the  server name you need to enter the IP Address of the SQL Server. After that hit the OK option.

7

Note: SQL Server’s default port number is 1433.

Step 8: Then tap to the Network Libraries for verifying the entries.

8

And you can get easy connection with the remote SQL Server by making use of the Server Name.

Method 7: Allow the instance name to measure the connection information

SQL Server 2005: In the SQL Server 2005, for measuring the connection detail the server gives instance name.

Solution: User needs to remember one thing, that the instances name must be included in assigned Server name.  As shown in the figure.

9

You can view the Server Name that is included along with the instance name i.e P6Instance.

Please Note: At the time you choose the by default instances that is already present on your PC. Then this will automatically take upgrade by the setup of SQL server. Apart from this a single system can only host just a default single instance.

Conclusion

In the above blog you must have got the possible reasons for SQL Server does not exist or access denied error and explained the solution to resolve the error.

Also Read:

How To Convert OR Migrate An Access Database To SQL Server

How To Fix Ms Access Error ‘3022’: “The Changes You Requested To The Table Were Not Successful “?

 

7 Fixes To Resolve “SQL Server Does Not Exist Or Access Denied” Error