Credentials Error on Refreshing

[AnujSikand]

I have a report/dashboard that has been published for about 4 - 5 months now without any changes, and the scheduled refresh was working fine. Suddenly last week, the report refuses to refresh. I get the following error:

"Credentials are required to connect to the SQL source"

I have entered the credentials and know they are correct, as i use the same credentials to refresh the desktop file without any issues

Its only this 1 specific report, i have other reports using the same connection to the same db, and don't experience this issue.

Has anyone come across this or know what may be causing it?

The report connects to Azure for the db

[freshroy]

I'm having same issues but with Quickbooks online.  I'm extremely disappointed.  This issue first came up in August and lasted about 1.5 months and was finally resolved.  Everything was working fine until 3 days ago when I started receiving the "invalid credentials" error again. I'm disappointed because I know now I can't rely on this tool; I have to go back to my client and tell them I can't deliver their promised reports.

[greggyb]

Make sure you submit this as a bug report, as well. You can do so in PBI Desktop by using the 'Send a frown' option in the File menu, and using the feedback menu in PBI Service.

The forums are a great avenue for discussing issues, sharing thoughts / ideas, and troubleshooting, but they are not the official medium to submit bug reports.

Proper bug reports will receive more attention from the devs than forum posts.

[AnujSikand]

thanks for the response,

i have done feedback in the desktop, frown in the service, and raised an issue in the office 365 admin panel, havent gotten a response as yet from MS, was hoping someone here had experienced the issue and found a resolution to to it.

[Tony]

Hi 

We are experiencing the same error with connection to Azure SQL database.

Any fix? 

Regards,

Tony

[AnujSikand]

@Tony, @freshroy, I just got off a couple hour session with MS support.  And seem to have found a work around that has worked for me at the moment.

Essentially created a couple more pages in the report, and added in some extra calculated columns, and visuals and republished.  This looks like it has resolved the issue and i have been able to have a successful refresh.

Let me know how you go and if that works out for you.

[StevenLee]

@AnujSikand The workaround you have suggested worked for me. Thanks