Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

PowerBI Desktop Publish Hangs

The previous version and the new October version of PowerBI desktop hangs when publishing reports to the Power BI portal. The report gets published sucessfully but the "Publishing to Power BI" dialog never finishes. Clicking on cancel or close on the dialog does nothing. The only way to get out of PowerBI desktop is to use task manger and kill the PowerBI process.

 

It is like PowerBI desktop gets stuck and the portal doesn't tell it the report and dataset is done publishing.

Status: Needs Info
Comments
kdelosh
Frequent Visitor

Another User here.  Reporting the same issue as above.  My file size is small <600k.

 

I publish to the service and Power BI desktop hangs and I never receive the "Successfully Published" notice.  I have to use the task manager to close down the Power BI service.  

 

I did go to the Power BI service and see that my changes were accepted, ie accurately published my report; however, it is very disconcerting as their is now doubt about what happened during the publish process.

 

 

Is there any logfile capture I can enable to record what is happening so I could aid in getting this issue closed?

 

Regards,

 

Kerry

mike_honey
Memorable Member

I'm striking the same behaviour on multiple machines, with multiple reports.

Anonymous
Not applicable

Just as a follow up with some additional information, we're working with Microsoft to get this resolved. We have noted:

 

- this issue does NOT occur with the April 2018 release, but started when we update to May 2018 release

 

- if I'm not on our corporate network, publishing works fine - even for the exact same file on the exact same machine. Through wireshark traces, we believe that it may (???) have something to do with connection reset acknowledgement messages and our proxy server. Sorry I'm just a parrot here, no idea what that means, but maybe useful to others.

 

Thanks,

Scott

Anonymous
Not applicable

Kerry - you can turn on diagnostics logging in Power BI desktop by going to Options and Settings / Options / Diagnostics / Enable tracing. Then click on the "open crash dump / traces folder" link to see where the files are actually being written.

 

Thx,

Scott

mike_honey
Memorable Member

@Anonymous thanks for the extra info Scott.  I've observed the same connection to the May 2018 update.  It's also only occurring in corporate environments with a proxy server.

Anonymous
Not applicable

Just as an update, the June 2018 release does not fix this issue. I'm still engaged with MS support...but we may need to roll back to the April version if this isn't resolved pretty quickly. I'll post updates as I get anything.

 

Thanks,

Scott

mike_honey
Memorable Member

I hesitate to present this as it is a bit farcical, but I do have a workaround:

 

1. Publish from Power BI Desktop

2. watch for your network traffic to stop in Task Manager

3. open the report in the web service and see if it has changed. 

4. Refresh and keep watching some more ...

5. If the publish actually worked (seems to usually) use Task Manager to kill Power BI Desktop.

6. shake your head and mutter hmmmmnnnn ...

Anonymous
Not applicable

Hi Mike - essentially I'm doing every step you listed except step #2. I wait for the report to show up in the Power BI cloud, and then kill the process.

 

But that's not something I can reasonably expect our users to do - especially since this will be our initial roll out of the service. If I give them a bad impression like this we'll never win them back. Also complicating this is the fact that about 1 time out of 3, when I do this, the "publish" link no longer works properly when I restart Power BI. In that case, I have to do a full reboot to make it work again.

 

😞

 

Scott

TDR
Regular Visitor

Same is happening to me. It happens to all reports.

The only solution is to kill Power BI after a while, reports are working well after publishing.

With me the behaviour was introduced with the May 2018 update, June 2018 update did not resolve the issue!

Anonymous
Not applicable
Adding to the woes, I too faced the issue many a time in last couple of months