Unable to load certificate errors in test instance after upgrading to Rome from Quebec
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2022 04:15 PM
Hi all,
Please help! Over the weekend we upgraded our test instance to Rome from Quebec on 3/5/2022. I happened to look at the System Logs when testing to make sure LDAP sync of users/groups was working. I saw some "unable to load certificate..." errors that started hours after the upgrade to Rome.... I am a new ServiceNow Admin and this is the first upgrade happening under my "watch" so I am unsure what is causing the errors and if they are something to worry about.
When I navigate to System Definition -> Certificates I do see both certificates listed and they appear valid.. Note the errors appeared after the upgrade to Rome on 3/5 since I do not see any earlier errors of the same type previous to that date...also when I look in the prod system logs I don't see the same errors.
Please see screenshots attached. I have blurred out identifying info on the pictures, but you can see that there is one "Unable to load certificate....publicsigver " error (it actually repeats in the log) related one certificate appearing in the Systel Log, and also a "Unable to load certificate : code-signing-key..." error (which also repeats in the log).
We are supposed to be upgrading our prod instance to Rome next weekend so this has me worried :(. Has anyone else seen these sorts of errors after upgrading to Rome? I am not sure how concern that I should be, but considering the errors only appeared after the Rome upgrade this has me questioning if we should move forward and upgrade our prod instance this weekend.
Thanks for any help!!
-Chris
P.S- Not sure if this contributed to the errors or not, but we did a clone down of prod to our test and dev instances last week around 3/2/2022 (before the upgrade of test and dev to "Rome".)
- Labels:
-
Instance Configuration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2022 08:05 PM
Try to refer to the ServiceNow KB https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0655967 and implement the changes and post the result whether it works or not.
Thanks & Regards,
Vasanth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2022 02:52 PM
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-08-2022 08:13 PM
Thank you Chris for providing the update.
Thanks & Regards,
Vasanth