Forum Discussion
PowerBi DirectQuery + SQL Data Connection Issue
- 4 years ago
v-janeyg-msft It is solved now. The encryption was to be enabled on the SQL Server side – As our server is internal-only we hadn’t enabled encryption on the connection.
Hi, shaht
Why are there two gateways? What is the connection information of LiveData in the gateway?
The upper one is running on my lcoal PC but i am not using it anymore.
The information is as below
- v-janeyg-msft4 years agoCommunity Support
I see that the account don't seem to match.
Can you refresh other reports such as local excel files using this gateway below?
- shaht4 years agoHelper I
Yes the personal gateway is running on my pc. the data set get refreshed successfully. On premise gateway is on Admin PC.
- v-janeyg-msft4 years agoCommunity Support
- shaht4 years agoHelper I
v-janeyg-msft It was successful only for personal gateway. For on-premises I am having the issue. My IT team just advised me that data source Encryption should be ON for gateway connection. They are testing it right now. I hope it will solve it.
- v-janeyg-msft4 years agoCommunity Support
Hi, shaht
Have you tried to change the authentication method to 'window'? I found that my machine will fail to connect if I use 'basic'. Since your personal gataway can connect successfully, The problem must be in the configuration of the service.
- shaht4 years agoHelper I
Yes Windows was the first option. Then I got special SQL credentials from IT with no restrictions and I used basic method, but still same issue. The error has been same in all cases.
What are your thoughts on the 'Encryption' option ?
- v-janeyg-msft4 years agoCommunity Support
Actually the 'Encryption' option you mentioned, I never noticed it, this step on the desktop is not important. Of course, it would be great if just ticking this option would solve the issue.
I still think it is because the service is not configured properly, you should always unify the credentials in the desktop and service.
Manage your data source - SQL - Power BI | Microsoft Docs
Janey
- shaht4 years agoHelper I
v-janeyg-msft It is solved now. The encryption was to be enabled on the SQL Server side – As our server is internal-only we hadn’t enabled encryption on the connection.