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

The ultimate Microsoft Fabric, Power BI, Azure AI & SQL learning event! Join us in Las Vegas from March 26-28, 2024. Use code MSCUST for a $100 discount. Register Now

Reply
Lorenz33
Helper III
Helper III

Cannot refresh a Power BI Report

We are running Power BI Report Server (January 2022). We have a Power BI report where the data source is a DB2 database. It imports approximately 5 GB of data. This report has been uploaded to our Power BI Report Server development environment. We set up the data source with Basic Authentication and it connects successfully. We then set up a scheduled refresh and it runs for 10 minutes and then fails with this error:

 

Data source error: Login failed for data source

[0] -33333333333: DataSource.Error: Microsoft Db2 Client: Processing was cancelled due to an interrupt. SQLSTATE=57014 SQLCODE=-952. DataSourceKind = DB2. DataSourcePath = BD33333;MyDB. Message = Processing was cancelled due to an interrupt. SQLSTATE=57014 SQLCODE=-952. ErrorCode = 0. . The exception was raised by the IDbCommand interface.

 

I increased the query timeout value from 1800 to 3600 seconds and it still fails. Please let me know what solutions are available to get this data refresh to finish successfully.

1 ACCEPTED SOLUTION

Hi @Lorenz33 ,

I am sorry that I cannot reproduce your situation. It seems to me that in Power Bi Service not need to be adjusted, if it is due to a timeout setting in Power BI Service, it will simply report an error timeout instead of Processing was cancelled due to an interrupt. Related link below, there are the same users who encountered the same problem If you have the same problem, you can refer to the linked solution to change the DB2 timeout or disable timouts:

https://www.toolbox.com/tech/data-management/question/sql0952n-processing-was-cancelled-due-to-an-in... 

https://stackoverflow.com/questions/11570439/db2-queries-get-occasional-sql0925n-processing-cancelle... 

https://www.ibm.com/mysupport/s/question/0D50z000060GOynCAG/error-57014-ibmdb2nt-sql0952n-processing... 

 

 

Best Regards

Lucien

 

View solution in original post

5 REPLIES 5
v-luwang-msft
Community Support
Community Support

Hi @Lorenz33 ,

If the application sets a query timeout value, it will stop the execution of the statement if it exceeds the timeout resulting in a SQL0952N error.

And details solution to resolve the problem,refer the following links:

https://www.ibm.com/support/pages/sql0952n-error-returned-long-running-sql-statement 

 

 

 

Did I answer your question? Mark my post as a solution!


Best Regards

Lucien

Thanks Lucien. The attached article looks very helpful. Does anything need to be done on the Power BI Report Server side? The article explains to increase the query timeout interval on the different application types. Within Power BI Report Server I went to site settings and under report timeout I changed the value to 3660 seconds from 1800 to allow the report to run before timing out. This would be one hour and the scheduled refresh fails after 10 minutes.

Hi @Lorenz33 ,

I am sorry that I cannot reproduce your situation. It seems to me that in Power Bi Service not need to be adjusted, if it is due to a timeout setting in Power BI Service, it will simply report an error timeout instead of Processing was cancelled due to an interrupt. Related link below, there are the same users who encountered the same problem If you have the same problem, you can refer to the linked solution to change the DB2 timeout or disable timouts:

https://www.toolbox.com/tech/data-management/question/sql0952n-processing-was-cancelled-due-to-an-in... 

https://stackoverflow.com/questions/11570439/db2-queries-get-occasional-sql0925n-processing-cancelle... 

https://www.ibm.com/mysupport/s/question/0D50z000060GOynCAG/error-57014-ibmdb2nt-sql0952n-processing... 

 

 

Best Regards

Lucien

 

d_gosbell
Super User
Super User

The part of the error that says "Processing was cancelled due to an interrupt" looks to me like it's probably coming from DB2. Have you talked to your DB2 DBAs to see if they can assist with this? It could be some sort of resource governing on the DB2 side of things

I spoke with the DB2 DBA and he said that there is no timeout value set up on the DB2 side and there is nothing in the DB2 logs related to the query being interupted or timing out.

Helpful resources

Announcements
Fabric Community Conference

Microsoft Fabric Community Conference

Join us at our first-ever Microsoft Fabric Community Conference, March 26-28, 2024 in Las Vegas with 100+ sessions by community experts and Microsoft engineering.

February 2024 Update Carousel

Power BI Monthly Update - February 2024

Check out the February 2024 Power BI update to learn about new features.

Fabric Career Hub

Microsoft Fabric Career Hub

Explore career paths and learn resources in Fabric.

Fabric Partner Community

Microsoft Fabric Partner Community

Engage with the Fabric engineering team, hear of product updates, business opportunities, and resources in the Fabric Partner Community.

Top Kudoed Authors