ODBC driver causes failed refresh of dashboards in Power BI

[Michael11l]

We used clickhouse db on our server and use data from there in power bi, but we are not able to refresh it everytime, it refreshes around 50%of the time successfully.
To connect to this data we use gateway from microsoft and odbc driver from CH.
Microsoft checked all logs in their services and didn't find that something was wrong on their side and they advised to contact you.
The message error is:
{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"ERROR [HY000] Incomplete input stream, expected at least 17 more bytes"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table: Deposits and users data.
FYI @[email protected] (Sante)
ClickHouse Case #00013258

[brucezzchen]

Our situation is the same, and the error happens randomly

[SpencerTorres]

Similar error message here #419

[ashish135906]

Same happening with us too. @mshustov Are issues being resolved actively?

[mshustov]

To start the investigation, we need more information to reproduce the problem:

1. ClickHouse and driver versions
2. OS
3. query log for the period when the problem happens
4. the driver logs for the period when the problem happens. The logging might be enabled via DriverLog and DriverLogFile DSN parameters:
   

   clickhouse-odbc/packaging/odbc.ini.sample

   Lines 36 to 37 in 2f55d01

   	# DriverLog = yes
   	# DriverLogFile = /tmp/chlickhouse-odbc-driver.log

5. DDL for a query target table

[abdrakhmash]

Same problem, but locally data load works and in BI online service refresh fails with incomplete input stream.

[mshustov]

locally data load works

@abdrakhmash could you elaborate? Do you mean that in your case everything works with PowerBI Desktop?

[abdrakhmash]

everything works with PowerBI Desktop

Yes, PowerBI desktop on my computer loads data from clickhouse (~180 million rows) and I can work with them. But refresh attempt in online service after publishing results in

Data source error: {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"ERROR [HY000] Incomplete input stream, expected at least 4 more bytes"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table: events.

[lsilvestrepereira]

same here, the error is happening randomly on several dashboards every day. When this error happen I refresh the dashboard again without changing anything and the error does not occur. It's really random

[lsilvestrepereira]

Example 1:

{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"ODBC: ERROR [HY000] I/O error: Bad address"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"ClickHouse"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"{"server":"[...]","port":8443}"}},{"code":"Microsoft.Data.Mashup.ValueError.OdbcErrors","detail":{"type":1,"value":"#table({"SQLState", "NativeError", "Message"}, {})"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table: vw_workorder_scheduled.

Example 2:

{"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"ODBC: ERROR [HY000] I/O error: Bad address"}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourceKind","detail":{"type":1,"value":"ClickHouse"}},{"code":"Microsoft.Data.Mashup.ValueError.DataSourcePath","detail":{"type":1,"value":"{"server":"[...]","port":8443}"}},{"code":"Microsoft.Data.Mashup.ValueError.OdbcErrors","detail":{"type":1,"value":"#table({"SQLState", "NativeError", "Message"}, {})"}},{"code":"Microsoft.Data.Mashup.ValueError.Reason","detail":{"type":1,"value":"DataSource.Error"}}],"exceptionCulprit":1}}} Table: dim_teams