AMB client disconnected after connecting

[Vinicius2]

Hello everyone,

We have a MID Server that is currently down and it has the following mid server issue, "AMB client disconnected after connecting", does anyone know how to fix this and what could be causing this error?

It's my first time troubleshooting mid servers so I don't have that much knowledge on the subject.

[Le Son]

Hi  Vinicius2,

Could you please for me know information details to fix this error?

[Vishwanath Nair]

Hi Vinicius2,

Please provide steps to fix this. We have run into a similar issue here.

[shubhamkhai]

Did you get the solution?

[Meagan]

Hi Vinicius2

Please can you provide the steps to resolve/ elaborate on your explanation as we are experiencing a similar error.

Regards

Meagan

[vaibhav_joshi]

Hello All,

We have faced the similar issue and i was able to resolve by following below steps -

As per the error message, I do understand this is a known issue. can you please provide me an update once by following the below steps.

To resolve the below mid server issues, please follow steps:

1. AMB client disconnected after connecting
Please manually resolve the error and restart the MID server to confirm it was an intermittent issue.

2. MID Server encryption keys do not match and are no longer valid. To restore proper functionality, invalidate and re-validate the MID Server.
Could not decrypt file discovery whitelist after sync

> Navigate to the Mid server on instance

> Under Related Links, click Rekey.

If the issue is still present, please follow below steps:
a. Stop the MID Server service.
b. Then delete the file .\agent\keystore\agent_keystore.jks, or .\agent\security\agent_keystore. [take back of this file first and then delete it, if 'agent_keystore.jks' not present already, you can ignore it]
c. open config.xml file (Agent/config.xml) with admin rights in notepad
d. Update the mid_instance.password parameter value in the plain text format in the config.xml file.
e. Remove the value of 'keypairs.mid_id' parameter from the config.xml file.
f. Save config.xml
g. Start the MID Server service. A new Keystore file should be created automatically on startup.
h. Invalidate then validate the MID on the instance UI action.
i. Rekey the MID server on instance UI action under Related Links.

If this does not help then, please open a HiCase with ServiceNow.