after update of bpi desktop this weekend having various issues, not a pbi person if thats not obviou

[pbissue]

1st the certs were not trusted, fixed that by setting an evironment variable but now we are having issues with directory queries. previewing the direct query works but when you actually use it you get an error.

Error Message:
We couldn't connect to your DirectQuery data source or internal model. Double-check that your server and database names are correct, and that you have permission to access them.

I don't know how I could preview the data if the account permissions and server name were wrong

thanks for any insights on this issue

[salamander]

Has this been resolved? I am having a similar issue

[pbissue]

thanks for the reply, so the issue started after they upgrade their desktop to current this last weekend, also btw there is no gateway being used just desktop.  The 1st issue was that the cert wasn't trusted but that was fixed by using the enivronment variable PBI_SQL_TRUSTED_SERVERS.  That fixed most issues but then they tried a directorquery that failed. Gave the account SA on the server for test purposes, it errors out on views or tables. 

[Anonymous]

Hi @pbissue ,

Based on the information you have provided, it appears that you are experiencing some difficulties, so let us work through these step-by-step.

1. As the error message indicates, double-check that the server and database names in the DirectQuery connection exactly match the configuration in Power BI Desktop and the gateway.

2. While it is possible to preview data, specific permissions may be required for broader operations not covered by the preview. Please ensure that the account used by DirectQuery has the necessary permissions on the data source.

If the above steps do not resolve your issue, can you provide more details to help diagnose the issue further:
Has this issue happened before, did it happen suddenly, did you do anything else before it happened?
Can you provide a detailed screenshot of the error report and the opportunity for it to occur, this will help us to better understand and resolve your issue.

Best Regards,

Ada Wang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[pbissue]

worked with ms support on this and we discovered that this is a bug in the newest version of the desktop.