MID server validation failed

[smrevanth]

We were facing some strange issue with our mid server in dev. ONLY WITH DV MIDSERVER

A quick background :

we have integration with remedy and this is through the midserver. We were able to send the SOAP message to the remedy instance. but, we are not able to get any response from the remedy. The remedy team has confirmed that their outbound logs have the response. but, in our servicenow instance, no response was registered in the ECC queue.

What I observed is, the MIDSERVER in the dev instance is UP but, Validation failed. I tried restarting the mid server, revalidating, even the rekey option. but, no luck

What are the causes of this MID SERVER validation failure? Any ideas from anyone?

[Saketh · Accepted solution]

Hi Revanth,

This happens when the keystore file is corrupted.

Try the below steps:

1. Stop the MID Server service

2. Wait for MID server to go down, you can check the status from Instance

3. In the agent folder, rename the "Keystore" Directory to "Keystore.old"

4. Run the "installer.bat" file and ensure you have correct MID server name/userid

5. Once the MID server comes up, you can try validating it again.

Thanks,

Saketh

[smrevanth]

Thanks Saketh,

I will try this method today. Will let you know

[smrevanth]

Hi Saketh,

It worked. Thanks

[jeffreyluto]

Is there a Keystore directory in Windows installs?