Forum Discussion
DirectQuery reports not loading in PowerBI service
It must be because it uses some other way to connect when using DirectQuery
I would think it should work if it is seen as a SQL Server source?
That's what we thought, but that resulted in the error message from my first post.
When ticking the SSO box as you mentioned earlier we get a different error by the way: "This report couldn't access the data source. Contact [my name], the author, to have it fixed"
- GilbertQ6 years agoSuper UserHi there
What happens if you use a SQL Server Account for authentication?- fabbimk6 years agoFrequent Visitor
It does not seem to make a difference whether Windows authentication or basic SQL server account is used. For both it says in the data source settings that the connection is successful, but when opening the report I get the same error message.
- TheCatt6 years agoNew Member
Do you have the GatewayErrors log from the Gateway? That will give you the definitive answer as to why your connections are failing.
The generic error message obscures a lot of other errors.
For instance, if you have upgrade your AWS RDS certificate, but it's not installed on the client (gateway) machine, you will get this error, despite the data source settings test working.
In the log, you'll see: [1]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.GatewayPipelineWrapperException: Substituted: SqlException:<pi>System.Data.SqlClient.SqlException (0x80131904): A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) ---> System.ComponentModel.Win32Exception (0x80004005): The certificate chain was issued by an authority that is not trusted