61

I cannot connect to my local SQL Server Express (2012, but the version shouldn't matter) from my server (Windows 2008 R2) to use a tool on it (APEX SQL Data Diff if you are wondering). I can browse the network servers fine, and select my local instance from the dropdown of available servers, but when I go to search tables on the server, it times out with this error message (same is true of SSMS).

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: SQL Network Interfaces, error: 28 - Server doesn't support strong text requested protocol) (Microsoft SQL Server, Error: -1)

I have enabled the firewall - that's not it.

I have allowed remote connections - that's not it.

SQL Server Browser service is on and passed through the firewall - that's not it.

I can connect fine with the same tools TO the server, but FROM the server it fails.

Any ideas?

marc_s
  • 732,580
  • 175
  • 1,330
  • 1,459
Watki02
  • 4,696
  • 7
  • 34
  • 36

3 Answers3

127

Thanks to this article for getting me somewhere with the error message. The issue is the necessary network protocols are disabled by default in SQL Server Express. I had to go to Sql Server Configuration Manager locally and turn on "Named Pipes" and "TCP/IP". After that, you need to restart the SQL Server Browser and SQL Server(instance) services.

SQL Server Config manager

While I did not have to, you may also need to check in "SQL Server Network Configuration" under "Protocols" for settings that need adjusted there.

starball
  • 20,030
  • 7
  • 43
  • 238
Watki02
  • 4,696
  • 7
  • 34
  • 36
  • 3
    +1 - I have been struggling with this. You deserve a medal. Thanks very much. – Rouan van Dalen May 17 '13 at 08:57
  • 1
    Then why not +1 the quetion as well as the answer? – Watki02 May 17 '13 at 15:06
  • 8
    This helped me as well, I had the same problem, but I had to do it under the SQL Server Network Configuration as well. – Taegost Jun 29 '13 at 16:37
  • 1
    In particular check the Protocols for SQLEXPRESS, they are disabled by default. – Saher Ahwal Jan 21 '17 at 02:00
  • If anyone can't find Configuration Manager, [here](https://stackoverflow.com/questions/9844771/sql-server-configuration-manager-not-found) is what helped me find it. – dotNET Jun 26 '18 at 11:57
  • Absolute legend! The mystery remains as to WHY we have to go and do this, and also why a core app using dbup connected fine, where-as another which used SqlConnection directly failed. – Kinetic Sep 18 '20 at 13:04
  • The Client Protocols were already enabled for me, but enabling same protocols under "SQL Server Network Configuration -> Protocols for SQLEXPRESS" worked for me! – Vinod T. Patil Apr 08 '21 at 17:12
16

SQL Configuration Manager:

SQL Configuration Manager

The picture has the wrong group selected on the link panel: it should be SQL Server Network Configuration → Protocols for SQLEXPRESS.

H. Pauwelyn
  • 13,575
  • 26
  • 81
  • 144
Teo
  • 330
  • 2
  • 9
13

Don't forget to also check under "SQL Server Network Configuration" -> Protocols for YourInstance. I was a bonehead and forgot to look there too.

ChrisM
  • 1,576
  • 6
  • 18
  • 29
Mike
  • 131
  • 1
  • 2