When I publish the power bi report from power bi report builder to the Power BI workspace with the following connection details, in public setting it works fine. The report loads in 3 secs.
Data Source=Azure cloud server;Initial Catalog=database name;Encrypt=True;Trust Server Certificate=True;Authentication=SqlPassword
But when I switch to private end point using VNET by creating a virtual data gateway and when I provide the same connection details I am getting error saying that is not support.
Could not connect to the data source. A data source used by this report returned an error. If you continue to experience this error contact the report author or data source owner quoting: DM_GWPipeline_UnknownError. Received error payload from gateway service with ID Keyword not supported: 'trust server certificate'.. Keyword not supported: 'trust server certificate'. Learn more: .
So when I removed the Trust server certificate from the connection string as shown below Data Source=Azure cloud server;Initial Catalog=database name;Encrypt=True;Authentication=SqlPassword
. I am not getting the error but the report takes 30 secs to perform the handshake between powerbi worksapce and azurecloud, so whenever I perform a query using the report it takes 30 secs. Whereas in the public setting it takes only 2 to 3 secs. May I know how to decrease from 30 secs to 3 seconds in the Prviate end point setting. When I try to connect locally from the report builder tool it takes only 3 seconds, but the issue occurs when it is published in the powerbi services (Power bi workspace and Power bi apps)
Is there a way that the private end point recognize the Trust server certificate as it is currently showing not support.
Since I removed the Trust server certificate from connection string it loads, but it takes 30 secs to load the report each time in Power BI workspace and even for every single query it takes 30 secs to load the data. Would appreciate your help in this regard.
Can you please check link Error when Refreshing Power BI Gateway - Mashup error
We having similar issue and we discussed this with microsoft team and they suggested using setting EnabledResultdownload=0 and we get some reports working after trying this settings. Looks something happened at network level, we used to have working reports and somehow 2 weeks back all refresh stopped working. But after using this setting some are working fine.