Error message when evaluating data flow: An error occurred while communicating with another service

[brian_123]

I am receiving this error on multiple data flows.  My co-worker with the same access rights doesn't get the error.  I have tried to rebuild the query and did not get the same error.  I am reluctant to rebuild all the data flows.  

An error occurred while communicating with another service, please try again later. If this problem recurs, please contact support with this message. (Request ID: 5437f65e-2c48-4d56-83a5-ead5bbdd9b8c)

[v-saisrao-msft]

Hi @brian_123,

Checking in to see if your issue has been resolved. let us know if you still need any assistance.

Thank you.

[v-veshwara-msft]

Hi @brian_123 ,

Thanks for reaching out to Microsoft Fabric Community.

Just wanted to check if the responses provided were helpful. If further assistance is needed, please reach out.
Thank you.

[brian_123]

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.   

[Parchitect · Accepted solution]

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

[GilbertQ]

Hi @brian_123 

Can you please provide more details with regards to the data source that you are connecting to or the source as that potentially might be where their issue is because your other co-worker does have the access required.