Devart Forums

MyDirect.NET version 4.85.35
Visual Studio 2008 SSIS
[ADO NET Destination [294]] Error: An exception has occurred during data insertion, the message returned from the provider is: Object reference not set to an instance of an object.
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "ADO NET Destination" (294) failed with error code 0xC020844B while processing input "ADO NET Destination Input" (297). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure.

Could you please send me a small test project (or provide us with the steps we should follow) and the script that creates the tables and fills them with data? We will try to reproduce the error.

FYI, I upgraded to version 4.85.36.0, but no improvement. Thanks.

I sent you a small test project. Did you receive it? Thanks.

Thank you for your letter. We could not reproduce the mentioned error. Please provide me (alexsh at devart.com) with the steps for reproducing this issue, maybe even with screenshots. That will help us locating the trouble.

Hi Alex,
I CC'd you on an email to [email protected]. It includes a screenshot. Thanks.

The problem is inside the SSIS.

The quoting character is hard-coded to " and cannot be changed. We will investigate the possibility of bypassing this problem.

As a hotfix you can manually append ",ANSI_QUOTES" to the value of "sql_mode" variable of your MySQL server instance.

Thanks. I will use that workaround. It fixes the "Object reference not set to an instance of an object" error when targeting a version 5.1.23 server.

I upgraded to dotConnect for MySQL version 5.0.12.0 and the workaround no longer fixes the problem. Has the workaround been tested using the new version? I will send you my project.

Thanks,
Al

Thank you for the report. We have reproduced the issue and now we are investigating it.
This time error is more serious, so unfortunately no timeframe can be provided. We will notify you about the results.

Any progress on this issue yet?

The described problem is fixed in the current build.

Thanks Andrey. I installed the latest build and it works for me now (using the 'ANSI_QUOTES' workaround).