Error when publishing Power BI report with multiple connections!

[Pujoni]

In Power BI Desktop I am able to update normally, but when publishing to the Workspace, an error occurs!

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.

I have 4 connections, 3 using GoogleSheets.Contents and 1 using SharePoint.Files. Is there any way to solve this or at least identify where the error is?

[Pujoni]

Something strange happened, on the other computer it updates in the Desktop version now, but in the Web version it continues with the same error.

[edhans]

Did you try narrowing down which file(s) it is per my previous post?

[Adamboer]

The error message you received indicates that there may be corrupted data in your Power BI Desktop file. When publishing your report to the workspace, the error was triggered due to an issue with the IDataReader interface.

There are several steps you can take to try to solve this issue. Firstly, you can try to identify which of the 4 connections may be causing the problem. To do this, you can try publishing the report with each connection disabled one at a time, to see if the error persists. If you are able to identify the connection that is causing the issue, you can then investigate further to determine the cause of the corruption.

Additionally, you can try to resolve the issue by refreshing the data sources in Power BI Desktop before publishing. This can help to ensure that any changes or updates to the data sources are properly integrated into the report, and may help to prevent corruption issues.

If neither of these solutions work, you may need to seek further assistance from Microsoft support or the provider documentation for your data sources to identify the root cause of the issue and implement a corrective action.

[edhans]

Are you using the latest version of Power BI Desktop - currently March 2023? I would use that and retry. then we can dig deeper to see what the issue is.

[Pujoni]

Yes, I am using the latest version

[edhans]

I would test it this way.

1. Save a copy of the PBIX.
2. Delete one of those tables and publish.
3. Keep doing that until it works.
4. Once you figure out which one was causing it post that code here and let's see if we can figure out what the issue was.

You could also make a new connection for that table and copy the M code into it, then load that. It will delete any measures you have stored in that table, so move them first. 

[Pujoni]

Great idea! The only data source that didn't work was the one coming from Sharepoint. It's a folder in Sharepoint documents, and when I query it, I combine all the .xlsx files from the folder. As mentioned before, there are no errors in the Desktop version, and through the connection manager, I see that this query is online. I wonder what happened with this one?

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.

I also ran the query on different accounts to ensure there was nothing different.

[edhans]

It looks like it is telling you the files in SharePoint are corrupted somehow. What kinds of files are those? CSV, XLS, XLSX?

If XLS, try converting them to XLSX. I've seen more and more problems over the years with XLS files.

If another type, just try opening and resaving. There could be a small corruption that Power BI Desktop doesn't care about but the service does.

Again, you could try the same type of process of elimination. Remove all but a few files from SharePoint temporarily. Refresh. If it works, add a few more files back. Keep doing this until if fails. You should narrow down the file(s) that are causing the problem.

[Pujoni]

The files are .xlsx

I changed the source to another Sharepoint, but the error persisted, so I used power bi on another computer and the error started to appear on the Desktop version as well. Which is strange, because on Machine 1 it loads without error through the Desktop, on Machine 2 it shows the error!

I'm testing each file to see if I can find a different one, but so far all I've tested come up as "corrupted".

[Streamline]

I have the same issue. Did you find a solution?