Forum Discussion
SAP BW timeout option, runtime errorcode 2147467259
thanks for the blog, but the attached pbix file does not work. I get a lot of errors inside the query.
I will try to get a support ticket.
I opened a support ticket, this is the answer I got:
Contacted the Product team and below is the update form the Product team
In the case posted to the forums, this means that their server ran out of memory while running the query. That’s a limitation on the server side. They may be able to overcome this by running more and then combining the data locally.
DataSource.Error: SAP Business Warehouse: RfcInvoke failed(RFC_ABAP_RUNTIME_FAILURE): TSV_TNEW_PAGE_ALLOC_FAILED
But I don´t think this is correct...
When I loaded the cube using another BI program, it loads the whole cube.
If I use Direct Query, Power BI is able to load the whole cube, but than the user interface is a lot more limited (cannot view data, relationships, cannot load more data on the same project).
Power BI somehow can only import 5 months of data (not direct query, import mode).
I know Power BI will convert the cube view to tabular view, but will this occur inside the SAP BW server? Is this the reason for the error?
This simple question was not answered by the ticket guy.
I'm with the same problem. Someone discover the cause? Is it a Power BI limitation?
I am also receiving the same issue! I think it's the way Power BI is calling the data or something that is maxing out our memory in SAP BW since I could see the entire InfoProvider when I looked at it in BEx Analyzer. Has anyone come up with a solution or work around?
Thanks,
no... so far, the best option is to adjust SAP BW in small cubes, this way the conversion is faster and does not run out of available memory and resources.
or use direct query in Power BI, but then you can only create measures. you cannot se data or relationship.
Thank you DN for such a quick response! I'll let you know if I figure out a solution.
In direct query mode, it doesn't load the whole cube, but it do many small request with few axes, one by graph or visualisation.
Same thing with analysis for office for exemple.
In import mode, it try to load one big set of data with many axes so it use a lot more memory on SAP application server side.
I think it's not a Power BI bug or a bad SAP configuration but more a concept weakness. Responsiveness of import mode come at a price...
We are having the same problem in my company.
Is there any update on this topic? There have been some fixes implemented?
Kind Regards
