Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago
Solved

OLE DB or ODBC error: Type mismatch. (Exception from HRESULT: 0x80020005)

Hi,   I'm really struggling to understand the error I'm having and I really hope someone can help me.   In Desktop I'm using an ODBC Connection to access a number of different data sources. One o...
Need Help
Show and Tell
  • Anonymous's avatar
    Anonymous
    7 years ago

    Hi rocky09 ,

     

    I had a similar report set up on the Power BI Service that failed to refresh but provided me with a more detailed error. It turns out one of the fields contains string values when the ODBC connection was expecting date. When I checked the set up for the original data source the field in question was shown as a string so I'm not sure where the change occured.

     

    Luckily, in this instance, I think I'll be able to omit the field from the report as I don't think it's entirely necessary. Hopefully that will negate the issue.


    Thanks,

    MarkJames

Anonymous's avatar
Anonymous
Not applicable
7 years ago

Hi rocky09 ,

 

I had a similar report set up on the Power BI Service that failed to refresh but provided me with a more detailed error. It turns out one of the fields contains string values when the ODBC connection was expecting date. When I checked the set up for the original data source the field in question was shown as a string so I'm not sure where the change occured.

 

Luckily, in this instance, I think I'll be able to omit the field from the report as I don't think it's entirely necessary. Hopefully that will negate the issue.


Thanks,

MarkJames

Anonymous's avatar
Anonymous
Not applicable
6 years ago

I am sure this is to do with the latest power bi updates. I have models that I created in 2019 that are giving me this error and I have noticed that the data types you set originally seem to revert to text. 

 

 

Related content