Forum Discussion
Error: conflicting protocol upgrade?
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 CommunitySolved: 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.
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
You have to click the refresh button over and over until it works. It is a solution, but not the right solution.
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?