Unable to load DLL 'ParquetSharpNative':

[frankmroberts]

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

[pqian_MSFT]

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.

[frankmroberts]

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!

[pqian_MSFT]

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.

[StuartTurner]

Is there a known issue/ recommendation for VMWare machines ? We have installed the latest Gateway version but are still getting this error

[pqian_MSFT]

@StuartTurner the issue around AVX2 instruction has been resolved, so you are probably running into a new issue.

Can you share your GW version and the exact error message?

[StuartTurner]

GW version 3000.214.8

ErrorCode=UserErrorFailedFileOperation,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=The file operation is failed, upload file failed at path: 'c64e7d4a-1a16-4b4d-b35a-77733bd38772/9a784df0-744c-41fb-8fa8-94e8291cdd48/Tables/PeriodTest'.,Source=mscorlib,''Type=System.TypeInitializationException,Message=The type initializer for 'Microsoft.DataTransfer.ClientLibrary.ParquetV2WriteTypeFactory' threw an exception.,Source=Microsoft.DataTransfer.Richfile.ParquetTransferPlugin,''Type=System.DllNotFoundException,Message=Unable to load DLL 'ParquetSharpNative': A dynamic link library (DLL) initialization routine failed. (Exception from HRESULT: 0x8007045A),Source=ParquetSharp,'

[pqian_MSFT]

@StuartTurner 

OK, that is the March release but coming from Pipelines. Since we have combined ADF SHIR and the Power BI Gateway, the Parquet problem needs to be patched in both sides.

Are you using Pipelines directly or are you trying out the fast copy via pipelines feature in Dataflows?

[StuartTurner]

We're using Pipelines directly - Copy data activity. To ingest data from an on-premise SQL Server database.

Dataflows are working (haven't tried fast copy, my undestanding is this is only available for Azure SQL). However, we are implementing a data driven load pattern using Pipelines.

Is there anything in the April release that addresses this issue?

Not sure what you mean by patching both sides, we can only update the Gateway - is there something that can be applied in Fabric?

Thanks

[pqian_MSFT]

This is something that we will need to fix on our side. 

[tonyalexanderIM]

@pqian_MSFT has there been any update related to this issue specifically for Pipelines? we are still having the issue with the latest gw version installed. 

[pqian_MSFT]

Yes, I'm working with the pipelines team to get this patched

[boley2131]

Is there any updated timeline on when this may be fixed?

[pqian_MSFT · Accepted solution]

@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.

[boley2131]

Looks like its working now.  Thanks!

[pqian_MSFT]

The SHIR part of the issue should be fixed within the month.

[pqian_MSFT]

@frankmroberts @JayJay11 @jawa @cieplag The patched gateway version 3000.214.8 is now live. Please download it and install it again.

[cieplag]

I have verified that everything works now after installing the March version. Thank you!

[jawa]

I was able to resolve

 Unable to load DLL 'ParquetSharpNative': A dynamic link library (DLL) initialization routine failed

by 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/

[frankmroberts]

@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!

[miguel]

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?