Skip to main content

Issues

New

Invalid Credentials on Scheduled Refresh for Project Online Dataset oath mode

Vote (9) Share
's profile image

on 27 Dec 2016 19:32:39

I have created a Report using Project Online Odata Source long back ago, It was working fine till last week. But now , the data set is not getting refreshing and though I have updated with my valid credentials it is throwing an error saying that "Failed to update data source credentials.". I'm facing this issue from last 2-3 days.

Comments (11)
's profile image Profile Picture

Power BI User on 05 Jul 2020 22:41:13

RE: Invalid Credentials on Scheduled Refresh for Project Online Dataset oath mode

I am still encountering this issue when trying to update the OAuth2 settings to schedule automatic refreshes from SharePoint Online spreadsheets.

's profile image Profile Picture

Rajkumar on 05 Jul 2020 22:38:18

RE: Invalid Credentials on Scheduled Refresh for Project Online Dataset oath mode

Hey Treb,

Though we provide valid O365 credentials to the data source it is taking too long time. However, it is not accepting the credentials.

Today we are getting one more issue Is that the reports are taking too long time to open in the Power BI Site. when I click on the report name it is saying "Loading ... , Almost done.." after 2-3 minutes of waiting the report is opening.

My team is very afraid of Power BI, as we are very close to start Project Online, Power Bi Go-Live but facing these kind of issues at the last minute. Please investigate & provide some fix for this at the earliest.

's profile image Profile Picture

Juan Carlos on 05 Jul 2020 22:38:16

RE: Invalid Credentials on Scheduled Refresh for Project Online Dataset oath mode

Same issue for me... not the only one with related problem, see discussion: http://community.powerbi.com/t5/Service/Data-source-credentials-hangs-on-refresh/m-p/113864#U113864

's profile image Profile Picture

Oleksiy Prosnitskyy on 05 Jul 2020 22:37:32

RE: Invalid Credentials on Scheduled Refresh for Project Online Dataset oath mode

'+1

's profile image Profile Picture

Treb Gatte, Microsoft MVP on 05 Jul 2020 22:37:32

RE: Invalid Credentials on Scheduled Refresh for Project Online Dataset oath mode

Ok, reading this a second time. I'd republish the model as there have been changes in recent updates.

's profile image Profile Picture

Ben Howard on 05 Jul 2020 22:37:31

RE: Invalid Credentials on Scheduled Refresh for Project Online Dataset oath mode

I'm afraid that didn't work for me Treb. I just get "Failed to update data source credentials"

's profile image Profile Picture

Treb Gatte, Microsoft MVP on 05 Jul 2020 22:37:31

RE: Invalid Credentials on Scheduled Refresh for Project Online Dataset oath mode

On first publish, the data source credentials are stripped and the authentication reverts back to Anonymous. This is by design security feature though at this early hour, the specific need escapes me.

To fix
• Expand the hamburger menu to expose your dashboards, reports and data sets
• Hover over the data set to expose the ellipsis menu
• Click Scheduled Refresh
• When the page comes up, it should prompt you to edit your credentials
• Click the link to edit credentials
• Change from Anonymous to OAuth2
• Enter O365 credentials and click OK
• Everything should work now.

's profile image Profile Picture

Aracelli Manrique on 05 Jul 2020 22:37:19

RE: Invalid Credentials on Scheduled Refresh for Project Online Dataset oath mode

I have the same issue

's profile image Profile Picture

Power BI User on 05 Jul 2020 22:37:03

RE: Invalid Credentials on Scheduled Refresh for Project Online Dataset oath mode

Same Issue here also.. Could you please provide a solution as soon as possible.

's profile image Profile Picture

Power BI User on 05 Jul 2020 22:37:02

RE: Invalid Credentials on Scheduled Refresh for Project Online Dataset oath mode

Facing the same issue, Dont know whats the wrong. It was working fine earlier, we are facing this issue since last few days. Microsoft team could you please look into this issue at the earliest as it is a Go-Live blocker for us.