- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-02-2022 10:40 AM
Dear Community,
When setting up MID Server under Ubuntu the configuration get's stuck in the last step: Validation of the MID Server in the ServiceNow instance.
I have checked time zones on the ServiceNow instance and the VM hosting the MID Server, both are the same.
I have invalidated and restarted the MID Server and validated again, still the "Validated" value is stuck in "Validating".
I have stopped the MID Server and reinstalled again. Still the issue is that same.
When reinstalling I followed these steps shown in the screen shots.
Any hint is much appreciated.
Thanks
Markus
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-02-2022 11:09 AM
Hi, may you please try restarting Ubuntu server as well?
I recently faced the same challenge after an upgrade; tried re-validate, rekey, restart MID app ... only rebooting Linux server made it functioning again.
Another possible issue - time is not synchronized on the server. Check NTP settings.
Hope it helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-02-2022 11:09 AM
Hi, may you please try restarting Ubuntu server as well?
I recently faced the same challenge after an upgrade; tried re-validate, rekey, restart MID app ... only rebooting Linux server made it functioning again.
Another possible issue - time is not synchronized on the server. Check NTP settings.
Hope it helps
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-02-2022 01:04 PM
Dear Appli,
Thanks for the quick reply. This was of great help. I needed to reboot the Linux/Ubuntu VM several times.
Additionally I needed to run the procedure of KB0959666 (which is describing your suggestion rekey and restart of MID server in detailed steps) several times, but with the difference that the deletion of the "keystore" worked via this way "/opt/servicenow/mid/agent/security$ rm agent_keystore" and not delete directory keystore under the agent directory.
I'm happy that it works.
Cheers
Markus
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-09-2022 01:46 AM
Thanks Markus. You pointed me in the right direction on where the keystore file was located. The location probably changed after Rome upgrade?
My problems started after auto-patching of MID server to patch "Rome Patch 4 Hot Fix 1a". Keystore was apparently corrupted in the process and no credentials used by the MID server worked.