MID Server issues - MID Server encryption keys do not match and are no longer valid

Leandro Carpent
Kilo Contributor

Guys, good morning.
Could someone help me with this error? MID SERVER is accusing this error for 4 days, I have already performed the following procedures to try to resolve:
- Delete the Keystore folder
- Delete the values of "parameter name =" keypairs.mid_id "value"
- Restart the server and services.
- Update the credential password on the services.
PS: This error, only happens in the Production environment, in DEV and QA it doesn't happen.
Has anyone been through this and could help me?
MID SERVER in Windows environment

find_real_file.png

10 REPLIES 10

Hi,

This mid server is windows mid server right. Can you show screenshot of this two error from the related list?


Thanks,
Ashutosh

Rahul Priyadars
Giga Sage
Giga Sage

Is it possible to TRY as per below KB-

https://hi.service-now.com/kb_view.do?sysparm_article=KB0752979

Reagrds

RP

When I trie discovery or test credencial in UNIX show error, when use credencial windows is working

Is it possible to try a putty session on these UNIX/Linux Servers using same credentials from this Mid Server?

Regards

RP

 

tim_broberg
ServiceNow Employee
ServiceNow Employee

As of Orlando, when the mid server restarts, it updates the public key used by the instance to encrypt credentials sent to the mid.

On restart, you should see a message about that public key: success, missing signature, or bad signature.

Which do you see?