Microsoft Dynamics AX (Archived)

Exception handling with Web Service (not catching)

(0) Share

Report

Posted on by Munib

2,500

Hi,

After all these years I have encountered this problem where exceptions were handled differently.

Martin wrote about X++ and CIL.

http://dev.goshoom.net/en/2013/09/exception-handling-with-x-and-net-interop/

I wrote a custom web service with try/catch statements to see how it behaves.

After debugging I found it errored with unhandled ErrorException.

The calling .NET console app catches the error as System.ServiceModelCommunicationException. This has the first error.

The fact that AX does not respect the "catch" concerns me. What this is telling me is that I have to make my web service much more granular. Also, catching the errors in the calling application and dealing with it.

I wanted to see if others are experiencing the same or if any comments.

*This post is locked for comments

All responses (6)

Answers (2)

Community Member Microsoft Employee on at

Like (0)

Report

RE: Exception handling with Web Service (not catching)

I would suggest using int ttsBeginCommitsFound; instead of boolean ttsBeginCommitFound;. Count found ttsLevel and at the end replace

if (ttsBeginCommitFound)

{

ttsBegin;

}

with

while (ttsBeginCommitsFound)

{

ttsBegin;

ttsBeginCommitsFound--;

}
Martin Dráb 230,445 Most Valuable Professional on at

Like (0)

Report

RE: Exception handling with Web Service (not catching)

I'm already discussing it with Tam Ngo in another answered thread, so let's not pollute the forum with duplicate questions.

By the way, Tam Ngo, please don't mark your questions as suggested answers.
Community Member Microsoft Employee on at

Like (0)

Report

RE: Exception handling with Web Service (not catching)

Hi Ahmed,

It works, but not in batch
Munib 2,500 on at

Like (1)

Report
RE: Exception handling with Web Service (not catching)

Thanks to both that have responded. Below is a simple extract of what I am intending on doing.

Hope it helps someone out there.

boolean ttsBeginCommitFound; //AIF does ttsbegin/ttscommit around the whole web service transaction. Commit it here while (appl.ttsLevel() > 0) { ttsCommit; ttsBeginCommitFound = true; } try { ttsBegin; //do my thing here ttsCommit; } catch { //log my error and do my exception handling } //AIF does ttsbegin/ttscommit around the whole web service transaction. Do the Begin here if (ttsBeginCommitFound) { ttsBegin; }
Verified answer

Vilmos Kintera 46,149 on at

Like (1)

Report

RE: Exception handling with Web Service (not catching)

It is TTS-related like Martin suggested, and not so long ago I've linked one possible solution here, similar to what the link above is suggesting:

community.dynamics.com/.../225090

Take a look and see if it helps to resolve your issue. Also I always like to tick the box for sending the AIF fault messages to the caller application in the port configuration, or wrap the error in a response data contract.
Verified answer

Martin Dráb 230,445 Most Valuable Professional on at

Like (1)

Report

RE: Exception handling with Web Service (not catching)

Check the transaction level - you can't catch errors inside transactions and custom services seem to be wrapped in transaction.