Error Connecting to SQL Server Using Gateway: Encryption Issue

[shakir_khananai]

Hello everyone,

I am encountering an issue while trying to connect to a Microsoft SQL Server using a gateway. The error message I receive is as follows:

We were unable to connect to the data source using an encrypted connection. To use an unencrypted connection, uncheck "Use encrypted connection" and try again.

1. Checked Connection Settings:
   • Verified the server name, authentication method, and other connection details.
2. Attempted to Disable Encryption:
   • Tried to find an option to uncheck "Use encrypted connection" in the connection settings, but I am unsure if I am doing it correctly.

Has anyone else experienced a similar issue? If so, could you provide some guidance on how to successfully connect without encryption or any troubleshooting steps that might resolve this error?

Any help or suggestions would be greatly appreciated.

Thank you!
Shakir

[RATG]

This article might help:

SQLingRAT: Microsoft Fabric Data Pipeline Connection Error - Created Using Copy Assistant

[robert2001b]

If you’re using Blob APIs, NFS 3.0, and Data Lake Storage Gen2 APIs to operate on the same data, be aware of their limitations. For instance, you can’t use blob APIs, NFS 3.0, and Data Lake Storage APIs to write to the same instance of a file. There might be an issue with the certificate validation during the TLS handshake. Engage your network team to check the local network configuration. 

fidelitynetbenefits

[v-cboorla-msft]

Hi @shakir_khananai 

Thanks for using Microsoft Fabric Community.

The error message indicates an issue with establishing an encrypted connection to the SQL Server through the gateway in Microsoft Fabric.

Here are some potential issues related to data source connectivity that might help you :

Credentials Verification: Double-check your credentials. Sometimes, the error occurs due to incorrect username/password, or you might need to use a different authentication method. Consider if a different authentication method is required and try again.

Firewall or Network Restrictions: Your network may have restrictions that prevent the connection to your SQL Server. Make sure the necessary ports are open and that your SQL Server is accessible from the machine where the gateway is installed.

On-Prem gateway version: It might be beneficial to upgrade the on-premises gateway to the latest version. Newer versions often include bug fixes and improvements that could potentially resolve the issue with encrypted connections.

For latest version please refer : On-premises data gateway

If the issue still persists, please do let us know. Glad to help.

I hope this information helps.

Thank you.

[shakir_khananai]

Hello,

Thank you for your response and the suggestions. I have reviewed the potential issues you mentioned and have the following updates:

1. Credentials Verification: I have double-checked the credentials, and they are correct. The issue persists despite using the correct username and password.

2. Firewall or Network Restrictions: I don't believe this is the issue, as I can successfully connect using ADLS Gen2 (Power Query), which warns about connecting unencrypted but does connect without any problems.

3. On-Prem Gateway Version: The gateway is up to date. I installed the latest version just yesterday, so I am confident this is not the cause of the issue.

Despite these checks, the error continues to occur. Could there be any other underlying issues or configurations that I might be missing? I appreciate any further assistance or guidance you can provide.

Thank you!

[v-cboorla-msft]

Hi @shakir_khananai 

Apologies for the inconvenience and delay in response.

Please reach out to our support team to gain deeper insights and explore potential solutions. It's highly recommended that you reach out to our support team. Their expertise will be invaluable in suggesting the most appropriate approach.

Please go ahead and raise a support ticket to reach our support team:

https://support.fabric.microsoft.com/support

After creating a Support ticket please provide the ticket number as it would help us to track for more information.

Thank you.

[v-cboorla-msft]

Hi @shakir_khananai 

We haven’t heard from you on the last response and was just checking back to see if you've had a chance to submit a support ticket. If you have, a reference to the ticket number would be greatly appreciated. This will allow us to track the progress of your request and ensure you receive the most efficient support possible.

Thanks.