Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes! Register now.
We have published incremental refresh report to Power BI service with Embed A4 capacity.
Report data source connection failing intermittently with error couldn't retrieve the data for this visual and cross marks.
In Power BI service, we can see below error,
"unable to connect to the data source 0cab5b3c-6305-48b8-9dbd-9b3cd3d9d0e5 . either the data source is inaccessible, a connection timeout occurred, or the data source credentials are invalid only " on power bi service
data Gateway logs showing below error,
1.
GatewayPipelineErrorCode=DM_GWPipeline_Gateway_MashupDataAccessError
GatewayVersion=
Reason= --->
[1]Microsoft.PowerBI.DataMovement.Pipeline.Diagnostics.GatewayPipelineWrapperException: Substituted: MashupValueException:<ccon>Microsoft.Data.Mashup.MashupValueException (0x80004005): PostgreSQL: Exception while reading from stream
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.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessorUtils.MashupExecuteReaderAsync(DbCommand command, ExecuteQueryRequest queryRequest, Guid activityId)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessorUtils.ExecuteReaderAsync(DbCommand command, ExecuteQueryRequest queryRequest, Guid activityId)
at Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.GatewayProcessor.<>c__DisplayClass4_3.<<ExecuteAdoQueryAsync>b__3>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
2.
GatewayPipelineErrorCode=DM_GWPipeline_UnknownError
GatewayVersion=
InnerType=MashupException
InnerMessage=<ccon>The command has been canceled.</ccon>
InnerToString=<ccon>Microsoft.Data.Mashup.MashupException (0x80004005): The command has been canceled.
3.
<ccon>Microsoft.Data.Mashup.MashupValueException (0x80004005): An error happened while reading data from the provider: 'Connection is not open'
Please help on this issue.
Thank you in advance.
Hi @balajiratnala6,
Based on the error messages provided, it appears that there is an issue with the data source connection or the credentials being used to connect to the data source. Here are some steps you can take to troubleshoot the issue:
Check the data source connection: Verify that the data source is accessible and that the connection string used to connect to the data source is correct. You can test the connection by connecting to the data source from the computer where the Power BI Gateway is installed.
Check the data source credentials: Verify that the credentials used to connect to the data source are valid and have not expired. If the credentials have expired, update them and test the connection again.
Check the Power BI Gateway logs: Review the logs to identify any specific errors or issues that may be causing the connection to fail. The error messages you provided suggest that there may be an issue with the Mashup engine or a cancellation of the command. You may need to consult with a technical expert to help you troubleshoot these issues.
Check for updates: Ensure that you are running the latest version of Power BI Gateway, as updates may include bug fixes and improvements that can help resolve connection issues.
Review network connectivity: Verify that there are no network issues that could be impacting the connection between the Power BI Gateway and the data source.
If none of these steps resolve the issue, you may need to reach out to Microsoft Support for further assistance.
Best regards,
Isaac Chavarria
If this post helps, then please consider Accepting it as the solution and give Kudos to help the other members find it more quickly