Question

I have created an AIF service in dynamics AX 2012, when I tested it by calling the entrypoint method from a job, it worked fine, but when it is deployed en the calls are comming from the soap UI, it crashes inside with an error: "Unhandled esception".

While debugging I found out the unhandled exception is thrown inside my catch clause of my try catch statement.

It gets inside the catch because the method I am calling inside the try clause thows an error.

So does anyone know why I can catch thrown error when I am running the code on client using the job, but can't catch it while it runs in CIL on the server and the service is called from SoapUi?

Was it helpful?

Solution

Solved,

AIF has one big transaction somewhere deep in the core code and an own try catch.

So when you throw an error inside AIF sevice it is going to abort the outer transaction and go to staight to the AIF catch clause, skipping all others.

That's why I couldn't catch it. Solution could be to commit AIF transaction, run your code and before return begin new transaction.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top