Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Cannot refresh report

Today I got this issue when trying to refresh report (including demain and schedule) 

 

{"error":{"code":"DM_GWPipeline_Gateway_SpooledOperationMissing","pbi.error":{"code":"DM_GWPipeline_Gateway_SpooledOperationMissing","parameters":{},"details":[],"exceptionCulprit":1}}}

 

{"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":"We're sorry, an error occurred during evaluation."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}}]}}}

 

{"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":"Microsoft SQL: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - The wait operation timed out.)"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Class","detail":{"type":1,"value":"20"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"SQL"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"<ip>.....</ip>,...;....."}},{"code":"Microsoft.Data.Mashup.ValueError.ErrorCode","detail":{"type":1,"value":"-2146232060"}},{"code":"Microsoft.Data.Mashup.ValueError.Message","detail":{"type":1,"value":"A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - The wait operation timed out.)"}},{"code":"Microsoft.Data.Mashup.ValueError.Number","detail":{"type":1,"value":"258"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}}

Status: Investigating

Hi @tannhq ,

According to the error message, do you use Azure SQL as data source? If so, please check if the setting "Allow Azure services and resource to access the server" is set to YES in Azure.

vyanjiangmsft_1-1682057532901.png

If it doesn't help, does this error occur on a specific scheduled time? During the refresh failure time, is the database at high utilization? If so, you may consider scaling up your SQL Azure instance to add more resources to it. See Scale resources - Azure SQL Database | Microsoft Docs

 

Another operation you could try is to restart your SQL Azure instance. You can simply scale the database to another tier and then scale it back. When scaling, it would restart database engine process. Sometimes restarting will solve some DB issues. See SQL SERVER - How to Restart SQL Azure Database? - SQL Authority with Pinal Dave

 

Best regards,

Community Support Team_yanjiang

 

 

Comments
v-yanjiang-msft
Community Support
Status changed to: Investigating

Hi @tannhq ,

According to the error message, do you use Azure SQL as data source? If so, please check if the setting "Allow Azure services and resource to access the server" is set to YES in Azure.

vyanjiangmsft_1-1682057532901.png

If it doesn't help, does this error occur on a specific scheduled time? During the refresh failure time, is the database at high utilization? If so, you may consider scaling up your SQL Azure instance to add more resources to it. See Scale resources - Azure SQL Database | Microsoft Docs

 

Another operation you could try is to restart your SQL Azure instance. You can simply scale the database to another tier and then scale it back. When scaling, it would restart database engine process. Sometimes restarting will solve some DB issues. See SQL SERVER - How to Restart SQL Azure Database? - SQL Authority with Pinal Dave

 

Best regards,

Community Support Team_yanjiang