We had the issue on one system, it appears to be because the 2022 R2/R2.1 installer does not update the JRE correctly in some(?) cases.

So we fixed this on our systems by stopping Tomcat and Quickfind, copying the JRE folder (e.g. C:\Program Files (x86)\Sage\CRM\Services\JRE ) from a 2022 R2 system that does work (such as a clean install on a local VM) to the newly upgraded system that didn't work, then start up the services again.

We had the issue on one system, it appears to be because the 2022 R2/R2.1 installer does not update the JRE correctly in some(?) cases.

So we fixed this on our systems by stopping Tomcat and Quickfind, copying the JRE folder (e.g. C:\Program Files (x86)\Sage\CRM\Services\JRE ) from a 2022 R2 system that does work (such as a clean install on a local VM) to the newly upgraded system that didn't work, then start up the services again.

Thank you John!  I am going to give this a try on one of the servers that is having an issue.

Thanks John...I can vouch that copying the JRE folder from a working 2022 R2 system does resolve the issue.  I can also confirm that it only happens in some cases...one in three installs for me.

Yes, that solution works.. copying JRE from a working 2022R2 install fixed the issue

Follow up on this.  I have been away from troubleshooting this due to being away from the office.  I have a 2022 install on my demo server that does not appear to have the url rewriter issue.  Therefore, I attempted the copy and paste of the JRE directory from this install on a new upgrade.  Unfortunately, this did not resolve the issue...the dashboard not working message still appeared.  I did reboot the server to make sure.

The upgraded server has been rolled back and I plan to attempt the complete uninstall and reinstall.  (I did attempt a "reinstall".  However, that did not fix the issue.)

I had hoped whatever was going on with the upgrade files would have been resolved...but it appears to still be there.  

I have logged a case with support previously and the resolution was to do a complete uninstall and reinstall.  Therefore, I will be working through that in the next couple of days.  I will circle back on the results.

Thanks John,

It worked for me as well & saved a lot of time.