Microsoft Dynamics AX (Archived)

Unbalanced X++ TTSBEGIN/TTSCOMMIT

(0) Share

Report

Posted on by Community Member

Dear All,

Today, I faced the below error:

1738.1.png

Though the error can be resolved by running a job as provided in the below link:

https://community.dynamics.com/ax/b/axaptavsme/archive/2013/08/29/error-an-unbalanced-x-ttsbegin-ttscommit-pair-has-been-detected-in-ax

Is there any way in AX to know which block code of had thrown this error other than debugging?

Thanks in advance!!!

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Hossein.K 6,648 on at

Like (0)

Report

RE: Unbalanced X++ TTSBEGIN/TTSCOMMIT

Hi Jaya Rajan ,

Check all code for form or class that all of ttsBegin must be Commit or Abort .

to resolve this error this TTS level should be ZERO, Run this job to get rid of that error, this job will find the tts level where its greater than zero and make it zero by calling TTSABORT

static void AxResetTTS(Args _args)

{

while (appl.ttsLevel() > 0)

{

info(strfmt("Level %1 aborted",appl.ttsLevel()));

ttsAbort;

}

}

Was this reply helpful? Yes No
Suggested answer

Hossein.K 6,648 on at

Like (0)

Report

RE: Unbalanced X++ TTSBEGIN/TTSCOMMIT

Hi Jaya Rajan ,

Check all code for form or class that all of ttsBegin must be Commit or Abort

to resolve this error this TTS level should be ZERO, Run this job to get rid of that error, this job will find the tts level where its greater than zero and make it zero by calling TTSABORT

static void AxResetTTS(Args _args)

{

while (appl.ttsLevel() > 0)

{

info(strfmt("Level %1 aborted",appl.ttsLevel()));

ttsAbort;

}

}

Was this reply helpful? Yes No
Suggested answer

Vilmos Kintera 46,149 on at

Like (1)

Report

RE: Unbalanced X++ TTSBEGIN/TTSCOMMIT

You would have to repeat the business functionality after freshly opening the client to see if you are able to reproduce the unbalanced TTS problem. We are sure that this is due to an incorrect customization. You could try adding infolog to the code involved in the business process which caused the above error, to tell what is the current TTS level before and after the ttsbegin/commit calls, so you could identify where could it be getting wrong.

Obviously only do such code changes in a QA/Test environment.

Other than this, the most reliable way to identify the issue is to debug it (once you could reliably reproduce it).

Was this reply helpful? Yes No
Suggested answer

Sukrut Parab 71,699 Moderator on at

Like (0)

Report

RE: Unbalanced X++ TTSBEGIN/TTSCOMMIT

Its just very difficult to say without debugging. Debug code in your process line by line and see which block of code is throwing this error.

Was this reply helpful? Yes No