Forum Discussion
Resolver IIRefresh error "end of buffer" for some reports
Hi all,
two of my reports aren't refreshing at the moment and i'm getting the following error:
the reference table is a dataflow in the service. manual refresh from within the desktop runs just fine.
I found some topics suggesting to emtpy the cache in the desktop, did that
Deleting and republishing could help, did that
Checked the dataflow itself for errors en refresh it manually from within the service, did that
And still i'm getting the above message.
Can anyone provide some more tips on how to resolve this?
FYI all other reports and dataflows are running just fine.
Thanks!
we're on Pro lincenses, i was hoping to find the smoking bullet on the forum but perhaps a ticket is the better way to go.
Thanks.
so a quick update for those running into the same issues, perhaps this helps.
I raised a support ticket and got the problem solved.
During debugging we found that the semantic model saved to service requires a connetion to either a on premises dataway or a cloud connection. This part was obvious and known.
However when a new cloud connection was created, I couldn't hit the apply button. I had to select a connection to a on premises dataway, then re-select the cloud connection, and then I was able to save the link.
After splitting m queries, publishing and other attempts, this seemed to be what was going wrong on my side.
5 Replies
- lbendlin
Super User
If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi - otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues .
PaulusDwe're on Pro lincenses, i was hoping to find the smoking bullet on the forum but perhaps a ticket is the better way to go.
Thanks.
- PaulusD
so a quick update for those running into the same issues, perhaps this helps.
I raised a support ticket and got the problem solved.
During debugging we found that the semantic model saved to service requires a connetion to either a on premises dataway or a cloud connection. This part was obvious and known.
However when a new cloud connection was created, I couldn't hit the apply button. I had to select a connection to a on premises dataway, then re-select the cloud connection, and then I was able to save the link.
After splitting m queries, publishing and other attempts, this seemed to be what was going wrong on my side.
- lbendlin
As a word of warning - Do not merge queries in Power Query. Absolutely do not merge queries that come from an on-premise data source and a cloud data source. Because if you do that your cloud data source will now also need a gateway. And once you go down that rat hole of creating a gateway connection for your cloud data source you will never ever be able to switch that off again.
- PaulusD
any idea on what happens when you do this?
i think we haven't done this yet, hope i'm right. mostly using cloud sources as dim tables with relations.
merging in power query makes refreshing super slow as well is my experience.
