Error executing code: <object name>object does not have method 'new' in Batch Job

(0) Share

Report

Posted on by Freya Tan

935

Hi,

I have a custom class which extends runbasebatch. The class I created have a new method which will initialize some variables. I have another classes which extends this class. Now, when I manually run the child class, no errors appears and it works as expected. But when I ran it as batch job, an error appears. The error log is: Error executing code: SomeObject object does not have method 'new'.

I tried the solution from this link: http://dynamics-ax-prasankumar.blogspot.co.nz/2012/07/ax2012-error-executing-code-object-does.html but still no luck.

Any ideas?

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

dolee 11,279 on at

Like (1)

Report
Copy link

Link copied!

Batch job runs in CIL, have you do a "Generate incremental CIL" or "Genreate Full CIL" before trying to run it as batch job?

Was this reply helpful? Yes No
Freya Tan 935 on at

Like (0)

Report
Copy link

Link copied!

yes i did.

Was this reply helpful? Yes No
dolee 11,279 on at

Like (0)

Report
Copy link

Link copied!

Hmm...try:

- Compile your custom class and its child classes one by one. (Have seen discussion about an issue that sometimes compilation error are not reported when compile multiple objects)

- Compile forward from the RunBaseBatch class

- Generate full CIL (Just to be sure)

Hopefully that'll do it for you.

Was this reply helpful? Yes No
Suggested answer

Tommy Skaue Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Batches run as CIL, so compiling CIL is a requirement, as dolee says. :-)

Just as a sanity check, you could make sure the new method exists in the source-folder located under:

C:\Program Files\Microsoft Dynamics AX\60\Server\YOUR_INSTANCE\bin\XppIL\

Search for a file named YourClassName.new.xpp.

Requires server side breakpoints to be enabled on the AOS though:

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

Like (0)

Report
Copy link

Link copied!

I don't know if it's relevant to your case, but you could get into troubles if the constructor doesn't have correct access modifier (public/protected...).

Let's say you have a private constructor and call it via reflection. AX reflection API ignores access modifiers and will call it without issues. But .NET reflection will use BindingFlags.Public and will fail to find any constructor.

Was this reply helpful? Yes No
Majid Hafeez 40 on at

Like (0)

Report
Copy link

Link copied!

I have faced the same issue and it resolved by running CIL Incremental Thanks, Dominic Lee

Was this reply helpful? Yes No