Forum Discussion
HUGE problem when publishing a report
hi
i have a dashboard that a live report is pinned to it.
i update the report very often, and then publish in the same name so the dashboard is updating automatically.
suddenly today when i tried to publish it takes a l-o-t of time!
i published with the same gateweay and DB other reports and there was no problem
after loading it writes a a "bad request" error or "publishing faile for unknown reason"
and the strangest thing is that the report on the service is sometimes show report from a lot of time (i don't even saved it on my account or my computer) and sometimes it shows the relevant report...
do you know this issue? it's a very bad one.
thanks... hopeless
23 Replies
I'm getting the exact same thing.
This is a showstopper -just walked my senior leadership through a report this morning and they asked me to send them the dashboard. Not going to send a thing if the service is failing to finish a publish or a full report load.
The bad part is, PowerBi's service level is rated at 'Green' right now, which I don't think is actually the case.
Tried to open up a support case and attach a screenshot of the error and the attachment service was reported as not responding. I'm guessing Microsoft is having server challenges today?
When was the last time you updated your gateway? I only ask because it was stated that it was the same gateway. In the past, I have noticed that there are times when the Service update will not play nice with a different version of the Gateway. I would recommend updating the gateway and the desktop PowerBI version. Then, republish the report and see if that speeds things back up.
This is not the issue unfortunately.
I found a workaround and it's not ideal, especially if this could happen repeatedly. Something about updating my dataset online is broken (though not locally). My old report times out on reading some of the data.
In order to have a correctly working report, I had to do a 'save-as', rename it, and publish a new report. If I've already shared the old broken report with coworkers, I now have two reports and one of them is no longer 'live'. That's not how this is supposed to work.
I'm going to give it a little more time before assuming this is not a server/service issue on Microsoft's end.
