Desktop work, but error in WorkSpace: File contains corrupted data [...]

[L_trainee]

Hello,

I've set up a Power BI process, loading data (excel listings) from SharePoint Library folders to a dashboard.

It works perfectly in Desktop version (load data and refresh the dashboard without any error) but when uploaded in a Workspace, any refresh attempt crash with the following error:

Data source error: File contains corrupted data.. The exception was raised by the IDataReader interface. Please review the error message and provider documentation for further information and corrective action. Table: Load New FullCasesListing.
Cluster URI: WABI-US-EAST2-B-PRIMARY-redirect.analysis.windows.net
Activity ID: 51a89816-1ad6-4c73-8fc5-c34dab94918b
Request ID: 60477eb5-864c-2e49-7d2a-cd1245e20f57
Time: 2025-04-29 16:58:12Z

If I remove some data sources from the query's reach (by changing folder's name for example), then the system can refresh from the Workspace as well.

I know the error seems to point in direction of corrupted source files, but:

• The same source (Excel files) can be read normally from the desktop version.
• When opened in excel, no issues whatsoever with the data source.
• I've been told the issue might be coming from date format, however all dates in the files are consistently in format DD-MMM-yyyy (30-May-2025).

A few points:

• I have full right (admin) on both the SharePoint library and the Workspace.
  • The Semantic model in Workspace use my Data source credentials.
  • I'm able to check the source data without issue in SP (I'm the SP admin).
  • Credentials used is: OAUth2, Privacy Level: Organizational
• The excel files are excel files extracted from a databse so they are quite consistent.
• Data on the Sharepoint library is coming from the dsame data source, but uploaded by three users: me and two others.
  • When removing "faulty" data and the workspace can load normally, it still load data from all three users.
  • This pushed me to think it's not a SP right access issue.
• New batch of excel files (3-5) are added every working day.
• There seems to have some weird "cut-off" date: data from all three users was being loaded without issue before April 17th.
  • It's causing issues past this date.
  • There was no change on SP or the Database on this date.
  • Excel files, when open, show no changes before and after this cut-off date.

After searching online I tested the following without success:

• Files Sensitivity: appear as "no label" for all files (working & not working).
  • Updating it (to "public" or "XXX Internal") doesn't solve the issue).
• Files themselves appear completely clean and not corrupted.
• None of the files are not password protected.
• Core excel > 30MB: each file is ~1.4 MB.
• Corrupted model: if hiding some files allow refresh again, It seems unlikely.

I've been trying to solkve the issue for two weeks now and nothing worked.

Would anybody have an idea of hwere the problem might coming from?

A way to try to pintpoint the issue? Any other suggestion?

[v-saisrao-msft]

Hi @L_trainee,

We haven’t heard back from you regarding your issue. If it has been resolved, please mark the helpful response as the solution and give a ‘Kudos’ to assist others. If you still need support, let us know.

Thank you.

[v-saisrao-msft]

Hi @L_trainee,

May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.

Thank you.

[v-saisrao-msft]

Hi @L_trainee,
I wanted to check if you had the opportunity to review the information provided by @Akash_Varuna . Please feel free to contact us if you have any further questions. If the response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.

[Akash_Varuna]

Hi @L_trainee  It might be caused by subtle data or formatting issues in Excel files that Power BI Service handles more strictly than Desktop. Check files added after April 17th for hidden inconsistencies like merged cells or date anomalies. Test these files individually to find the problematic ones. 

[L_trainee]

Hey @Akash_Varuna , thank you for your answer!

That's the thing: I already identified problematic files, but I can't seems to find any difference while comparing them manualy to previous data.

At this point I'm afraid of excel shenanigans with the data (especially dates fields).

My next steps will be:

• Save the files as .csv and open them with a notebook-style software for manual comparison.
• Create a different query just for these files (and merge it with the previous ones) and see if this somehow solve the issue?

Any advice to compare the two data types?

[Akash_Varuna · Accepted solution]

Hi @L_trainee I think your next steps will help pinpoint the issue. Converting the files to CSV and inspecting them with a notebook can reveal hidden inconsistencies like invalid characters or formatting issues. Creating a separate query for these files will allow you to test their compatibility with Power BI Service independently. If merging works after isolating the issue, it confirms the problem lies in file structure or formatting.