Solving SQL Server Error 17

Solving SQL Server Error 17

What Exactly Does The Error Mean?

Occurring during server configuration, Error 17 signifies a communication failure between the remote connection and the host machine.

What Could Be Causing It?

There are a few factors which could potentially return an error 17 with a connection attempt (via Microsoft):

  • The server is not running
  • The SQL server software is incorrectly-configured
  • Permissions are not properly configured
  • Port 1433 is blocked, or a firewall is interfering with the connection.
  • The hostname has been entered incorrectly
  • A MDAC Mismatch has occurred (Microsoft servers only)
  • You’re using the incorrect protocol or the proper protocols are not enabled
  • You’re trying to connect with the incorrect pipe name.
  • Name resolution is broken
  • You’re trying to connect to a multihomed computer (more information)
  • Something’s going wrong with your network
  • TCP/IP Are Not Enabled
  • An SQL Driver Mismatch has occurred

What’s The Solution?

There are a few steps you should take in order to troubleshoot (and eventually correct) the error:

  • Run the command telnet (servername) 1433. If it does not work, create a rule for port 1433 on your firewall, and make sure the port is not blocked.
  • Double-check the host, server, and pipe information.
  • Double check to make sure that Named Pipes are enabled, and configure your client computer to connect through Named Pipes.
  • Verify that you are using the correct login information
  • Ensure that your server is in the Active Directory Published Directory.
  • Make sure your server is online, and that you’ve properly installed SQL
  • Verify that SQL is not running as a named instance. If it is, ensure you’re referencing your server as servername/instancename.
  • Ensure another application has not wrested control of port 1433 from SQL (via)
  • Try connecting on port 1434 instead of 1433.
  • Verify that remote tcp connections are enabled on your server.
  • Make sure you’ve downloaded the latest service packs/patches for your SQL application.
  • Double check to make sure your server isn’t missing any networking components/clients (via Microsoft)
  • If you’re making an ODBC connection, make sure you’re using the correct version of all applications (32 or 64 bit).
Follow Liberty Center One:

Subscribe with Feedly