topic Re: Encryption Support Message in Report Server

Encryption Support Message

whereismydata — Tue, 27 Sep 2022 15:21:38 GMT

Hi,

I get the following message when I connect to our on-prem SQL database with PowerBI or SSAS:

Encryption Support

We were unable to connect to the data source using an encrypted connection. To access this data source using an unencrypted connection, click OK

So, of course, clicking OK helps and I can connect to the database but I want to get rid of this message or at least understand the consequences of clicking this OK button.

I was told, all our connections are secured, but reading this message I'm not so sure

As mentioned, everything is on prem and protected by firewall. Authentication is via active directory/Windows.

Connecting to the sql server via report server does work without any problem/warning, or does clicking the OK button also surpress any warning on the report server side?

thank you!

Re: Encryption Support Message

Shahfaisal — Wed, 28 Sep 2022 11:06:50 GMT

It is because the connections are encrypted by default but it can be turned off using File->Options and Settings -> Data Source Settings > SQL Server data source > Edit and uncheck "Encrypt Connections" option.

Here is a detailed answer - https://community.powerbi.com/t5/Desktop/connect-to-SQL-DB-prompt-quot-The-data-source-you-re-trying-to/td-p/24296

Re: Encryption Support Message

whereismydata — Tue, 27 Sep 2022 15:51:25 GMT

hi, yes, but that means that our sql server does not support encrypted connection at the moment?

Re: Encryption Support Message

v-alipat — Tue, 27 Sep 2022 16:25:22 GMT

Hi,

Your SQL Server should be SSL-enabled

Please check this link for more info: https://powerbi.microsoft.com/en-us/blog/ssl-security-error-with-data-source/

🙂

Re: Encryption Support Message

Shahfaisal — Tue, 27 Sep 2022 17:29:51 GMT

whereismydata wrote:
hi, yes, but that means that our sql server does not support encrypted connection at the moment?

No, your SQL Server instance might require configuration changes to support encryption. I would check with your DBA.