DataSource Error in ODBC Connection

[Xarsas]

Hi All,

I've run into an issue with PowerBI drawing a scheduled refresh of our on premise server. The connection is fine, and data has been working flawlessly for abour a year and a half, but something must have either changed on the data table or the on premise gateway a while back.

I couldn't really find a way in the online interfce to pinpoint the problem so I tried to import data from each of the tables in the original connection seperately. I have now narrowed the error down to one table.

The error I'm receiving now is as follows :

DataSource.Error: ODBC: ERROR [HY000] [Elevate Software][DBISAM] '-6406.0' is not a valid timestamp
Details:
DataSourceKind=Odbc
DataSourcePath=dsn=ODBC-Data
OdbcErrors=[Table]

As far as I can see in the query editor the colums with dates in are all correctly classified as such by PowerBI so I'm not sure what is causing the error. Is there some way to see which column in specific is causing the error?

Thanks

[Anonymous]

Hi Guys,

I'm having a different issue, whereby i unble to access ODBC from Power Bi desktop app in my server.

But i test the connection, able to establish.

only via power Bi can't.

Urgently need help

Thanks.

[v-yueyunzh-msft]

Hi , @Xarsas 

According to your error information provided, it seems that you have encountered an ODBC related error related to the ODBC connector: ERROR [HY000] [Elevate Software][DBISAM] '-6406.0' is not a valid timestamp, you are using an ODBC data source as a connection to associate with your local data source and Power BI, the problem does not seem to be related to the direct connectivity between Power BI and ODBC, Related to the internal error of ODBC, if it is convenient, you can try to use the ODBC connector to create a new connection to this local data source, check whether the connection can be successful, if possible, you can update the data source path in the source desktop connection of the report, and use this new ODBC as the link instead.

Thank you for your time and sharing, and thank you for your support and understanding of PowerBI! 

Best Regards,

Aniya Zhang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

[Xarsas · Accepted solution]

Hi @v-yueyunzh-msft 

Thanks for the reply.

A new data connection has the same issue. I created a second ODBC connection in Windows to test as well and that had the same issue.

I can't find a place to see where exactly Power BI has the issue though, as in which column or row to narrow down the problem finding. This connection acceses a database from an ERP system, and the table is operating fine in that system so obviously sometime in the last two weeks some data field was changed/updated in a way that is casuing Power BI to hit a snag. 

I'll have to trawl through the audit trails to find whatever caused it then, was just hoping there was a way to pinpoint in Power BI.

Regards,