Refresh error: The end of the input was reached. OLE DB or ODBC error: [Expression.Error]

[Vee711]

I came back from Christmas to find that my Dashboard is no longer refreshing properly. I haven't made any changes to it since (besides new inputs). It keeps coming up with this error when I try to refresh it back am unsure how to fix.

Similar error in the Data:

When I click go to error: it just takes me to the first column which has 598 entries.

Any guidance will be much appreciated.

Thanks

[Anonymous · Accepted solution]

Hi @Vee711 ,

Thanks for the reply from Ritaf1983 .

An error message indicates that a step in Power Query was processed incorrectly or that a function in Power Query was given an out-of-expectation or invalid parameter.

Here are some of my suggestions:

You mentioned that it has worked fine in the past and you have not made any changes other than adding new data, then the problem may be in the newly added data, if there are blank rows in the data it will report an error, so add a step to remove any blank rows that may be present.

You can also try to check the steps that are causing the error by temporarily deleting them one by one in Power Query, which can be a bit of a pain, but is useful for troubleshooting the problem.

The user in the case below had a similar problem to you, and you can refer to his solution:

Solved: The mess "Expression.Error: The 'Count' argument i... - Microsoft Fabric Community

If you have any other questions please feel free to contact me.

Best Regards,
Yang
Community Support Team

If there is any post helps, then please consider Accept it as the solution  to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

[Vee711]

Thank you. I ended up going through each item row by row and found the issue that was causing the Count to be -29, hence causing the error. I've since fixed it and everything works now!

[Ritaf1983]

Hi @Vee711 

It seems like the issue could be related to unexpected data in the source or a step in Power Query that's processing the data incorrectly. Here's how to troubleshoot:

1. Check the data source: Ensure the source hasn't changed, contains no blank rows, and has consistent formatting (e.g., no unexpected values like text in numeric columns).

2. Review Power Query steps:

   • Open Power Query Editor and go step by step through the applied steps.
   • After each step, check if the error appears. This will help you identify the problematic transformation.

3. Potential issues to look for:

   • A function using a "count" argument that exceeds the available rows (e.g., Table.RemoveRows with an invalid count).
   • Columns with unexpected values or formatting changes.
   • Blank rows or invalid data being introduced in earlier steps.

4. Try cleaning the data:

   • Add steps to remove blank rows or replace errors in problematic columns.

5. Verify the ODBC connection:

   • If the source uses ODBC, ensure the driver is up to date.

Once you've identified the step causing the error, you can adjust or remove it to resolve the issue.

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly.