Here is the November 2024 release of the on-premises data gateway (version 3000.246.5).

Announcements

Fabric Pipeline Integration in On-premises Data Gateway is now generally available

This release of the on-premises data gateway is now ready to support your production Pipelines in connecting to on-premises data sources.

This is a significant milestone in expanding our data integration offering, as you can now use the Copy Activity with on-premises sources.

Bug Fix for Fabric Pipelines through on-premises data gateway

Resolved an issue in Fabric Pipeline when using Azure Data Explorer as the sink.

SQL Server certificate isn’t trusted on the client (Power BI Desktop or on-premises data gateway)

Users on the September gateway release or later connecting to SQL will need to make the changes below or will see SQL errors.

When establishing a connection to an on-premises SQL Server using the on-premises data gateway or Power BI Desktop and the SQL Server utilizes a self-signed certificate, it’s possible that the refresh operation for a Fabric semantic model or dataflow can fail with the following error message:

Microsoft SQL: 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.)

To avoid or fix this error when using on-premises data gateway, change the gateway configurations to update the SqlTrustedServers setting using the following steps:

1. On the local machine where the on-premises data gateway is installed, navigate to C:\Program Files\On-premises data gateway.
2. Make a backup of the configuration file named Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config.
3. Open the original Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config configuration file and locate the SqlTrustedServers entry.
4. Update the SqlTrustedServers value with the names of the SQL servers to trust and connect to.
   The value contains a comma-delimited list of server names and supports * as a wild card. So for instance in the following example:
   <setting name="SqlTrustedServers" serializeAs="String"> <value>contososql*,mysvr</value> </setting>
   the value contososql*,mysvr matches contososql6, contososqlazure, and mysvr, but doesn’t match mysvr.microsoft.com.

To troubleshoot this error when using Power BI Desktop, modify the value of the environment variable PBI_SQL_TRUSTED_SERVERS to include the SQL Servers. The supported values are the same as outlined for gateway configuration (as described in step 4 above).

For connections to SQL Server from Power BI Desktop and on-premises data gateway versions starting with February 2024, follow one of these options:

• Follow the solution mentioned previously to add the environment variable PBI_SQL_TRUSTED_SERVERS.
• Ask your SQL administrators to acquire a certificate from a well-known certificate authority.
• Change the setting SqlTrustedServers on the gateway config file.

Power BI Desktop Compatibility

This update brings the on-premises data gateway up to date with the November 2024 release of Power BI Desktop.

This version of the gateway will ensure that the reports that you publish to the Power BI Service and refresh via the gateway will go through the same query execution logic/run-time as in the November version of Power BI Desktop. View the data connectivity section of Power BI’s November 2024 feature summary for updates on relevant connectors.

Thank you!

Please continue to send us feedback for what new capabilities you’d like to see in the future! You can vote for your favorite feature suggestions at Ideas (powerbi.com).