CLR error in D365FO

(0) Share

Report

Posted on by Riyas ahamed F

1,215

Hi guys,

While a debugging its stopped in run method.

below error:

Can you tell me what it says that error ?

Thanks

I have the same question (0)

All responses (7)

Answers (3)

Riyas ahamed F 1,215 on at

Like (0)

Report

Additional information : while a importing excel sheet.

issue : The menu item with name mpimportdata could not be opened.

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

Like (0)

Report

Look at details of the $exception object (in the Locals windows when debugging).

By the way, the exception handling code makes little sense to me. It has no positive effect; it just makes your debugging harder by swallowing important information.

Was this reply helpful? Yes No
Verified answer

ergun sahin 8,826 Moderator on at

Like (0)

Report

It is a very common error and can happen for many reasons. You probably searched the internet and tested the solutions you saw.

I looked for 5-10 minutes to see if there was a general solution. There are different solutions, from the one that says "refresh" the menuitem in AOT to the one that says I uninstalled and reinstalled the Model.

You need to share the inner exceptions with us so that we can give more specific answers. Where you catch the error, instead of throwing an error again, you need to reach the details with a more meaningful code or as Martin suggested share the details of the exception object with us .

Was this reply helpful? Yes No
Verified answer

Leo Chen on at

Like (0)

Report

Do something like below, you'll get the details of the exception

https://docs.microsoft.com/en-us/dynamicsax-2012/developer/how-to-catch-exceptions-thrown-from-clr-objects

Was this reply helpful? Yes No
Verified answer

Martin Dráb 237,783 Most Valuable Professional on at

Like (1)

Report
Leo, there is a simpler way in D365FO:

System.Exception ex; try { ... } catch (ex) { info(ex.ToString()); throw; // Throwing the same exception object (with the same type, stack trace etc.) }

But you normally don't need code like this, because the message is put into infolog automatically.

Was this reply helpful? Yes No
Suggested answer

Hossein.K 6,648 on at

Like (0)

Report

Hi,

Execute business operations in CIL in your user options and see if that makes a difference (restart your client before debugging).

and then use Visual Studio debugger to see what happens there.

Was this reply helpful? Yes No
Riyas ahamed F 1,215 on at

Like (0)

Report

Thanks to all its resolved!

Was this reply helpful? Yes No