Forum Discussion
Error when publishing Power BI report with multiple connections!
Yes, I am using the latest version
Community ChampionI would test it this way.
- Save a copy of the PBIX.
- Delete one of those tables and publish.
- Keep doing that until it works.
- 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.
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.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".