BUG::Invalid: Parquet magic bytes not found in footer, OLE DB or ODBC error: [DataFormat.Error]

[Element115]

ISSUE:

After connecting successfully to a Fabric lakehouse table via the Azure Data Lake Gen2 from Power Query Desktop, the following error messages are emitted by Power BI Desktop when applying the changes:

Query1
Failed to save modifications to the server. Error returned: 'OLE DB or ODBC error: [DataFormat.Error] Parquet: class parquet::ParquetInvalidOrCorruptedFileException (message: 'Invalid: Parquet magic bytes not found in footer. Either the file is corrupted or this is not a parquet file.'). '.

Query parameters
Parameter2
Failed to save modifications to the server. Error returned: 'OLE DB or ODBC error: [DataFormat.Error] Parquet: class parquet::ParquetInvalidOrCorruptedFileException (message: 'Invalid: Parquet magic bytes not found in footer. Either the file is corrupted or this is not a parquet file.'). '.

STEPS:

Assumptions:  You have created a Fabric lakehouse and already populated it with at least one table.

0__in Power Query Desktop, Home>New Source>More>Azure.

1__select Azure Data Lake Gen2 in the right pane and then click Connect.

2__navigate to your Fabric lakehouse and click ...>Properties.

3__copy the https URL.

4__navigate back to Power Query Desktop and paste the URL in the dialog into the 'File' textbox under 'Data view' and click OK.

5__click the 'Combine and Transform Data' button in the new dialog that pops up.

6__a new dialog opens up titled 'Parquet' presenting a view of the data; all looks good; click 'OK.'

7__a preview of the data loads fine inside the Power Query Desktop editor. Click Home>Close and Apply.

8__you are back in Power BI Desktop and the 2 error messages above appear in the dialog titled 'Load.'  You cry yourself to sleep.  😓

[Anonymous]

Hi @Element115 ,

This error typically occurs when Power BI Desktop tries to read a Parquet file but cannot find the expected “magic bytes” in the footer of the file. The “magic bytes” are a specific sequence of bytes that identify the file as a Parquet file.

If the Parquet file was downloaded from a source, there might have been an issue with the download process that caused the file to be incomplete or corrupted. Try re-downloading the file. If the file was generated by a process, try regenerating the file.

Best Regards,
Community Support Team _ Caitlyn

[Element115]

@AnonymousThis happens when using the ADSL2 connector to connect to a Fabric lakehouse whose tables have all been generated by multiple dataflows gen2.  So at this point, if the magic bytes are missing, it's either a bug with the connector, or with the way Fabric dataflows gen2 generate those parquet files when writing to a lakehouse.  

It's out of my hands at this point, and in Microsoft's lap to investigate what on earth is going.