Can't publish - Object reference not set to an instance of an object

[rkcasey]

I have a couple of reports that I update monthly and then publish and share the dashboard. No major changes this month - mostly data and filters. Everything looks totally cool in Desktop. However, when I tried to publish them both I got an error message Object reference not set to an instance of an object. I did not get to the usual - you already have a report with this name do you want to replace. Everything on PowerBI.com looks normal.

I am on the 365 Pro trial.  Any thoughts? THANKS

[hermesgoddess]

I also get this error. But the proposed solution is not working for me. I still get the same error if I go through the File->Publish route. I am also on Power BI Pro Trial. However, I get past the "You already have a report with this name do you want to replace" step. Please help. 

I normally update my report daily. I was out of the office for a few days and did not update since Jul 11, 2017, which published fine. 

[BKnecht]

I am getting the same error when trying to do the same thing. I also just made sure to update PowerBI desktop to. Publishing through File --> Publish did not work either. This is frustruating.

[rkcasey · Accepted solution]

Update - it appears that this ONLY is an issue if you use the publish button on the HOME ribbon - if you choose the publish option from file tab it works fine.

[KrisW]

Now 1-Feb-2018 (over 6 mo later) & *still* an issue!

When does a bug become a feature? When the developers finally remove the PUBLISH/SHARE option from the menu ribbon or simply pop up w/ a message (when button pushed) - "Sorry, we cannot be bothered &/or cannot figure this error out. Use FILE - PUBLISH option instead."

[syedgj]

---

wrote:

Update - it appears that this ONLY is an issue if you use the publish button on the HOME ribbon - if you choose the publish option from file tab it works fine.

---

This actually helped. Home button still doesn't work but at least I can publish through File.

[KrisW]

Glad to find this solution, but when will it be fixed? This just happened to me this morning.

Version: 2.53.4954.481 64-bit (December, 2017)