Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
2 years ago

Unexpected parquet exception occurred. Class: 'ParquetStatusException'

Hi I am getting errors on my power bi desktop app and web published versions. Its connecting to Azure Data Warehouse through a dataset though even if I create a new report and connect direct to ware...
dataflow
Need Help
Anonymous's avatar
Anonymous
Not applicable
2 years ago

Hi Anonymous ,

Based on the error message you provided, it seems that there is an issue with accessing a lake file in Azure. The error message indicates that the StatusCode is 404, which means that the requested resource was not found.

I would recommend checking the following:

  • Ensure that the lake file exists and is accessible.
  • Check if the file path is correct.
  • Verify that you have the necessary permissions to access the file.

 

Best regards,
Community Support Team_Binbin Yu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Anonymous's avatar
Anonymous
Not applicable
2 years ago

Hi


Thanks for your reply. The strange thing is that when I first create the flow it all works fine. Then if I re-run the Dataflow I get the issue. I have found that if I then 'drop' the table, go back to the flow and get it to recreate the table and rerun the import it all works again. The only difference is that on the first run it creates the table, on the second run it is replacing the data. 

 

Hope that makes sense.

 

Regards

Toby

  • Alex_Rajkov's avatar
    Alex_Rajkov
    Icon for Advocate III rankAdvocate III
    2 years ago

    Hi Toby,

     

    this is exactly what I found out yesterday. (Drop the tables in Lakehouse / Warehouse) and rerun the dataflow solves the report for again only the 1st refresh.
    But This is clearly a bug IMO. Replacing a table shouldt break the lineage (table names and so on didnt change..).
    Maybe for now we could try something like this:
    1.  using pipeline to schedule the DFs

    2. adding a step (for warehouses it can be a stored procedure) before running the DF, which says - not drop the table - but delete all rows in the table

    3. changing the DF from replace to append

    maybe this works but clearly this should be a top issue to solve for the fabric team..

    • Anonymous's avatar
      Anonymous
      Not applicable
      2 years ago

      I had a support call with MS yesterday and they confirmed it is not linked to my subscription model and they are looking into it. 

       

      • webchris's avatar
        webchris
        Icon for Advocate III rankAdvocate III
        2 years ago

        I am facing the same issue... I hope that support will come back with a solution quick...

    • SnoekL's avatar
      SnoekL
      Icon for Helper II rankHelper II
      2 years ago

      Any news on this issue. I'm experiencing the same problem.

    • Anonymous's avatar
      Anonymous
      Not applicable
      2 years ago

      Having similar issue. Please keep us posted of the solution

  • kroma's avatar
    kroma
    Regular Visitor
    2 years ago

    Hi,

    I have the same issue. I am not able to create any report using Fabric Warehouse default semantic model after refreshing Fabric Warehouse data using DataFlowGen2.

    Error:

    Unexpected parquet exception occurred. Class: 'ParquetStatusException' Status: 'IOError' Message: 'Encountered Azure error while accessing lake file, StatusCode = 404, ErrorCode = , Reason = Not Found'

    This looks like a bug. 

    Workaround: do not use warehouse default semantic model, but create new semantic model and use it for your reports. It will still work after warehouse data refresh.

    Regards,

    Romans

  • EliseuRodrigue's avatar
    EliseuRodrigue
    New Member
    2 years ago

    Também estou passando por esse problema, fiquei 4 dias batendo cabeça com isso, se alguém tiver uma solução ou novas atualizações sobre, será de grande ajuda.

    • ernesth65's avatar
      ernesth65
      Regular Visitor
      2 years ago

      try to recreate the semantic model and then run the script, also make sure that in the visual query a relationship is made, hope this helps