Forum Discussion
Dataflow (gen2) error: Couldn't refresh the entity because of an issue with the mashup document
I am receiving the following error when my dataflow (gen 2) attempts to sync data from Salesforce to Lakehouse.
Error Code: 999999, Error Details: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: DataSource.Error: Failed to insert a table., InnerException: Unable to create a table on the Lakehouse SQL catalog due to metadata refresh failure
I have deleted the original tables in the Lakehouse, but I am receiving the same error messages. I created a new dataflow (gen 2) with different data and received the same error message. I have created a new lakehouse altogether and tested the original dataflow (noted above) and new dataflow (gen 2) without success. I keep getting this metadata error.
Your assistance would be appreciated.
I had to rebuild the Lakehouse completely to resolve this issue. I used the same dataflow (gen 2) to achieve this outcome.
23 Replies
v-cboorla-msftMicrosoft Employee
Hi andyemiller
Thanks for using Fabric Community.
Sorry for the inconvenience that you are facing.
Currently there is ongoing bug with some similar issue "Couldn't refresh the entity because of an issue with the mashup document".
I will reach to the internal team on the issue. I will update you once I hear from them.
Meanwhile you can refer to the below links where OP has resolved the similar kind of issue with some workarounds.
Appreciate your patience.I am getting same error and neither of the workarounds worked for me.
I am also getting the same error. Any ideas yet? Its been a few months. andyemiller when you say you had to "rebuild the Lakehouse completely". Did you do anything differnt in the creation of the new lakehouse that was differnt then the first one? Or is your hypothosis that perhaps MS has invoked some new capability the Lakehouse creation process behind the scenes and this was not a capability your old lake house had. Just grabbing at straws here to try to figure out what the issue could be. Thanks for your help!
I have the same error. I need a solution.
I had to recreate the Lakehouse and Warehouse to overcome the challenge.
- v-cboorla-msft
Hi andyemiller
Follow up to see you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others.
In case if the issue still persists please upgrade the gateway version to the latest, this might help me in resolving the issue.
Please refer to the Link for more details on the latest gateway version.
I hope this helps. Please do let us know if you have any further questions.
- v-cboorla-msft
Hi andyemiller
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.
Thanks
I am in the same situation as acitsme : I am trying to ingest data from an on-premises Oracle database via a gateway and I am not able to get anywhere so far, all my attempts at refreshing dataflows are returning errors ala:
Error Code: 999999, Error Details: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: Container exited unexpectedly with code 0xC000001D. PID: 5384. Details: GatewayObjectId: c90672b7-2a7d-4bee-a4ae-bbff19f736ee (Request ID: ebb0b366-0baa-4235-8956-57b11e9511d8).
- acitsme
Advocate II
the issue still there. I've tried to delete everything in the workspace and launching dataflow from pipeline. Non success. Someone here suggested not to publish the dataflow, wait 5 min and use it on a new pipeline.
I've tried but if the dataflow is not published you cannot pick it in the pipeline.
One piece of information missing: I'm testing fabric being in a trial enviroment. MICROSOFT PLEASE HELP
I am also in a Trial environment...but I just found this one: https://community.fabric.microsoft.com/t5/Dataflows/MashupException-Error-The-value-is-not-updatable/m-p/3549552#M1260 and I have my tech guy downgrade the gw to the September version.
And my dataflows are running successfully now, ingesting data from on-premises Oracle to a lakehouse (with "staging enabled"). Need to test a lot more to build confidence in this platform.
br
johsm
N_Active Whitespace_WriteToDataDestination: There was a problem refreshing the dataflow: 'Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: Microsoft SQL: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.) Details: Reason = DataSource.Error;ErrorCode = 10478;DataSourceKind = Lakehouse;DataSourcePath = Lakehouse;DataSourceKind.2 = SQL;DataSourcePath.2 = e7wsghirn5iebb2lpycmuu2ybe-iugykc6jil7etlnah6lvkybrda.datawarehouse.fabric.microsoft.com;Client_Life_Cycle_Data;Message = A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.);ErrorCode = -2146232060;Number = 121;Class = 20;State = 0;ConnectionId = fc742d30-6693-4de7-9f82-4f138cca6e70;Microsoft.Data.Mashup.Error.Context = User GatewayObjectId: 53d15534-6a3a-4b71-b53f-da03a1adf8e2'. Error code: Mashup Exception Data Source Error. (Request ID: a21db1ae-2139-4591-9e7b-8eaf0cacbc7c).
