Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
My report has been published on the service for a while now, and has been refreshing just fine. In my report I retrieve our user profile pics from O365 using the following url
https://outlook.office365.com/ews/Exchange.asmx/s/GetUserPhoto?email={UserEmail}&size=HR120x120
Today I noticed that the refresh has been failing for the last few days and it is reporting that it is failing due to the credentials to access O365. These have not changed.
It works on desktop still, just not in the service. I have a gateway setup, and the credentials in there. I skip the test for the O365 url as is the practice.
What could have changed?
This is the error I get
Last refresh failed: Mon Aug 03 2020 17:11:34 GMT-0400 (Eastern Daylight Time)
Invalid connection credentials.Hide details
Underlying error code: | -2147467259 |
Underlying error message: | The credentials provided for the Web source are invalid. (Source at https://outlook.office365.com/ews/Exchange.asmx/s/GetUserPhoto.) |
DM_ErrorDetailNameCode_UnderlyingHResult: | -2147467259 |
Microsoft.Data.Mashup.CredentialError.DataSourceKind: | Web |
Microsoft.Data.Mashup.CredentialError.DataSourcePath: | https://outlook.office365.com/ews/Exchange.asmx/s/GetUserPhoto?email={userEmail}&size=HR120x120 |
Microsoft.Data.Mashup.CredentialError.Reason: | AccessUnauthorized |
Microsoft.Data.Mashup.MashupSecurityException.DataSources: | [{"kind":"Web","path":"https://outlook.office365.com/ews/Exchange.asmx/s/GetUserPhoto?email={userEmail}\u0026size=HR120x120... |
Microsoft.Data.Mashup.MashupSecurityException.Reason: | AccessUnauthorized |
Cluster URI: | WABI-WEST-EUROPE-redirect.analysis.windows.net |
Activity ID: | 1afa3205-73c3-4eb0-b95e-6535c8641544 |
Request ID: | 56a8ed17-4752-7c30-b4c8-92b48059e720 |
Time: | 2020-08-03 21:11:34Z |
Solved! Go to Solution.
Thanks for the quick response @GilbertQ,
It seems to be resolved.
I cleared my chache on my browser (Chrome) and then re-entered all the creds on the service and it's now decided to be ok...
Not sure what creds it was trying to use since I entered them a number of times, as well as logged out and back into the account.
I think it has to do with multiple O365 accounts being used on this machine, and that not 'cleaning up' well.
Thanks for the quick response @GilbertQ,
It seems to be resolved.
I cleared my chache on my browser (Chrome) and then re-entered all the creds on the service and it's now decided to be ok...
Not sure what creds it was trying to use since I entered them a number of times, as well as logged out and back into the account.
I think it has to do with multiple O365 accounts being used on this machine, and that not 'cleaning up' well.