Deadlock in BatchRun.serverGetTask()

(1) Share

Report

Posted on by Community Member

how to resolve the following issue in AX

Object Server 01: Microsoft.Dynamics.Ax.Xpp.DeadlockException: Exception of type 'Microsoft.Dynamics.Ax.Xpp.DeadlockException' was thrown.

at Microsoft.Dynamics.Ax.MSIL.Interop.throwException(Int32 ExceptionValue)

at Microsoft.Dynamics.Ax.MSIL.cqlCursorIL.UpdateAll(IntPtr table)

at Dynamics.Ax.Application.BatchRun.serverGetTask(Batch batch, String serverId) in BatchRun.serverGetTask.xpp:line 27

at BatchRun::serverGetTask(Object[] )

at Microsoft.Dynamics.Ax.Xpp.ReflectionCallHelper.MakeStaticCall(Type type, String MethodName, Object[] parameters)

at BatchIL.startTask()

at BatchIL.threadFunc(Object threadArg)

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

Umesh Pandit 9,315 User Group Leader on at

Like (0)

Report

check this tech.alirazazaidi.com/dynamics-ax-2012-xpp-errorexception

community.dynamics.com/.../97953.aspx

Was this reply helpful? Yes No
Martin Dráb 237,963 Most Valuable Professional on at

Like (0)

Report

Are you able to reproduce the issue? If so, activate SQL server tracing for deadlocks - it will tell you which resources were locked and by which queries. Otherwise you will have to analyze source code and try to guess what happened, which is often very difficult.

By the way, do you know what deadlock is?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

[quote user="UMESH PANDIT"]

check this tech.alirazazaidi.com/dynamics-ax-2012-xpp-errorexception

https://community.dynamics.com/ax/f/33/t/97953.aspx

[/quote]

That's a different error in those links. We are also getting that same specific error from the OP. There are no deadlocks being detected in SQL Server at the same time, but these errors cause the Dynamics AX jobs to terminate without being flagged as an error.

Was this reply helpful? Yes No
Esther Mulijono 435 on at

Like (0)

Report

Hi All,

Have anyone found solution for this problem?

We faced the same issue, just slightly different stack trace

Object Server 03: Microsoft.Dynamics.Ax.Xpp.DeadlockException: Exception of type 'Microsoft.Dynamics.Ax.Xpp.DeadlockException' was thrown.

at Microsoft.Dynamics.Ax.MSIL.Interop.throwException(Int32 ExceptionValue)

at Microsoft.Dynamics.Ax.MSIL.cqlCursorIL.UpdateAll(IntPtr table)

at Dynamics.Ax.Application.BatchRun.serverProcessFinishedJobs(Boolean forceProcessing, Boolean ) in BatchRun.serverProcessFinishedJobs.xpp:line 166

at Dynamics.Ax.Application.BatchRun.serverProcessFinishedJobs(Boolean forceProcessing)

at BatchRun::serverProcessFinishedJobs(Object[] )

at Microsoft.Dynamics.Ax.Xpp.ReflectionCallHelper.MakeStaticCall(Type type, String MethodName, Object[] parameters)

at BatchIL.checkFinishedJobs(Boolean forceProcessing)

at BatchIL.threadFunc(Object threadArg)

happened when we start the AOS

and the AX client also always crashing so we cannot open AX.

Was this reply helpful? Yes No
Suggested answer

Vilmos Kintera 46,149 on at

Like (0)

Report

Did you have batches running (executing status) when you have stopped the AOS? Have you deployed code customizations? How are you releasing your changes (preferred: AX modelstore, with a successful full application compile and full CIL)? Is your AX AOS using the latest kernel hotfixes for the version that you are using?

Make sure you verify all of the above.

Was this reply helpful? Yes No