What is causing this error message? Again, there is not a syntax error, nor is the statement actually "timing out", as there is a 6000 second timeout limit, and this error occurs instantly.
I see there are other posts over the last year with this issue, none of which seem to offer any solution.
Plz advise, thanks.
More detail: this bot uses a nested loop: the inner loop iterates through a datatable, for each row composing a SQL Insert statement using row data variables, and then stores the statement into a string variable $sSqlInsert$. For each iteration it then combines the sql inserts into one long string: $sSqlTransaction$ (SqlTransaction = SqlTransaction+SqlInsert). when the inner loop finishes, the outer loop composes another SQL Update statement $SqlUpdate$, and concatenates that with $SqlTransaction$ (SqlTransaction = SqlTransaction+SqlUpdate).
Then I attempt to Start Transaction, run the whole statement $sSqlTransaction$ in a single Database INSERT/UPDATE/DELETE action. and then End Transaction.
This has been working successfully for weeks, and only stopped working when switching to a different database.
In my attempts to isolate the problem, after validating my sql statements, I have also now tried skipping all the above concatenation, and only running a single insert statement, and that also is giving the same error.
Hi @Andrew Yankee ,
You mentioned that you have switched to a different database correct?
Would you be so kind as to tell us which Database you are using now?
Also, since the code is dynamically generating the queries, I would recommend adding message boxes, or logging the queries csv so that you can cross check and validate whether the syntax is wrong.
Also, you might want to check if there are any access issues that prevent you from interacting with the database.
If you are certain that nothing is wrong, then I'd recommend opening a case(requires partner access) with Automation Anywhere and let the product experts have a look at it.
HI @Ashwin A.K (TheCodingTheory),
Thanks for your response.
I am using an Azure database.
I have indeed been able to verify the accuracy of everything, except to ensure all access. (Waiting for a response from my IT department).
"Also, since the code is dynamically generating the queries, I would recommend adding message boxes, or logging the queries csv so that you can cross check and validate whether the syntax is wrong."
-This is the method I used to verify the statements, which I then copied and successfully ran directly through Microsoft SSMS.
I guess, even IF I am being restricted by a permissions issue, I still see this as a bug because it is giving me the incorrect error message. There are no syntactical errors or timeouts occurring but that is the error message that is generated.
However, I should be able to ascertain that I have all required permissions today, I have been waiting for a response from our DBA team.
I simultaneously have a ticket open with Automation Anywhere.
Hopefully this will be resolved today.