'ExecuteStatement finished with operation state: ERROR_STATE'.

[sxa445]

I've been getting an error recently which I have not been able to find any useful information online for. I am pulling data from a table going back to 2020 to current date. The Alteryx workflow use to take about an hour to run in the past but recently it is taking more than 4 hours to run and I also get the following error which I can't quite determine the root cause for: Error running PreSQL on "NoTable": [Simba][Hardy] (35) Error from server: error code: '0' error message: 'ExecuteStatement finished with operation state: ERROR_STATE'.

I am not sure if this is a data limit issue.

In the Alteryx Workflow, the error usually occurs at the creation of this Write In-DB/table tool. We have limited amount of data to try to determine the root cause of the issue but the error still happens randomly somedays and other days the workflow runs without errors. 

Because the workflows runs fine somedays and runs into this error someday, I can't tell if this is related to a connection issue. 

Has anyone encountered or read about this issue before? If so, can you please help me as I am in a time crunch to fix this issue. Thank you so much in advance for your time and consideration. 

[simonaubert_bd]

@sxa445Usually when I have this error, it comes from an ODBC driver configuration issue, so it always crashes.
However, what would be needed to help you :

indb configuration

odbc driver configuration

the whole error message

Best regards,

Simon

[sxa445]

@ simonaubert_bd Thanks for your response. Here is the whole error message: 

Executing PreSQL: "CREATE TABLE `AYX230706bfc5754c1849e70234c181aaeeba7dff` AS SELECT `InvoiceNum_o`, `InvoiceLineNum`, `InvoiceDate`, `Original..." : [Simba][Hardy] (35) Error from server: error code: '0' error message: 'ExecuteStatement finished with operation state: ERROR_STATE'.

Error running PreSQL on "NoTable": [Simba][Hardy] (35) Error from server: error code: '0' error message: 'ExecuteStatement finished with operation state: ERROR_STATE'.

I am also attaching images of indb configuration, odbc driver configuration and screenshot of the workflow configuration. Please let me know if you require additional information or further clarification. 

[simonaubert_bd]

Hello @sxa445 

Thanks

-on your indb configuration, there is a "write" tab with the most important informations here (so that I can see if you use ODBC or not, this is the part used by the write in db tool)
-for ODBC, it's the DSN configuration. What you show here is a "sample" with only default configuration. And in this confuguration, the advanced settings is precious.

Best regards,

Simon

[sxa445]

Hi @simonaubert_bd,

I am attaching new files, let me know if this is it. Thank you

[simonaubert_bd]

Hello @sxa445 
I checked my own ODBC configuration. Here what I found :
-it's the same configuration

-your ODBC driver is quite different.

You're supposed to use

which is the only one officially supported by Alteryx.

Best regards,

Simon

[sxa445]

Hey  @simonaubert_bd,

So I deleted the my previous Simba Hive Driver x64 for Alteryx 2.1.7.1010 for the driver you suggested and now this is the new error that I get. 

Connect In-DB (319) Error SQLDriverConnect: [Simba][ThriftExtension] (14) Unexpected response from server during a HTTP connection: SSL_CTX_load_verify_locations: bad decrypt; bad decrypt; bad decrypt; bad decrypt; bad decrypt; bad decrypt; bad decrypt; bad decrypt; bad decrypt; bad decrypt; bad decrypt; bad decrypt; No such file or directory; no such file; system lib.[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed

[simonaubert_bd]

Hello @sxa445 

This errot is related to your ssl certificate. Have you checked your SSL Options for your DSN? Maybe the certicate path is empty? (and can you do a screenshot of the ssl options please?)

Best regards,

Simon

[sxa445]

Hey @simonaubert_bd,

I am attaching a screenshot of the SSL Options settings as it is right now. 

[simonaubert_bd]

Hello @sxa445 

SSL is disabled on your screenshot, I think you should enable it and select the path of your certificate.

Best regards,

Simon