CAN'T CONNECT TO MS SQL SERVER

[tuyencv]

Hi, I am experiencing a connection issue between Data Studio and MS SQL Server. I have entered the correct IP address of the machine, opened port 1433 for SQL, and created a user login with sysadmin permissions. I have filled in all the necessary information for the connection, but it is still not successful.
Please help me with this. Thank you!

[Nathy]

Hey!
Could you share the error you are getting?
What is your MS SQL Server version?

[jonfree]

I have this same issue. The error message is not helpful at all. 

[Nathy]

Could you share the error you are getting?
What is your MS SQL Server version?

0 Likes

[Nathy]

Could you share the error you are getting?
What is your MS SQL Server version?

[jonfree]

Sorry, we encountered an error and were unable to complete your request Error ID: af003cfb

[abjames]

I have the same issue. I am trying to connect to a SQL Server 2019 system, but the instance is 2017. It seems this may not be allowed. I am getting the "sorry we encountered an error" message but the error ID changes every time I try to connect. I would prefer to be able to connect using Windows authentication but that doesn't seem to be an option at all so I'm trying on a SQL Server authenticated database. 

[Nathy]

It's likely that the incompatibility between Looker's requirement for SQL Server 2019 and your existing 2017 instance is causing the connection issue. The changing error IDs might indicate underlying compatibility problems that Looker is struggling to handle

Please, verify that there are no network firewalls or restrictions preventing Looker from reaching your SQL Server instance.

Some extra configuration checks:
- Ensure the "SQL Server Browser" service is running on the SQL Server machine. This service helps Data Studio discover the SQL Server instance.
- Confirm that the TCP/IP protocol is enabled in SQL Server Configuration Manager.
- In SQL Server Management Studio, right-click on the server instance, go to "Properties" > "Connections", and ensure that "Allow remote connections to this server" is checked.

You also can try to check the connectivity by doing a Telnet from a machine where Data Studio is running, try using telnet ServerIPAddress 1433 (replace with your actual IP and port). If successful, you should see a blank screen. If not, it indicates a network issue. 
- Attempt to connect to the SQL Server using SQL Server Management Studio from the same machine where Data Studio is running. This helps isolate whether the issue is specific to Data Studio or a general connectivity problem.

[abjames]

Thanks for the suggestions. I don't have access to try all of the things
you mentioned, unfortunately. I'll see what I can manage with help from my
DBA.


*Andrea James*

Sr Software Engineer, Application and Software Engineering

Post Acute Application Support

Information Technology (IT)


*CommonSpirit Health**®*

Caution: This email is both proprietary and confidential, and not intended for transmission to (or receipt by) any unauthorized person(s). If you believe that you have received this email in error, do not read any attachments. Instead, kindly reply to the sender stating that you have received the message in error. Then destroy it and any attachments. Thank you.

[jonfree]

I'm using Azure SQL. And my firewall is open to the relative IPs. All of your other suggestions aren't really relative to Azure SQL server as I have no access to the host machine.

Is there no one who can support on a one to one level for this product?