Forum Discussion

Xarsas's avatar
Xarsas
New Member
3 years ago
Solved

DataSource Error in ODBC Connection

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 som...
Dataflow
  • Xarsas's avatar
    Xarsas
    3 years ago

    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,

     

v-yueyunzh-msft's avatar
v-yueyunzh-msft
Community Support
3 years ago

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's avatar
    Xarsas
    New Member
    3 years ago

    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,