Forum Discussion
Refresh does nothing after Preparing to refresh
Hi , Anonymous ;
You could try to reduce the size of the data source and then refresh to test whether it is related to the size of the data source. Secondly, you can refer to the following two articles.
https://medium.datadriveninvestor.com/my-dataset-is-taking-too-long-to-refresh-843fd8fd4a51
Best Regards,
Community Support Team_ Yalan Wu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Yalan,
I am facung this same issue now. I have tried this at least five times, and each time it shows the "Preparing for refresh" message pop-up for 5-6 seconds. I don't see this pop-up in my other work where we have successful refreshes. The dataset itself never shows the busy circle cursor that we normally see for good datasets. After all of these attempts, the Refresh History > Scheduled tab is still empty - no indication of an attempt.
My dataset is very small. PBIX is 57K, one table, 4 rows - all set up for testing. I just published this report and configured it to use ODBC through our Enterprise gateway to connect to Azure HDInsight. We are trying other connections for future use, but for the short term, we need to have this working with ODBC.
My main concern overall is that, regardless of whatever problems there might be with the data source and the connector... why doesn't Power BI log an attempt to refresh? I would consider this a bug, and would ask that each time a refresh request is registered, an audit entry should be logged, and an error message of some sort should be recorded when failing.
Regards,
Tom
Hi Tom,
With your comment, I realized I didn't post what helped for us. After some careful debugging and some tests, we realized that the issue happened when multiple people tried to refresh at the same time (this wasn't easy to replicate and didn't happen all the time that we tried, so I couldn't tell for sure if this was the only reason for this to happen). For some reason that concurrent refresh attempts created a backlog of 2-3 refreshes one right after the next and blocked any further refreshing with the behavior mentioned in my original question.
What we did to numb the issue, was to ask the team to be more conscious about the refreshing and to communicate between themselves when they were going to try and refresh (sometimes they did it in less than 30 seconds after the refresh finshed).
I do agree that that is a bug and some kind of error message or failed attempt should be logged somewhere.
Hope this helps,
Jose.