Home › Microsoft Power BI › DM_GWPipeline_Gateway_MashupDataAccessError

Microsoft Power BI · DM_GWPipeline_Gateway_MashupDataAccessError · Windows 11 23H2

Power BI DM_GWPipeline_Gateway_MashupDataAccessError Windows 11 23H2

Gateway service account lacks read permissions or data source credentials are stale. Re-enter credentials and verify db_datareader role.

Error Details

FactValueSourceNote
Exact error stringDM_GWPipeline_Gateway_MashupDataAccessErrorPower BI gateway log file->
Affected OS build rangeWindows 11 23H2
Registry key involvedHKLM\SOFTWARE\Microsoft\DataGateway\ConfigurationsRegistry Editor->
Relevant service URLhttps://api.powerbi.com/v1.0/myorg/gateways
Log line signatureGateway failed to access data source due to insufficient permissions or invalid credentials.Power BI gateway log file->

Log Files to Check

What This Error Actually Means

The error code DM_GWPipeline_Gateway_MashupDataAccessError is raised by Microsoft's Power BI Gateway when there are issues accessing the on-premises data source due to insufficient permissions or invalid credentials stored in the gateway configuration. This error occurs during the refresh process of a dataset connected to an on-premises SQL Server or Analysis Services, indicating that the service account used by the gateway does not have sufficient read permissions on the target database or the stored credentials are outdated.

Affected Versions and Scope

This issue is observed in Power BI Gateway running on Windows 11 build 23H2. It affects datasets connected to SQL Server, Analysis Services, and other on-premises data sources that require a gateway for connectivity. The error does not occur when refreshing datasets connected directly to cloud-based services such as Azure SQL Database or Azure Synapse Analytics.

Where To Look First: Logs and Event IDs

To diagnose this issue, you should first examine the Power BI Gateway logs located at C:\ProgramData\Microsoft\Data Connectivity Gateway\Logs\Gateway.log and C:\ProgramData\Microsoft\Data Connectivity Gateway\Logs\GatewaySetup.log. Look for log entries that contain the exact string "DM_GWPipeline_Gateway_MashupDataAccessError". Additionally, you can check the Event Viewer logs for events related to this error. Specific event IDs to look out for are 1024 and 1035.

Root Causes

Lack of Read Permissions on Data Source

This issue arises when the service account used by Power BI Gateway does not have sufficient read permissions on the target database. To diagnose this, you need to verify that the service account has been granted the db_datareader role on the SQL Server or Analysis Services instance.

Stale Data Source Credentials in Gateway Configuration

Another common cause is when the credentials stored within the Power BI gateway configuration are outdated. This can happen if the password for the service account has been changed without updating it in the gateway settings.

Incorrect Service Account Configuration

Sometimes, the issue might be due to an incorrect configuration of the service account used by the Power BI Gateway. Ensure that the correct service account is specified and that its credentials are up-to-date.

Fix Procedure

  1. Verify Service Account Permissions: Use SQL Server Management Studio (SSMS) or a similar tool to verify that the gateway's service account has been granted the db_datareader role on the target database. If not, run the following T-SQL command:
          USE [YourDatabaseName];
          EXEC sp_addrolemember 'db_datareader', '';
        
  2. Re-enter Data Source Credentials: Navigate to the Power BI Service and re-enter the data source credentials in the gateway configuration. Go to Power BI admin portal > Gateway management, select your gateway, and click on "Manage" under the "Data sources" tab.
  3. Check Registry Configuration: Open the registry editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataGateway\Configurations. Ensure that the service account is correctly specified in this key. If necessary, update the configuration using PowerShell:
          Set-PowerBIGateway -ServiceAccount "" -Credential (Get-Credential)
        
  4. Restart Gateway Service: After making changes to the service account or credentials, restart the Power BI Gateway service to ensure that all updates are applied. You can do this via PowerShell:
          Restart-Service "PowerBIReportServerGateway"
        

Error Code Variants

Code Description Distinguishing Features
DM_GWPipeline_Gateway_MashupDataAccessError Lack of read permissions or invalid credentials. Log entries indicate insufficient permissions or outdated credentials.
DM_GWPipeline_Gateway_ConnectionFailed Connection failure to data source. Error occurs during the initial connection attempt, not related to permissions or credentials.
DM_GWPipeline_Gateway_DataLoadError Data loading issues due to schema mismatch or unsupported features. Error messages indicate specific data type mismatches or unsupported database features.

Verification

To verify that the issue has been resolved, monitor the Power BI Gateway logs for successful refresh attempts. Look for log entries indicating a successful connection and data retrieval from the on-premises data source. Additionally, check the Power BI admin portal under Tenant settings > Refresh history to ensure that dataset refreshes are completing successfully without errors.

Prevention

To prevent recurrence of this issue, establish a policy for regular review and update of service account credentials in the Power BI Gateway configuration. Additionally, implement an automated process to check and grant db_datareader permissions on new databases or when database schemas change.
Be cautious when modifying registry keys as incorrect changes can break enrolled devices.
Use the PowerShell cmdlet Get-PowerBIGatewayDataSource | Select-Object Name,ConnectionDetails,CredentialType to quickly review and validate data source configurations in the Power BI Gateway.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.