Forum Discussion
Error message when evaluating data flow: An error occurred while communicating with another service
- 2 months ago
Hi brian_123,
that detail hopefully is the key.
The Analysis Services connection itself is fine — it works in your other dataflows, and a recreated query works too. So this isn't a broken connection; the affected dataflows have their source binding authenticated under a different identity, most likely your co-worker who created or last authenticated them. A dataflow ties source authentication to its stored bindings, so they fail under your account while a query you build yourself binds as you and works.
Fix (no rebuild):
1. Open one affected dataflow > Edit tables.
2. Re-authenticate the Analysis Services source under your own account. If there's a gateway mapping, remove and reassign it.
3. Save & Close — this re-binds the existing queries as you.If that clears it, repeat just step 3 on the rest.
Durable solution for production recomendation:
authenticate the source with a service principal or shared service account so the binding doesn't depend on one user.
Docs: https://learn.microsoft.com/en-us/power-bi/transform-model/dataflows/dataflows-features-limitations
The source connection is Analysis Services. Other data flows with the same source connection are not having issues. Also, if I recreate the query exactly the same way it works.
Hi brian_123,
that detail hopefully is the key.
The Analysis Services connection itself is fine — it works in your other dataflows, and a recreated query works too. So this isn't a broken connection; the affected dataflows have their source binding authenticated under a different identity, most likely your co-worker who created or last authenticated them. A dataflow ties source authentication to its stored bindings, so they fail under your account while a query you build yourself binds as you and works.
Fix (no rebuild):
1. Open one affected dataflow > Edit tables.
2. Re-authenticate the Analysis Services source under your own account. If there's a gateway mapping, remove and reassign it.
3. Save & Close — this re-binds the existing queries as you.
If that clears it, repeat just step 3 on the rest.
Durable solution for production recomendation:
authenticate the source with a service principal or shared service account so the binding doesn't depend on one user.
Docs: https://learn.microsoft.com/en-us/power-bi/transform-model/dataflows/dataflows-features-limitations