ExecuteObject Failure

Hi. Update on this

Still running with original solution using ExecuteObject as we have some dependancy on package variables that get used. But wanted to let you know that with release.25 we still have the odd Out Of Bounds Message which then causes the parent package to think the child package failed. While I am here. May I also ask what the execution % equates to?

While I am here. May I also ask what the execution % equates to?

It is a percentage of time taken to execute specific action within the package.
eg whole package is 100% = Action 1 (30%) + Action 2 (70%)

Regarding the issue, you reported we will create a special build for you later today

Thanks Mike. Whilst I haven't really dug into it my query about the execution % was because it didn't look like it added up and at one point I had 3 x 50% within the one package and that's when I wondered if it had anything to do with the error I see. But as I have said, I haven't really look at it in detail to verify what I thought I saw.

have a good weekend

cheers

Hi.

I am sorry that following up on this specific topic has fallen so far behind. The issue is still relevant to us and occurs on a semi-frequent basis but at this stage we still have not isolated what the root cause is.

The symptom is an Index Out of Bounds (-1) error message that appears in the log file and the return result from the package being executed by the ExecuteObject() function returns a failed return code. However, our logging and checks of the called package indicate it has ended successfully.

From an internal code perspective is it possible that logic in the ExecuteObject() function is either expecting a list/array or is attempting to output one which may result in an out of bounds exception?

Knowing what that may be my help us determine what the cause may be.

To be honest we last touched on this 10 months ago (again my apologies) but I can't recall if a debug version of AETL was shipped. in either case it has probably expired in any case and I know we have done some updates since then.

Mike also mentioned about calling a stored procedure to create a queue entry rather than using a trigger file and using the ExecuteObject() function. We are working on a couple of other projects and haven;t had a chance to look at integrating this approach and so would like to see if we can resolve the false-positive return and array error if we can.

thanks in advance

We will create another debug version for you

Thanks. Was wondering if this was still on your radar?