Forum Discussion
We encountered an error during evaluation.
Hello,
I encountered an issue while performing an evaluation. The following error message appeared:
"An error occurred while communicating with another service, please try again later. If this problem recurs, please contact support with this message."
Additional details:
- Request ID: ca57e4da-8d51-4462-8fac-14f2ea70ee10
- The error occurs repeatedly even after several attempts.
Please help investigate the cause and provide guidance on how to resolve this issue.
Unfortunately, I’ve tried re-authenticating but it still doesn’t work. Since I needed it urgently, I created a new dataflow that is exactly the same as the old one, and surprisingly it worked, though I still don’t understand why the original one continues to fail.
5 Replies
Hii epratomo
It is typically caused by a temporary service outage, expired data source credentials, or an offline/on-premises gateway not a DAX or report issue. Re-authenticate dataset credentials, confirm the gateway is online (if used), and retry. If it persists, contact Microsoft support and provide the Request ID for backend trace investigation.
Hey epratomo ,
The error message “An error occurred while communicating with another service” usually indicates a backend service issue in Power BI rather than a problem with your report logic. It typically occurs during dataset refresh, dataflow evaluation, publishing, or when using DirectQuery, and means one Power BI component failed to communicate with another service (capacity, gateway, identity service, etc.).
Since the issue is recurring, check the following:
- Confirm there is no active outage in the Microsoft 365 Admin Center (Service Health).
- If refreshing a dataset, verify the capacity is active (not paused or overloaded).
- If using an On-Premises Data Gateway, ensure it is online and credentials are valid.
- If using DirectQuery, confirm the source database is accessible.
- Check whether any credentials (including Service Principal secrets) have expired.
Because you have a Request ID (ca57e4da-8d51-4462-8fac-14f2ea70ee10), the best next step is to open a Microsoft support ticket and provide:
- The Request ID
- Exact timestamp (with timezone)
- Workspace and dataset/dataflow name
- Capacity name (if applicable)
Microsoft can trace the backend failure using that Request ID and identify the root cause.
If this explanation helped, please mark it as the solution so others can find it easily.
If it helped, a quick Kudos is always appreciated it highlights useful answers for the community.
Thanks for being part of the discussion!
Unfortunately, I’ve tried re-authenticating but it still doesn’t work. Since I needed it urgently, I created a new dataflow that is exactly the same as the old one, and surprisingly it worked, though I still don’t understand why the original one continues to fail.
Hi epratomo ,
It is possible that one of the internal services used by the dataflow is failing, which could be causing the error you are encountering. Although glad to know you werre able to bypass the error by creating a new Dataflow.We really appreciate your efforts and for letting us know the update on the issue.
Please continue using fabric community forum for your further assistance.
Regards
Hi epratomo
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank you.
