Unable to configure MID server

girishk
Tera Expert

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.

1 ACCEPTED SOLUTION

dravvyramlochun
ServiceNow Employee
ServiceNow Employee

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


View solution in original post

6 REPLIES 6

glenn_pinto
ServiceNow Employee
ServiceNow Employee

MID Server Fundamentals launched today based on the Paris release with Installation and Configuration.

find_real_file.png

Upgrade and Optimization will be added to this course within a couple of weeks. https://nowlearning.service-now.com/lxp?id=overview&sys_id=dcfdb5b5dbf5acd030c91fdc1396199a&type=cou...

Look forward to your feedback and additional needs surrounding the MID Server

 

MID Server Fundamentals (updated)
The MID Server Fundamentals course is now updated to include all the new security features added in the Quebec release including:
- Certificate Check Policies
- Unified Key Store
- MID Server Mutual AuthenticationCourse is free to internal, customers, and partners. (edited)