Forum Discussion
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 warehouse I get the same issue.
Im using a Dataflow Gen2 to push data from excels to SQL tables
In Power BI I can see all the tables and columns but when I try to add anything I can get the error below.
I have tried enabling / disabling staging in Dataflow but makes no difference.
I can connect to the SQL server using MS SSMS and run queries against it fine.
- I have checked all the settings & permissions that I can find
Below is the error I am getting, can't find anything on google for this.
Any help is appreciated.
Couldn't load the data for this visual
Unexpected parquet exception occurred. Class: 'ParquetStatusException' Status: 'IOError' Message: 'Encountered Azure error while accessing lake file, StatusCode = 404, ErrorCode = , Reason = Not Found'
38 Replies
I'm facing the same error but a different experience. Running through the Fabric tutorial here to create a data warehouse. The problem lies in creating the report visualization. Dragging SalesTotal from the FactSalesOrder table works fine. Dragging Category from the DimProduct table causes the error message. I've verified that data is in the table via the Warehouse explorer in Fabric as well as in OneLake via Azure Storage Explorer. I've also created a new workspace and went through the same steps only to run into the same issue.
Steps to repro:
Starting at Create tables and insert data:
- Create DimProduct table
- Insert sample data
- Run new query with GitHub MSFT Learning warehouse txt file SQL script
- Follow instructions to properly model data (make connections in the Model view)
- Go to Visualize your data section
- Follow instructions to create a New Report
- When dragging clicking category to add to view, the error will occur.
One thing I haven't tried was skipping steps 1 and 2 in the repro steps and just using the SQL Script as it contains code to drop and recreate that table with the original values (as well as some new ones). Though that shouldn't make a difference.
Update: After reviewing my model, I noticed that additional relationships were automatically created. (See image)
They link on the same keys but start in the opposite direction e.g., DimCustomer -> FactSalesOrder -- with Assume Referential Integrity turned on. I removed these relationships, went back to Power BI, clicked SalesTotal (ok), clicked Category (error again), went back to my Model view and those relationships had reappeared! What gives?!
gthillAdvocate I
I just had the same issue following Lab 06 'Analyze data in a data warehouse' on mslearn-fabric (microsoftlearning.github.io)
Would you try my solution?
Re: Unexpected parquet exception occurred. Class: ... - Microsoft Fabric Community
I encounted the same error doing the MS Fabric labs. I ended up:
- deleting the whole data warehouse
- create a new v2 data warehouse
- skip entering data manually and just put in the SQL script to create the 4 tables with data.
- I was then able to create the correct relationships
However, I did continue to run into random errors (in the visual editor and when hiding columns). I hit refresh a couple times, deleted and readded things, and got things to work.
Overall, it was very buggy. Hope it gets resolved soon because dropping a whole data warehouse in real life is more of an undertaking than during a lab.
- Alex_Rajkov
Advocate III
Great to hear.
please post the answer / solution if possible Hi Anonymous ,
If a root cause or solution is found, please continue to share this issue to help others experiencing similar problems.
Thanks for your efforts & time in advance.
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.- Alex_Rajkov
Ok, when will it be fixed?
Would you try my solution?
Re: Unexpected parquet exception occurred. Class: ... - Microsoft Fabric Community
I found a quicker solution than the one proposed above for deleting the tables.
Go into your Lakehouse or Warehouse object > Reporting > Manage default semantic model
Remove all your tables from the semantic model, click confirm.
Add all your tables back to the semantic model again.
Try to load the tables in a report and confirm the error no longer exists.I got this error as well and recalled that I had code in my notebook which dropped and then recreated the tables. Therefore, the semantic model lost the connection to the tables.
- It can be temporarily be resolved, until the next run of the notebook, with opening the semantic model -> edit tables -> and click the refresh button.
- Ultimately, however, tables should not be dropped and then recreated. So I removed the corresponding code lines and it worked even after rerunning the notebook.
Hello everyone,
I am encountering the same problem with a customer. I currently 'solve' it by removing and adding the tables in my semantic model every day. Obviously not workable for a customer.
Does anyone know the status of this error message, or where I can track the status? I couldn't find any recorded bug on this topic, even though I expected it to be at the top of the list.
Thanks.
Floris
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.- Alex_Rajkov
Hi,
this is the kind of reply wich is not helpful at all. this answer is expected from a chat bot, not a person wich folows the stated problem. sorry.
The files exist and can be accessed by querying via sql. select from ...
the initial pbi report ist created within the fabric workspace and is showing results. wich was stated and so the second and third suggestions are obsolete. clearly the permission doesnt change by refreshing the data, right?
please investigate this topic. 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
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 DFs2. 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..
- djurecic
Super User
Anonymous Are you using the Fabric trial? If not, what Fabric capacity sku are you using?
I need a solution too
Hi Anonymous ,
I think I found the root cause about your problem which I also had.
I found that this issue happens when I add 'category' from 'DimProduct' and never happens when I add 'SalesTotal' from 'FactSalesOrder'.
So, I explored the workspace first in the left pane.
When you click the workspace, for me it is 'dp_fabric', you can see a similar image to the below:
Then you will see there is a semantic model, the number 2 in the red circle of the above image.
Click the semantic model, you will see a modal like window in the right pane.
Then click 'View item details' in the green button, the number 3 in the above image.You will see another page of 'Details for <<your semantic model>>' and there are information about Tables in the right pane.
When I tick the table of 'DimProduct', I found that the values of 'DimProduct' was not visible and there's the '404' error about the table.
So, I thought that there was some problem when I create the table of 'DimProduct'.
There must have been a trouble when I created the table.
Since I found the root cause of the problem, I made a hyperthesis to fix by making another query to create the table.
Move to the warehouse by clicking the warehous in the left pane.
First, I need to delete the relations between the existing "FactSalesOrder" and "DimProduct" before creating the "DimProduct" table again.
Because of the relationship, you cannot recreate the table without deleting the relationship.
I deleted the visual query by right-clicking 'Visual query 1', just in case.
Now the time to re-create the table of 'DimProdut' by running the proper query.
For me, it was SQL query 3.
After getting the message that the query succeeded, make the relation between 'FactSalesOrder' and 'DimProduct' again.
Make another visual query as well.
Move to the semantic model again to check if the error has been fixed.
I can see the table was fixed.
Let's check if the error fixed in the report as well.
Move to the warehouse and click model to creat a new report.
(It may ask you sign in)
Threre's a blank report page.
Select 'clustered bar chart'.
Add the relevant data into the chart.
Y axis --> Category from DimDate.
X axis --> SalesTotal from FactSalesOrder.
Adjust the size of the chart just like the below image.
I hope this help you.
If it works, would you take this answer as the verified answer?
I tried your method and didn't work, even the semantic model is fixed but when tried to work in Power BI same error
parandurume thank you for this detailed explanation.
In my case, the bug appeared when I dropped the table and recreated it again in the stored procedure. It seemed like the link between the table and the semantic model was disrupted.
Instead of dropping the table, I just reloaded the data, and now it's working as expected.
However, every time the table schema has to be changed, the table must be altered or recreated. As a result, the semantic model has to be deleted and recreated with the same name.
