Not able to refresh power bi dataset

[Anonymous]

Hi All,

Need some quick help. I have a dataset and some reports connected to the same. From last couple of days, I am not able to refresh that particular dataset manually and even my scheduled refresh are not working. It gives an "Internal Service Error".

So I am trying to publish the same dataset through Power BI desktop, however it is taking ages to publish it and it doesn't even go through in the end. I am able to rename the file and publish it to the same workspace but just not able to replace the existing dataset.

So currently I am stuck wherein I can't refresh my report on Power BI service as well as I can't publish it through desktop.

Not too sure what the issue is but really need a quick fix on it due to the business requirements. Any help is greatly appreciated.

Note: I do not want to delete the dataset and then publish it as a new one, because that will change the link to the reports for the users and even I will have to connect the dataset again to all my existing reports

[GilbertQ]

Hi @Anonymous 

What happens when you try and refresh it in the Power BI Service?

[Anonymous]

It gives an Internal service Error. Firstly it doesn't even show me that it is refreshing and then after sometime it shows out that red marker. Then upon checking into refresh history I see the mentioned error. Not too sure if this is due to the latest updates but it is surely frustrating.

[GilbertQ]

Hi @Anonymous 

Can you install the latest version of Power BI Desktop, then open make a change, save this and then try and upload again?

has anything changed with the existing report?

[Anonymous]

Also to add, when I allow the desktop file to publish for a long time, it shows me the below message,

'Publishing is complete. However, we couldn't refresh your dataset. Please manually refresh your dataset in the service or schedule refresh.'

[Anonymous]

I have already installed the latest version. Trying to publish from the same but still giving the same error. 

No I didn't change anything in the report. In fact the report was on schedule refresh when the issue first started.