Forum Discussion
Refresh failure
Hello,pborah and FarhanJeelani ,thanks for your concern about this issue.
Your answers are excellent!
And I would like to share some additional solutions below.
Hi,Kalina .I am glad to help you.1. Please check whether the data type format of the data in your data source is correct.
2 If you could ensure that there is no problem with the data itself, please try to clear the data source cache in power BI Desktop.
3. Check whether your Power BI Desktop version is a newer version, if the version is too old, you can update the Power BI Desktop version!
Hope the following related articles and issues can help you.
How to solve OLE DB or ODBC errors in PowerBI - CloudFronts
When using Power BI Desktop, you may encounter various data loading failures, but some of them can be resolved after clearing the data cache and reopening Power BI Desktop to reload the data.
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
This error in Power BI indicates an issue with reading data from a Parquet file. The `System.ArgumentOutOfRangeException` in the error message suggests that Power BI encountered unexpected data or reached an out-of-bounds value while reading from the Parquet source. Here are some possible causes and solutions:
1. Check for Corrupted Parquet File
- The Parquet file itself might be corrupted or incomplete, which could cause Power BI to fail when trying to read it.
- Try re-generating the Parquet file or replacing it with a new copy if possible.
2. Power BI Version Compatibility- Power BI may not fully support the version or format of the Parquet file you’re using. Ensure that you’re using the latest version of Power BI Desktop, as updates often improve compatibility with different file formats.
- You can download the latest version of Power BI from the official [Power BI download page](https://powerbi.microsoft.com/).
3. Data Type or Structure Issues
- The Parquet file might contain complex data types or structures that Power BI is struggling to interpret (e.g., nested structures, unusual encodings).
- If you have control over the data source, try simplifying the structure of the Parquet file, such as removing nested fields or adjusting complex data types.
4. Memory Constraints
- The error mentions `PagedHttpBinaryValue.GetPage`, which could indicate that Power BI is running into memory limitations or is unable to fully load the dataset.
- Try refreshing the data in smaller increments if possible, or increase your machine’s memory resources to handle larger datasets.
5. Encoding or Compression Issues
- Some Parquet files use compression codecs that Power BI may not fully support.
- If you have the option, try saving the Parquet file with a different compression setting (e.g., uncompressed, or using a simpler codec like `GZIP`).
6. Use Alternative Tools to Validate the Parquet File- Use tools like Apache Parquet CLI, Apache Spark, or Python libraries (e.g., `pyarrow`, `pandas`) to read and validate the Parquet file. If these tools can read the file successfully, then the issue is more likely specific to Power BI’s handling of the data.
7. Review Applied Steps in Power Query
- In Power BI, go to the Power Query Editor and check each step in the Applied Steps pane. Sometimes, transformations like renaming columns, changing data types, or filtering rows can cause errors when Power BI encounters unexpected data in the Parquet file.
- Removing or adjusting some steps may help isolate the problematic transformation.
8. Convert the Parquet File to Another Format
- If the Parquet format continues to cause issues, consider converting the file to another format, such as CSV, and testing if Power BI can read it without errors. This is a workaround, but it can help confirm whether the issue is specific to Parquet.
Additional Information
If the issue persists and you’re still not sure of the root cause, try enabling Data Load Diagnostics in Power BI to get a detailed log of the error. This can sometimes provide more insight into the specific part of the file or transformation that is causing the problem.
Let me know if any of these steps help or if you have further details about the data source structure!