Forum Discussion
Problems publishing updates from desktop
Not sure what is causing this but signing out of P BI Desktop and back in has let me publish updates again.
Something is wrong somewhere along the line so hoefully will be fixed soon but in the meantime a simple workaround.
Solution was found in this thread:
Hi Charlie.
Thanks for the reply.
I am using the latest version, albeit the 32 bit version - Version: 2.41.4581.361 32-bit (November 2016)
(my employers are yet to embrace the joys of a 64bit OS!)
I stopped getting the error yesterday and publishing has been working fine until this afternoon when i have again started getting the same serror.
I have just noticed on the service, at the side of one of my datasets that I am trying to update, there is an error icon that shows this when i click on it:
I am not using a gateway and to my understanding i don't need one as my datasets are all just standard Excel tables.
Could this be affecting it?
I now have a colleague who has the same problem
Not sure what is causing this but signing out of P BI Desktop and back in has let me publish updates again.
Something is wrong somewhere along the line so hoefully will be fixed soon but in the meantime a simple workaround.
Solution was found in this thread:
I just experienced this issue. I just installed the Jan 2017 PBI Desktop update today but I am pretty sure I published at least once successfully since then. The *only* thing I changed in the .pbix was to enable wordwrap in some table columns so maybe that was not enough of a change? I do not want to delete the dataset that has already been published just in case the problem persists even after I delete it. I did try closing PBI Desktop & signing out of the service--that did not solve the problem for me.
This is much like when I sometimes republish a .pbix file and when I go to update the content pack PBI does not recognize/flag the content pack as needing to be republished. So I have to edit the title/description to force PBI to enable the Update button for the content pack. Grrr...
Update: I was able to signout, sign in and publish. I continued to experience the issue with other reports and signing out was the solution. Fingers crossed that MSFT is on it.
