x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 4 replies
  • Subscribers 75 subscribers
  • Views 743 views
  • Users 0 members are here
Browse Forums
Announcements
105
topics
32
replies
General Discussion
6k
topics
18k
replies
Michele Gaw

Sage CRM 2022 R2 Upgrade -- Is this a bug? System Locked Value.

Posted By

I am in the process of troubleshooting a Sage CRM 2022 R2 upgrade.  I have been trying to clear the red Xs in System Health. 

During troubleshooting, I have noticed that some of the logs indicate that the escalation service has not run because the system is locked.  (I always lock the system before starting an upgrade.)  In order to let the system run the escalation and see if that clears my notification that not all services have started, I went to unlock the system.  However, on the admin screen, the system did not show that it was locked.  That was weird...but I was assuming that maybe the upgrade "unlocked" it.  However, the logs say it is locked.  Therefore, I went through the process of locking the system through the admin screen and then unlocking it.  After unlocking the database through the admin screen, I decided to see what the database indicated.  Therefore, I ran the following script...

select * from custom_sysparams where parm_name like '%syslocked%'

The database is showing as locked as seen in the screenshot below even though on the admin screen it does not show locked.  Is this a bug or am I not looking at this correctly?

This is what my admin screen looks like...you can see it does not show the system is locked...

Also, if the system is locked...does it cause the System Health to look like this??

Any assistance would be greatly appreciated!

  • 0

    Hi Michelle,

    System lock will not cause your services to go red- I really think the cause of your problem has to do with IIS.  Tomcat communicates over the http protocol, if your http settings are out of whack, it will cause what you're seeing.

    If you haven't already, check your http binding in IIS - if your hostname is not correct, Tomcat wont run correctly, neither will any service that uses http

  • 0 in reply to atreulich

    Thank you, I did figure out that I was looking at the wrong field for the "lock".  :-)  My brain is kinda fried righ now...been looking at this too long!!!

    This is what my bindings look like.  I double checked another system and that system only has the lines that I highlighted but that system is on 2021 so I don't know if these other lines are needed and I am not sure why they are there.  Any thoughts?

    Again, I really appreciate your assistance!!

  • 0 in reply to Michele Gaw

    Wow - I don't know why those other bindings are there, but they are bound to localhost, and I think that may be at the root of this.  The only bindings I use for CRM are the ones you highlighted - http and https.

    Can you temporarily remove the other bindings, or find out what they're for?  if you can get them out of the way temporarily, you can see if that solves the problem.

  • 0 in reply to atreulich

    I was thinking the same thing.  Copy the setup and then remove them.  I will give that a try.  I took a look at the tomcat logs and this is what I find there....

    org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
    27-Sep-2022 11:17:37.478 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [/crmExchangeSyncEngine] startup failed due to previous errors

    Not sure where to look at "the appropriate container log file."

    I really appreciate your assistance.

*Community Hub is the new name for Sage City