Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Dataflows type data source is working fine but regularly this error comes up. When I re-authenticate the data source, it starts working again. This error comes up about once in few weeks.
First thing - why there is no message coming from Gateway data source to it's owners, that there is a problem? There should be an email message or some notification about this problem so that you could go and fix it. Now you don't know there is an error, when datasets are not refreshing. This is too late and it is not looking good for customer.
Then the actual error. It is only concerning the PowerPlatform Dataflows type data source. Authentication is done using generic account used by all Power BI main users. There is no MFA in use.
Error message is:
"PrimaryGatewayMemberName": Received error payload from gateway service with ID 1764825: Missing or invalid credentials for data source. Reason = 'AccessForbidden', DataSource = '<ccon>[ccon]PowerBI/PowerBI[/ccon]</ccon>', DataSourceReference = '', DataSourceOrigin = '<ccon>[ccon]Web/https://api.powerbi.com/powerbi/globalservice/v201606/clusterdetails[/ccon]</ccon>', DataSourceReferenceOrigin = '', InnerExceptionMessage = '<ccon>inner exception message 0: The credentials provided for the PowerBI source are invalid. (Source at PowerBI.), inner exception stacktrace 0: at Microsoft.Data.Mashup.ProviderCommon.MashupResource.<>c__DisplayClass47_2`1.<StartEvaluationAndGetResultSource>b__0()
at Microsoft.Mashup.Security.Impersonation.RunAsProcessUser[T](Func`1 func)
at Microsoft.Data.Mashup.MashupCommand.EvaluateAndGetSource[T](String commandText, CommandType commandType, Int32 commandTimeout, MashupParameterCollection parameters, String resultTransform, Boolean forColumnInfo, Boolean executeAction)
at Microsoft.Data.Mashup.MashupCommand.ExecuteReader(CommandBehavior commandBehavior, MashupCommandBehavior mashupCommandBehavior)
at Microsoft.Data.Mashup.MashupCommand.ExecuteReader()
at Microsoft.Data.Mashup.DataSourceReference.TestConnection(String connectionString)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.GatewayDataAccessMashupUtils.DSRTestConnectionAsync(String dsrJson, MashupCredential credential, Nullable`1 activityId, Int32 testConnectionTimeout, String[] exemptions, String containerPool)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.MashupOleDbConnectionProvider.<>c__DisplayClass7_0.<<TestConnectionAsyncImpl>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.MashupOleDbConnectionProvider.<TestConnectionAsyncImpl>d__7.MoveNext().
</ccon>'..
"SecondaryGatewayMemberName": Received error payload from gateway service with ID 2820840: Missing or invalid credentials for data source. Reason = 'AccessForbidden', DataSource = '<ccon>[ccon]PowerBI/PowerBI[/ccon]</ccon>', DataSourceReference = '', DataSourceOrigin = '<ccon>[ccon]Web/https://api.powerbi.com/powerbi/globalservice/v201606/clusterdetails[/ccon]</ccon>', DataSourceReferenceOrigin = '', InnerExceptionMessage = '<ccon>inner exception message 0: The credentials provided for the PowerBI source are invalid. (Source at PowerBI.), inner exception stacktrace 0: at Microsoft.Data.Mashup.ProviderCommon.MashupResource.<>c__DisplayClass47_2`1.<StartEvaluationAndGetResultSource>b__0()
at Microsoft.Mashup.Security.Impersonation.RunAsProcessUser[T](Func`1 func)
at Microsoft.Data.Mashup.MashupCommand.EvaluateAndGetSource[T](String commandText, CommandType commandType, Int32 commandTimeout, MashupParameterCollection parameters, String resultTransform, Boolean forColumnInfo, Boolean executeAction)
at Microsoft.Data.Mashup.MashupCommand.ExecuteReader(CommandBehavior commandBehavior, MashupCommandBehavior mashupCommandBehavior)
at Microsoft.Data.Mashup.MashupCommand.ExecuteReader()
at Microsoft.Data.Mashup.DataSourceReference.TestConnection(String connectionString)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.GatewayDataAccessMashupUtils.DSRTestConnectionAsync(String dsrJson, MashupCredential credential, Nullable`1 activityId, Int32 testConnectionTimeout, String[] exemptions, String containerPool)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.MashupOleDbConnectionProvider.<>c__DisplayClass7_0.<<TestConnectionAsyncImpl>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayDataAccess.MashupOleDbConnectionProvider.<TestConnectionAsyncImpl>d__7.MoveNext().
</ccon>'..
Hi @MiraNi ,
I also see the issue you encountered as a convenient feature we should have in data governance. For now, I purchased Power Automate license to track those key Dataflow that failed to refresh.
Believe it or not, Power Automate license really contributing more than just setting up alert. And hopefully that you could try it out.
Hi,
do you have an explanation, why this is happening? And if this is "an expected feature", I would like to know in advance, if a key needs re-authentication instead of noticing it when the refresh failes.
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
37 | |
30 | |
18 | |
14 | |
8 |
User | Count |
---|---|
50 | |
39 | |
32 | |
15 | |
13 |