[Daniel Zook]

.NET Framework 4.6.2 (and some patches for it) were recently installed on our DEV and TEST environments.  AX has been broken ever since.  Opening the client triggers multiple redundant errors stating “Object ‘CLRObject’ could not be created”.  Opening the Released Products area page gets stuck in an infinite loop with the same error message repeating every time you try to click anywhere or do anything.  (You have to kill the ax32.exe process to get out.)

I can’t prove it (yet), but I think this problem was caused by the 4.6.2 version of the framework, since nothing else was changed in the two days since it worked last.

Has anyone else experienced this?

——————————
Daniel Zook
Director of IT
Lehman’s
Dalton OH
——————————

[Daniel Zook]

Update on this…

We had the same problem appear on both DEV and TEST, both after the .NET Framework 4.6.2 was installed.

On TEST the server ended up hosed after removing 4.6.2 and restarting.  I had to re-install Windows and etc.

On DEV, I stopped the AOS, removed 4.6.2 and immediately installed 4.5.2 and AX was back to normal without any further changes.

The bad news is that I wasted 2+ days working on recovering our TEST environment.  (yes, we have backups).  The good news is that we caught this before 4.6.2 was deployed to our production environment.  I shudder to think what would have happened in that case.

I have the problem may have been caused by being a couple years behind schedule on deploying binary updates, so I’ll test 4.6.2 again after getting up-to-date on that.

——————————
Daniel Zook
Director of IT
Lehman’s
Dalton OH
——————————
——————————————-

[Mark Schurmann]

We are implementing D365 and had the opposite problem.  The Management Reporter and Workflow Editor application downloads would not work without upgrading the client workstations to .net Framework 4.6.2.

——————————
Mark Schurmann
Automobile Protection Corp
Norcross GA
——————————
——————————————-