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.

Parents
  • 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!

Reply
  • 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!

Children
  • 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!  :-)