Refresh error from exchange connector in desktop and online

[KrysiaJK]

Hi All,

I have a dahsboard that connects multiple shared mailboxes and it has been working well until sveral days ago. It started failing every time I try to run it, whether on dekstop or online.

The error message is always: DataSource.Error: ErrorInternalServerError: An internal server error occurred. The operation failed.. Microsoft.Data.Mashup.ErrorCode = 10478. DataSourceKind = Exchange.

The thing is, everytime it gives a different mailbox as a source of failure. 

I have re-done the tables, made sure all of them are Exchange Online, but I'm getting really frustrated with this now...

As to what I'm doing with the data, there are several steps to remove, add conditional columns etc in each of the shared mailbox queries, then I append them all into one table and load that to my dashboard.

Has anyone experiend same issue recently?

[KrysiaJK · Accepted solution]

Thank you both, @wardy912  and @v-sgandrathi 

I have confirmed that all necessary permissions are in place and cleared the cache, but that did not help.

I have then proceeded to strip each query one by one, step by step to identify the problems. Turns out, the problematic steps have always been either extracting a record column (eg. Attributes column from the Exchange Online) or extracting data from a list column (eg. Categories column). I used try...otherwise for these steps instead of just extracting the data from the record or list, and that seems to have done the trick!

Interestingy, this issue appeared only in tables where there was a significant number of records (10k+)

Hope this helps someone if they are experiencing same issues with refreshing exchange online.

[v-sgandrathi]

Hi @KrysiaJK,

Thank you for providing your comprehensive findings; they are much valuable.

Your explanation regarding the issue arising from extracting data from record or list columns, such as Attributes or Categories, particularly with larger datasets, is clear and logical.

Implementing the try … otherwise method is an effective solution for managing unexpected values and preventing refresh failures.

This approach aligns with similar scenarios we have observed in Exchange Online queries, where large volumes of records can lead to errors due to minor data inconsistencies.

By incorporating error handling, you have enhanced the resilience of the queries.

Thank you for sharing your solution, as it will be beneficial for others encountering similar refresh challenges.

Thank you.

[v-sgandrathi]

Hi @KrysiaJK,

Firstly Thank you for the answer @wardy912.

Thank you for providing the details. The ErrorInternalServerError – Microsoft.Data.Mashup.ErrorCode = 10478 typically indicates a temporary issue with the Exchange connector, especially since the error appears across different mailboxes.

As initial step, please verify the data source credentials in both Desktop and Service, refresh each mailbox individually to determine if the issue is related to multiple queries, and check with your administrator regarding any recent policy or permission updates in Exchange Online.

You try clearing the Power BI Desktop cache, simplifying any complex query transformations, or dividing the refresh into smaller tables before appending them.

Next, reviewing the refresh history in Power BI Service could help pinpoint any recurring issues during the process.

Thank you.

[wardy912]

Hi @KrysiaJK 

 First step I would do is edit the query, remove steps and refresh to find out which step is causing the issue. You may find this is a transformation in power query at fault, a column with an unexpected null value or something similar that you can edit to fix the issue.

--------------------------------

I hope this helps, please mark as solved if it does!

kudos always welcome .

Connect with me on LinkedIn

Subscribe to my YouTube channel for Fabric/Power Platform related content!