Forum Discussion
PowerBi DirectQuery + SQL Data Connection Issue
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
Can you find more specific error messages like this:
I found some thread with similar situation:
Solved: Unable to connect to the data source undefined - Microsoft Power BI Community
Solved: Unable to Connect to Data Source Undefined - Microsoft Power BI Community
Solved: data gateway cluster and failed refresh: "Unable t... - Microsoft Power BI Community
Hope it helps.
Did you map to the correct data source? The gateway is also not the same as the previous one. I feel like I didn't get your specific info...
Janey
v-janeyg-msft Yes Gateway is now running 24 hours on an admin account. Previously it was running locally on my PC. So datasource is correct.
i also tried a dirrenet datasource, but it showed the same error. So the issue is with SQL server connection. Is there any permission to be given in SQL server setting to make this work ?
this is the message i get when i try to refresh import file
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
I see that the account don't seem to match.
Can you refresh other reports such as local excel files using this gateway below?
Yes the personal gateway is running on my pc. the data set get refreshed successfully. On premise gateway is on Admin PC.
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.
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.
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 ?
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
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.