Sage CRM 2022 R2 upgrade - URL rewriter may not be working

SUGGESTED

After completing the 2022 R2 upgrade, I am getting a message that the url rewriter may not be working properly.  Also after checking the System Health area, almost everything has a red X beside it.

I have been through the troubleshooting steps and I am not sure how to interpret the returned information in the command prompt.

Based on the above information is there something I need to change?

Any assistance you be greatly appreciated.

  • 0

    Hi Michelle,

    Did you get to the bottom of this?  Had something very similar with an upgrade to 2022 R2 from 2019 R2.  The only solution after hours of pain was to uninstall R2, and first go to 2022 R1 before then going to R2.  Then everything worked ok. 

    Documentation says it's ok to go straight from 2019 R2 to 2022 R2, but from now on I'll be going via 2022 R1 first.

    Pete.

  • 0 in reply to Peter Clark SCS

    Peter, so I have this problem at 3 clients right now...if I install Sage CRM 2022 R1 over the current install of Sage CRM 2022 R2 and login the dashboard and related functions work.  If I reinstall Sage CRM 2022 R2 over the R1 the dashboards break......so did you fully uninstall Sage CRM instead of overwriting?  There must be some sort of bug in 2022 R2....

  • 0 in reply to cmengerink

    Hi,

    Yes, I had to do a full uninstall of R2, and then a reinstall of 2019 R2.  Once I'd tested and confirmed 2019 R2 was working ok, I then upgraded to 2022 R1, tested, and then upgraded to 2022 R2. 

  • 0

    Hi, I've had exactly the same issue and the only way Sage Support have managed to resolve is by backing up the database, library and custom pages/ custom dot net etc then uninstalling CRM and perform a fresh install of 2022R2. Then restore backed up database/folders and all OK!!!

    A pain but a solution.

    Hope it helps!

  • 0 in reply to RBC_1

    Thanks RBC that's exactly what I ended up doing and it worked for me as well...though note it may change the tomcat port to 10001 when the older systems were on 10009 so you have to update the two params in the restored database.

  • 0 in reply to cmengerink

    Gentlemen:  I have this on multiple clients as well.  I have spent DAYS trying to resolve.  I worked with support in the last week or two.  After checking all the connections and finding nothing wrong.  I was instructed to reinstall the program files and aliases.  I did that on one of the installs and it did not resolve the issue.  Therefore, I was preparing to do another round with support.

    I am going to go back and try the recommendations listed above.  I will circle back and let you know if it worked for me as well.  

    So glad that I logged on and found that I am not the only one banging there head on the desk with this issue!  :-)

  • 0

    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.

  • 0 in reply to John Kingsbury

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

  • 0 in reply to John Kingsbury

    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.

  • 0 in reply to Joel - DA
    SUGGESTED

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

  • 0 in reply to Mathew Simon

    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.

  • 0 in reply to John Kingsbury

    Thanks John,

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