OLE DB or ODBC error: type mismatch (exception from HRESULT: 0x80020005 (DISP_E_TYPEMISMATCH))

[Virtual_Ames]

Hello,

I have a report that has been running just fine for the last few weeks.  Nothing has changed about the report.

Upon attempting to refresh the data today - it does not work.  If gives me this error:

     OLE DB or ODBC error: type mismatch (exception from HRESULT: 0x80020005 (DISP_E_YTPEMISMATCH))

Any ideas about what is going on and how to address this?

Thanks,

[Anonymous]

Hi,

Reason for this error is that the content of your data has changed.

It means for example that you have a text in a number formatted column.

For example :

* you have a column in your report who also only containes number values and your data type is also number.

 When refreshing your data if this column now contains a text value, then you will receive this error.(This is the reason for mismatch)

#example;

   row      column a 

      1        10

      2        22

      3        35

      4        Ranking

You can solve this with Power Query by sorting and deleting this unwanted rows and your report will refresh again.   

[Anonymous]

Hi, What is your data source?

[Anonymous]

I got this error when I appended the data from CSV and Data from excell.

[Anonymous]

I'm getting this error from a sharepoint excel. I've formatted all columns in the offending table as text and deleted all relationships..still there. 

[Chris13]

I was able to resolve this error, it turns out that when I was merging 2 Excel tables with same columns, the columns themselves didn't get the correct matching types.   Once I changed the columns to match it worked properly.

[TimonMeyer]

Hi,

had this error a couple of times...was able to solve it everytime when I checked the source. In the last case my Excel table (which I feed manualy) produced a few empty rows at the end refering to no data...deleted them and everything was fine.

[Greg_Deckler]

Is this in the Service, Desktop or gateway?

[Virtual_Ames]

Desktop.....

[arify]

Can you please give us some information about your query and the failure? Sending a frown with traces would be very helpful.

(Just a guess, are you connecting to an Analysis Services Database?)

[Virtual_Ames]

Yes, frown with data has now been sent.

Sources are Sharepoint List and OData....

[spiderrob]

I'm seeing exactly the same error. Report was running fine? Using Power BI desktop and source is a SQL server database.

[Virtual_Ames]

Sorry to hear that.  You could open a ticket, but here are a few suggestions.

Run the refresh in PowerBI.com - it will fail, but the error reporting is better (? why ? I don't know) - so if you look at the dataset in the "schedule refresh" area, you will see the failure notification -  if you expand that, it may identify the column that is causing the problem.  Then you step through your query (and rebuild it if necessary).

If that error does not show, go to PowerBI desktop and get into the data view - then look at the fields list and start by inspecting any columns that are flagged, then look for items that are have date format. Hypotheis is that a new value showed up in your data that caused PowerBI to "change it's mind" about the TYPE - moving from Text or Date Type to "any" or "text". 

May need to rebuild those. 

I do not think this was a matter of someone changing the format in the source - so the cause of the problem is not known - one day it was working, the next it was not - so I would not advise going down that path as a first step - unless you control everything and have easy access.

Good luck.

[Syndicate_Admin]

your suggestion to run the refresh in PowerBI.com was very helpful to me. Thanks also for the detailed description where to find the error description in the power BI service. Turned out for me that a whole different column threw me out than I wuold have expected and was trying to change. Thanks a lot

@Syndicate_Admin

[chabib]

Just had the same error and solved it by duplicating my table in the Query Editor, deleting the original table and renaming the copy to the original's name.. Hope that helps

[David_Castr]

This works for me, thanks!

[Anonymous]

Thank you very much.

[gDae]

It did not help. I lost my charts in the process because they were built on the original.

[gDae]

It didn´t help. I just lost all my charts and need to start building from scratch! 

[jocy]

It worked thank you very much!

Too bad I had to copy all my old measures again and change the origin of the dependant queries, but it helped a lot 🙂

[KH11NDR]

A date field was giving me probs, it loaded from SQL as text, so I changed it to Decimal number and then then tried to create a Date field, But I still got that message, so I left it as a Decimal number and created  four seperate columns, Year, Month, Day and then concateated them together and the query reloads without the error.  Hope that helps someone.