Forum Discussion
Unable to load DLL 'ParquetSharpNative':
I am testing out fabric for my organization and one of our key things to figure out is how to attached to a vendors MySQL database on AWS and bring it back to a LakeHouse. I have created a Gen2 Dataflow that uses our on prem Data Gateway. I then provide it the login info for the MySQL database on AWS and I can succefully see all the table in the database, so that part seems succeful. However when I attempt to bring it back to the LakeHouse in Fabric it fails. Error messages can be seen below.
- There was a problem refreshing the dataflow. Please review the error message(s) below, fix the problem, and try again. (Request ID: ee843b8f-21f2-4a4b-a0ee-9ad495a060b6)
- flightspan_maf_test aircraft: Error Code: 999999, Error Details: Couldn't refresh the entity because of an issue with the mashup document MashupException.Error: Unable to load DLL 'ParquetSharpNative': A dynamic link library (DLL) initialization routine failed. (Exception from HRESULT: 0x8007045A) Details: GatewayObjectId: 6b63dd19-d7ee-4ee0-8a3a-0bb4e48f5b66 (Request ID: ee843b8f-21f2-4a4b-a0ee-9ad495a060b6).
After the process runs, I do seem to get a empty parquet file and a _delta_log file in the Tables section of the LakeHouse. All the files have a size of 0.
To rectify the situation we have attempted several things:
1) Per a form post we have upgraded to the latest version of the Data Gateway - no luck
2) I have stripped the fields moved over to the DataLake to just two fields - no luck
3) Turned off Enable Staging on the table
Any ideas?
Thanks for your Help
Frank
boley2131 tonyalexanderIM StuartTurner , the latest gateway version (3000.222.10) has been published and it contains the fix for the pipeline side as well. Please try it out.
30 Replies
Hi frankmroberts ,
Thanks for using Fabric Community.
Apologies for the issue you have been facing. I would like to check are you still facing this issue?
It's difficult to tell what could be the reason for this performance. I would request you to wait for sometime and try again.
If the issue still persists, please reach out to our support team so they can do a more thorough investigation on why this it is happening: LinkAfter creating a Support ticket please provide the ticket number as it would help us to track for more information.
Hope this helps. Please let us know if you have any other queries.Anonymous Thanks for looking at my thread. I have re-created the dataflow this morning and it appears to have the same error. I have placed a support ticket on this and the case number is 2402020010002491
Let me know if there are any other details I can provide. This is a pretty important trial for our ogranization and if Fabric can't create a dataflow for this database I will need to pass on using fabric.
Thanks for your help
This could potentially be related to the machine where the gateway is installed.
What happens if you use a different machine to run / host the gateway?
miguel I was also thining that. I have started down the road to install a data gateway (personal mode). But based on the feedback on my ticket with MS, they didn't think that was the issue. I did see in another post where someone downgraded there gatway to the Sept 2023 version and this fixed their issue. I am waiting on what I here from MS, but if I don't here back by the end of the day I might give the data gateway (personal mode) a shot. I am new to the use the of the data gateway, so it is unclear to me how it is configured, if anyone has a link to that, that would be amazing. I do have it installed on my machine, but I assume there is some configuration that must occur to get it working correctly.
Definitely give it a try. Try installing the gateway on a different machine and use that new gateway installation for your dataflow. Then see if the issue persists or not.
Do continue talking with the support team and if you see that things work after the new installation, then report those back to the support team.
Anonymous
its been over a week and the support analyst has not responded to my emails and teams posts. Is there some other way to communicate with them that I am not aware of. The problem still exists, however I was successful at coming up with a workaround using a Spak Notebook. But it would still be nice to get to the bottom of this topic. Thanks for your help!
I was able to resolve
Unable to load DLL 'ParquetSharpNative': A dynamic link library (DLL) initialization routine failedby downgrading to September 2023 release of data gateway.
I used the download link here https://powerbi.microsoft.com/en-us/blog/on-premises-data-gateway-september-2023-release/
Hey everyone, I believe we have narrowed down the ParquetSharp issue on post-NOV-23 gateways to compilation options against the AVX-2 instruction set, which does not work on older CPUs or hyper-v servers that has compatibility mode turned on.
If you are on older CPUs: wait for an update
If you are on Hyper-v that has compatibility mode on: try turning it off.
So to be clear, is this an issue with where the gateway is installed? Are you saying turn off Hyper-v compatibility mode off on that machine where the gateway is installed? If so will this then be fixed on the coming version of the gateway? When will that come out?
Thanks for your help on this!
Yes, it's about where the GW is installed. It'd be interesting to confirm how many people on this thread is running inside Hyper-V with compatibility mode on.
It'll be fixed and QFEd. Expect this within 1-2 business weeks.
