Answered

Microsoft.Dynamics.Ax.Xpp.ErrorException "A parameter could not be serialized." when posting document

(0) Share

Report

Posted on by Community Member

Hello,

when posting a document (sales confirmation, purchase order) we get the following error message:

Microsoft.Dynamics.Ax.Xpp.ErrorException: Exception of type 'Microsoft.Dynamics.Ax.Xpp.ErrorException' was thrown.

at Dynamics.Ax.Application.SysOperationServiceController.runServiceOperation(Object[] parameters) in SysOperationServiceController.runServiceOperation.xpp:line 22

at SysOperationServiceController::runServiceOperation(Object[] )

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

at Dynamics.Ax.Application.SysDictClass.invokeStaticMethod(Object[] _params) in SysDictClass.invokeStaticMethod.xpp:line 26

at SysDictClass::invokeStaticMethod(Object[] )

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

at Microsoft.Dynamics.Ax.Xpp.PredefinedFunctions.runAsInvoke(String className, String staticMethodName, Object[] parms, Object[]& exportInfolog)

I have already compiled the whole application with complete CIL-generation aftwards, restarted the complete application server. Nothing helps. In the moment we have removed the check "Execute business operations in CIL" in the user options, then it's possible to post the documents. Has here anybody a tip for me would I could do to get rid of this problem?

Regards
Patrick

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (1)

Sort by

Martin Dráb 239,932 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

It seems that one of parameters of the methods is not serializable or the serialization fails, therefore the object can't be passed to a CLR application domain. What parameters do you use there?

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

Hello,

sorry for the late reply... The reports where the error occurred aren't modified, they run completely in standard. But the problem is solved now. Although several runs of complete compilation/CIL-generations couldn't solve the problems one compilation/CIL-generation must have done the trick, suddenly and without me doing anything to solve the problem it runs...

Thanks for your reply anyway!

Regards

Patrick

Was this reply helpful? Yes No
prateep 10 on at

Like
a
(0)

Report
Copy link

Link copied!

Could you please advise yor trick ? I have the same problem with you

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

Unfortunately I can't give you additional information. It was just that after one complete compilations with CIL-generations it worked surprisingly again, although several complete previous compilation & CIL-generation-runs couldn't solve the problem. So there wasn't anything what I did specifically to get this problem solved, it was just a "sufficient" number of compilations & CIL-generations.

Sorry that I can't give you a specific advise to solve this problem..

Regards

Patrick

Was this reply helpful? Yes No
Verified answer

Dick Wenning 8,705 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Patrick,

remove all cil files from the server bin directory

restart AOS and do full CIL

I have seen that sometimes CIL does not get updated correctly, sparely when removing a method.

also when a database is restored and the timestamp of x++ is older than the cil timestamp

does it happen for al users, or some of them

Was this reply helpful? Yes No
Community Member on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Dick,

As this problem just "disappeared" suddenly I can't verify if your reply would have solved this. But at least it's a good tip for future problems which also could be linked with the CIL.

Regards

Patrick

Was this reply helpful? Yes No