The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I have uploaded my Power BI file in Power BI Service (Power BI online) and the source of this file is Azure Sql database and for the credentials of this database in Power Service I have set virtual network data gateways.
So the problem is that refreshing of the dataset fails occasionally, means sometimes it refreshes with no problem and everything work fine but sometimes the refresh fails with the error below.
And one more thing is that data refreshing in Power BI Desktop (while creating the dashboard) is ok and has no problem.
{
"error":{
"code":"DM_GWPipeline_Gateway_MashupDataAccessError",
"pbi.error":{
"code":"DM_GWPipeline_Gateway_MashupDataAccessError",
"parameters":{
},
"details":[
{
"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode",
"detail":{
"type":1,
"value":"-2147467259"
}
},
{
"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage",
"detail":{
"type":1,
"value":"An error happened while reading data from the provider: 'Invalid operation. The connection is closed.'"
}
},
{
"code":"DM_ErrorDetailNameCode_UnderlyingHResult",
"detail":{
"type":1,
"value":"-2147467259"
}
},
{
"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind",
"detail":{
"type":1,
"value":"SQL"
}
},
{
"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath",
"detail":{
"type":1,
"value":"----------"
}
},
{
"code":"Microsoft.Data.Mashup.ValueError.Reason",
"detail":{
"type":1,
"value":"DataSource.Error"
}
}
],
"exceptionCulprit":1
}
}
} Table: ----------.
{The ---------- is private information}
Is your Azure database online all the time or maybe it is taken down during periods of no use and needs to be brought back up when a request comes in? You could do a "wakeup" refresh request followed by another request a short time later.
Another option is that one of your VNet gateway cluster members is either misconfigured or equally spotty with staying alive. Then you could explain the randomness by the way the load balancer is choosing cluster members.