Being signed out on publish on newest version desktop

[SharonHMA]

I recently downloaded the newest version of PowerBI.  

Now when I publish I am being asked to sign in even though I already was.  The signin box pops up but you can't fill it in because powerBI says it's 'working'. Only solution is to use the task manager to close PowerBI and use auto recovery if you haven't saved first which is annoying. Re-open, sign-in & save then you can publish.

I've checked at the top right before hitting publish and it says my name so I should be signed in. This happens after you have been working for a while. If you sign in, publish immediately all is fine.  Never had this problem before.

This is happening on two different PC's, both updated.

Is anyone experiencing a similar issue?

[v-yuezhe-msft · Accepted solution]

Hi @SharonHMA @ShaneC @Anonymous,

A new version of Power BI Desktop has been released, please download it from the following link, and the issue should be fixed in this version.

https://www.microsoft.com/en-us/download/details.aspx?id=45331

Thanks,
Lydia Zhang

[Anonymous]

Hi,

I'm now getting a similar error/problem with the latest version, all other Office Apps are working fine, it's just Power BI and my administrator can't find anything wrong. This only signs me out when I try to publish and I can't sign in again without a reboot:

Error

An error occurred

An error occurred. Contact your administrator for more information.

Error details

• Activity ID: 4ea02e47-645f-4f1a-8ed3-96af5fc4bb07
• Relying party: Microsoft Office 365 Identity Platform
• Error time: Fri, 03 Mar 2017 12:28:53 GMT
• Cookie: enabled
• User agent string: Mozilla/5.0 (Windows NT 6.1; Win64; x64; Trident/7.0; rv:11.0) like Gecko

I start off logged into my Office account and as soon as I publish, it generates this error. The only fix seems to be a reboot of the laptop, after which I can login fine for an hour or two before this happens again. There's no way to send a frown on this screen.

[v-yuezhe-msft · Accepted solution]

Hi @SharonHMA @ShaneC @Anonymous,

A new version of Power BI Desktop has been released, please download it from the following link, and the issue should be fixed in this version.

https://www.microsoft.com/en-us/download/details.aspx?id=45331

Thanks,
Lydia Zhang

[ShaneC · Accepted solution]

Thanks, did a quick test and the issues seems to be resolved.

Regards

Shane

[SharonHMA]

Yes everything is working!  Wonderful thanks.

[v-yuezhe-msft]

Hi @SharonHMA @ShaneC @Anonymous,

We have reported the issue internally. I will post back once I get any updates.

You can also check the following similar issues.
http://community.powerbi.com/t5/Issues/Publish-Report-Error-if-Not-Signed-In/idi-p/113197
http://community.powerbi.com/t5/Issues/Power-BI-Desktop-January-2017-Login-popup-blocked/idi-p/113292

Thanks,
Lydia Zhang

[SharonHMA]

Thanks Lydia - I'm sure it will get fixed in the next update.  Still loving PowerBI 🙂

[Anonymous]

aaahhh yes!  It is horrible since when I go to publish it then hangs and i have to Ctrl+alt+Delete.  The good news is that it does SAVE when it gets hung.  It is trying to publish, but then in the background it requests my sign in, but it wont let me click on that window since it things it is publishing.  Some sort of logic error.

[ShaneC]

I get the same error. Even when I am signed in. To get around this issue...

1. I first logout

2. Then login again

3. Then publish

But still, very frustrating!!!

Shane

[SharonHMA]

Yes. It's been happening to me for days now.  You can publish a few times in a row, but if you don't publish for about 30 minutes it seems to sign you out. My solution is to close & resign in before publishing if I've been working in desktop for a while.

[parry2k]

Hey @SharonHMA,

Thanks for posting this, infect I expereience this today after most recent upgrade, I cannot say if that is an issue becuase I came across this one but it is for sure was never an issue before. Also to resolve, I did exactly what you mentioned.

Let's what others have to say. Also I will keep posted in case I expereience the issue again.