Error: conflicting protocol upgrade?

[dbeavon3]

Can someone provide an English translation of the message:

Error Code: Mashup Exception Data Source Error,
Error Details: Couldn't refresh the entity
because of an issue with the mashup document MashupException.

Error: conflicting protocol upgrade

The team is once again using language that doesn't mean anything to the audience.  It is like technobabble from Star Trek.

This happens on a Gen 2 dataflow refresh with a recent gateway version (May or later).

Any tips on workarounds would be appreciated.

[Anonymous · Accepted solution]

Hi, @dbeavon3 

We apologize for the bad experience. After my search, I found a similar issue to yours. This issue appeared in November of last year and seems to be related to the November version of the gateway. The workaround at the time was to roll back the following version and wait for updates from the gateway. I suspect that this time it may have something to do with the new version of the gateway again.

Disabling staging for Power Query at the same time seems to alleviate the problem, so you might want to give it a try. Here are the relevant links that you can take a look at:
Solved: Re: Couldn't refresh the entity because of an issu... - Microsoft Fabric Community

Solved: MashupException.Error: The value is not updatable. - Microsoft Fabric Community

Solved: Dataflow (gen2) error: Couldn't refresh the entity... - Microsoft Fabric Community

Solved: Re: Gen2 Dataflow Failed to insert a table - Microsoft Fabric Community

Apologies again.

How to Get Your Question Answered Quickly

Best Regards

Yongkang Hua

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hi, @dbeavon3 

Mashup Exception data source error, which means that there was a problem with the data source during the mashup process.
There was a problem with mashup documents, and there was a problem with combining documents from different data sources. A conflict occurred when the communication protocol was upgraded, possibly due to an update.

You'll need to make sure that the gateway version you're using is compatible with the dataflow. Sometimes, rolling back to a previous version resolves the conflict. Also confirm that the data source's credentials are up-to-date and configured correctly.
For issues with mashup documentation, review recent changes to the mashup documentation that may have caused conflicts.
Check the privacy level and set it to Private in Power BI Desktop and the Power BI service. This helps avoid conflicts when combining data from different sources.
Ensure that all data sources and gateways use compatible protocols. A mismatch can cause these errors.
You can also check the official documentation or support forums for known issues or patches related to specific bugs. Here are the relevant links:

Known issue - ParquetSharpNative error in dataflow refresh using a gateway - Microsoft Fabric | Micr...

Solved: mashup data source error in gateway (only) refresh - Microsoft Fabric Community

How to Get Your Question Answered Quickly

Best Regards

Yongkang Hua

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[dbeavon3]

@Anonymous 
Thanks for the response.  I was looking for an English translation.  I don't need any workaround at this time.  I have discovered a workaround (see below***).  I know what a mashup is, and a data source, and a document. 
But the part that is a real head-scratcher is this :

Error: conflicting protocol upgrade
You said:
"A conflict occurred when the communication protocol was upgraded, possibly due to an update"

... but that is as meaningless to me as the original error message.

What specific protocols are being referenced here?  What is the thing being "upgraded"?  What was the version before?  What was the version after?

Again, I am on a recent version of the gateway, and using fresh PQ.  There is nothing on my side that would lead me to anticipate a "conflicting protocol upgrade.

If you are using an AI to generate content here, please stop doing so.  It is just creating circular reasoning and is not contributing any new information, or first-hand/real-world experience. 

*** Workaround:  The error appears to be intermittent.  Refreshing the PQ over and over again causes it to go away.

[dbeavon3]

An update.  Like with other issues in Power BI, it seems to go away if you click the button again and again.

It seems like a feature not a bug, and it may enhance job security for the guy pushing the button. 😉

[Anonymous]

Hi, @dbeavon3 

Have you solved your problem? If so, can you share your solution here and mark the correct answer as a standard answer to help other members find it faster? Thank you very much for your kind cooperation!

Best Regards

Yongkang Hua

[dbeavon3]

You have to click the refresh button over and over until it works.  It is a solution, but not the right solution.

[dbeavon3]

We just upgraded to the January (2025) version of the PBI gateway and this error is still appearing:

"Error Code: Mashup Exception Data Source Error, Error Details: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: conflicting protocol upgrade Details: Reason = DataSource.Error;Microsoft.Data.Mashup.Error.Context = System GatewayObjectId: ccc169cc-5919-4718-9c07-48672601c02c (Request ID: aaaaa4e9f-5f3b-4a51-9181-f1ef3a6bbcd3)."

@Anonymous  Do you have any more insight into this error?  Any chance this will ever be added to the "known issues" list?