Error OLE DB o ODBC: [DataSource.Error] ODBC: SUCCESS_WITH_INFO [22008]

[dgianni]

Good morning

Diego from Italy here, hi guys

I see this unusual error on my BI, it looks like something went wrong on the download of data direct from OLE ODBC, the error shows an error of invalid data like "Errore OLE DB o ODBC: [DataSource.Error] ODBC: SUCCESS_WITH_INFO [22008] [IBM][Programma di controllo ODBC di System i Access][DB2 per i5/OS]SQL0181 - Valore data, ora o registrazione data/ora non valido..", but nothing has changed on my side or my DB data type, there is also no dirty data inside my system that could justify this error (I checked thoroughly).

Can you please verify this issue?

Thank you so much,

Diego

[dgianni]

I found the error finally, it was in my DB in a variable i used as parameter,

Thank you everyone!

Diego

[dgianni]

I do not see any errors in my DB... All the same as many years from now.

Do you know how can i update ODBC driver version?

[v-achippa · Accepted solution]

Hi @dgianni,

The error likely means that the ODBC driver found at least one value in your data that is not a valid date or time. This can happen even if the data has not changed. Please follow below steps:

Go to Power Query Editor in power bi, find the date/time columns, open the Advanced Editor and add this below step:

let

    Source = ...,

    Cleaned = Table.TransformColumns(

        Source,

        {

          {"order_date", each try Date.From(_) otherwise null},

          {"ship_time", each try Time.From(_) otherwise null},

          {"timestamp_column", each try DateTime.From(_) otherwise null}

        })

in

    Cleaned

This tells the power bi to ignore any invalid bad date/time values and replace them with nulls, so the refresh completes successfully.

If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it! 

Thanks and regards,

Anjan Kumar Chippa

[v-achippa]

Hi @dgianni,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue worked.
If my response addressed, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

Thanks and regards,

Anjan Kumar Chippa

[v-achippa]

Hi @dgianni,

We wanted to kindly follow up to check if the solution I have provided for the issue worked.
If my response addressed, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

Thanks and regards,

Anjan Kumar Chippa

[Akash_Varuna]

Hi @dgianni  I think the driver found invalid or out-of-range date/time values, like 0000-00-00, in your data. Check and clean date fields in your source query to handle or exclude these values. Also, ensure Power BI and the ODBC driver have matching regional and date format settings. Updating or rolling back the ODBC driver version may help if the issue started after an update.

[v-achippa]

Hi @dgianni,

Thank you for reaching out to Microsoft Fabric Community.

Thank you @Akash_Varuna for the prompt response.

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the super user resolved your issue? or let us know if you need any further assistance.
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.

Thanks and regards,

Anjan Kumar Chippa