Unable to configure MID server

[girishk]

We are unable to configure MID server for our SNOW instance   Version:Helsinki .patch7 updated.we get the error as follows

Encountered error: [null] while starting up the service. Retry...

05/16/17 22:36:22 (688) StartupSequencer SEVERE *** ERROR *** Unable to load keystore: Unexpected IOException loading KeyStore, caused by: Keystore was tampered with, or password was incorrect

The user account has mid_server role.and password is getting "encrypted"when i start the service.But the MID server is still showing down.

Kindly do the helpful.

[dravvyramlochun · Accepted solution]

Hello Girish,

I think this might be helpful to you:

Keystore Corrupted

The MID Server has a keystore on the host machine of the MID Server. The keystore is a repository of security certificates and private keys that have been established as part of the trust management between the MID Server and either the instance itself or the host machines the MID Server is configured to communicate with during a discovery or integration task. When this keystore becomes corrupted, either the communication with the instance itself is compromised or part of the services supported by the MID Server are corrupted. The keystore is located under the /agent directory of the MID Server. When you validate the MID Server from the instance, you contribute to the keystore.When a MID Server has been reinstalled, or if a MID Server crashes unexpectedly, the keystore can become corrupted. Once it does, the MID Server will act unpredictably.You can see if the keystore is the source of MID Server issues by looking in the agent log and searching for the phrase SEVERE *** ERROR *** Unable to load keystore:. If the MID Server is attempting to start or restart, this will prevent the MID from starting successfully.SOLUTION: Recreate the keystore directory - There is no way to mend the keystore once corrupted. The only thing you can do is delete the keystore directory from the /agent directory of the affected MID Server.

1. If the MID Server is running, go to the /agent directory and execute the stop script (.bat or .sh).
2. Delete the keystore directory.
3. Restart the MID Server using the start script (.bat or .sh).
4. On the instance, open the MID Server > Servers list.
5. Open the record for the restarted MID Server.
6. Select the Validate UI. The MID Server will clear the cache, restart, and regenerate the keystore. The MID Server record will report that it is Validated.

You can also refer to ServiceNow KB: SOLUTION: Resolve MID Server user credential issues (KB0597570)

Thanks,

Dravvy

Please Hit like, Helpful or Correct depending on the impact of the response

[girishk]

That worked.Thanks dravvy

[Runjay Patel]

Check out this video, it will clear all your doubts and help you to understand mid server in details. It will help you resolve below queries:

Link: https://youtu.be/RMXhYJxPMPU

1. Mid Server Installation step by steps
2. Mid Server Troubleshooting for all version.
3. I am unable to install mid server.
4. Unable to configure MID server.
5. Service Mapping Mid Servers.
6. How to log in to the Mid server using the Credential.
7. MID Server for multiple sub production instances.
8. Why do we use MID server? Purpose of using MID Server?
9. How to define a specific mid server for the discoverIpAddress () function?
10. Other issues.

[Tom Rausch]

Hello, @Runjay Patel ,

The linked video is no longer available.

How does one "define a specific mid server for the discoverIpAddress() function?"