ERROR : "Object 'CLRObject' could not be created" in AX 2012 r2

(1) Share

Report

Posted on by Manmohan Mehta

1,185

We have ax 2012 server in which we have Database, AOS and client installed. We have Windows 2008 r2 standard OS installed on server. We later realize that we need ram more than 32Gb and so for this we have to update OS from Standard to Enterprise edition.

After updating we were facing the issue while restarting the AOS which was later resolved by editing the registry.

I am now able to start AOS and ax client however I am getting an error "Object 'CLRObject' could not be created" while compiling, generate full cil or opening any menu item.

I tried the following thing so far :

Full CIL

Full Compile

Restart AOS

But getting error on clicking every menu item or compile etc.

*This post is locked for comments

I have the same question (0)

All responses (16)

Answers (1)

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

Like (0)

Report

Are you able to get the call stack?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

hi

not sure this is related but whenever we get a CLRobject error it is because a DLL is missing.

maybe upgrading the OS has messed up the GAC?

if you check the Windows event viewer are there any more clues? i would have thought those errors will appear in the application section of the event viewer, and might include more helpful info.

You might be quicker reinstalling AX on this server, i dont think anyone would ever recommend upgrading the windows OS AFTER the applications have been installed.

hope it helps and good luck.

Was this reply helpful? Yes No
Manmohan Mehta 1,185 on at

Like (0)

Report

I have installed another aos and things are wirking for it but now i want run my old aos as this instance is replica of production and i cant reinstall another aos and reconfigure client configurations

Thr should be an another way. I also tried to delete the assembly files from aos xppil folder and restarted aos to check if it works but system didn't generate new assembly files after restart.

@mr drab. Yes while generating a full cil the debbuger windows get open and points to an exception under generateil method.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (1)

Report

You probably have "Enable the hot-swapping of assemblies for each development session" enabled on the AX server configuration. Try turning it off.

Was this reply helpful? Yes No
Suggested answer

Brandon Wiese 17,788 on at

Like (0)

Report

I recently saw the same CLRObject error messages. We fixed it by launching ax32.exe -developer (or -development, can't recall), then opening the AOT, navigating to the Menu node, System Administration, then under Checklists run the Initialize Partition checklist. Mark all steps as completed. Close the client and restart the AOS. Hope this helps.

Was this reply helpful? Yes No
Deepak Agarwal 8,602 on at

Like (0)

Report

Hi Did you got the solution for this issue?? Please share.

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

Like (0)

Report

"Object 'CLRObject' could not be created" doesn't say anything more than that an exception was thrown when constructing a .NET object. It's clearly not possible to provide a single solution that resolves any exception in any object; you have to find out where the error occurs and what error it is (exception type, error message, inner exceptions etc.).

Was this reply helpful? Yes No
Suggested answer

Deepak Agarwal 8,602 on at

Like (0)

Report

May be this will help

theaxapta.blogspot.com/.../error-cil-generator-found-errors-and.html

Was this reply helpful? Yes No
Suggested answer

ArunGarg 3,926 on at

Like (0)

Report

Hi Manmohan,

Could you please go through below link

blogs.msdn.com/.../clrobject-could-not-be-created-error-when-entering-tools-options-in-microsoft-dynamics-ax-2012.aspx

May be it can help you and please verify the solution if your issue has been resolved.

Regards

Arun

Was this reply helpful? Yes No
Preetham 85 on at

Like (0)

Report

Hi Manmohan,

Even I had the same issue. Hot swap was enabled in my machine. I unchecked and restarted the sever. Now I am not getting that error.

Was this reply helpful? Yes No