We are getting a render exception after starting PC server. Before this we did a PC upgrade to higher version. The render exception is being thrown on entering any coverages screen or any screen with Coverages tab. In short, none of the coverages are loading on the screen after upgrade.
We were creating a submission after the upgrade. All screens worked fine except the Coverages screen or a screen with a Coverages tab. On entering the coverages screen it is throwing render exception. On analyzing logs, we found that the Coverage type loader is trying to load a direct covterm config class which was present in the older version OOTB. It’s an OOTB class, so why is it not upgraded to its equivalent class in the higher version? What is the possible solution for this?
Any information regarding how to solve such type loading issues is highly appreciated.
Thank you!
Krishna Mohan Rao Dabiru is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.