You are viewing limited content. For full access, please sign in.

Question

Question

arithmetic operation resulted in an overflow

asked on June 30, 2015

I'm getting this error when running a lookup via an ODBC driver. No details are reported in either Workflow error logs or elsewhere.

Both Workflow and the ODBC driver in question are 64-bit. Workflow version is 9.2.0.167 (designer).

One odd thing I noticed is that table names appear twice in the dropdown list in Workflow. See the attachment.

I did some Google searches and found that this is a .NET error that might occur if an integer value is too large (link). Although I can't think of why that would be an issue here.

Has anyone seen this before? 

error.PNG
error.PNG (20.67 KB)
0 0

Replies

replied on June 30, 2015

Can you check the Activity Errors.log in the Workflow Admin Console? It should have the error with more details.

What value are you passing in?

0 0
replied on June 30, 2015 Show version history

Hi Miruna,

There isn't anything in the activity errors log. That's the first place I looked.

I'm passing a numeric value (71104, which is the invoice number), but I tried other values and got the same error.

Custom query activity also gives the same error with this query:

SELECT *
FROM Invoiceline
WHERE refnumber = '71104'

EDIT: Other troubleshooting I tried --

I'm able to query the third-party database using this ODBC driver if I hook it up to SQL Server as a linked server. So I know that it works fine. Only Workflow is having this issue.

0 0
replied on July 1, 2015

So where do you see the error then?

0 0
replied on July 1, 2015

It is reported in Workflow Designer when I test the query, and also in the messages tab when the instance terminates.

0 0
replied on July 1, 2015

If it's in the instance details, then it has to be in one of the logs in the WF Admin. Could you open a Tech Support case and attach the contents of the Logs folder?

0 0
replied on July 1, 2015

I thought so too but the logs don't contain anything recent. I'll open a case.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.