ViktorV wrote: ↑Thu 02 Aug 2018 14:28
Thank you for the information. We investigated the issue and found out the cause of the described behavior. In the case you are describing, SSIS uses the SQLExecDirect ODBC function to execute the query. According to Microsoft documentation
https://docs.microsoft.com/en-us/sql/od ... erver-2017 if the query has not affected any records will return the result SQL_NO_DATA (for the ODBC 3.x specification). Our driver and SSIS use the ODBC 3.x specification, however, in the described case, SSIS implements the behavior as ODBC 2.x . That's why, when the result of SQL_NO_DATA is received, the error "Error HRESULT E_FAIL has been returned from a call to a COM component" is returned.
In the next release of ODBC Driver for MySQL, we will add the possibility to force ODBC 2.x behavior.
You can use the night build of ODBC Driver for MySQL with this functionality at
https://devart.com/pub/dac/DevartODBCMySQL.exe
To solve the issue, please try to enable the "Force the ODBC 2.x behavior" checkbox on the Advanced settings tab in the configuration dialogbox of ODBC Driver for MySQL.
I will check it lets see will it work or not