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.

[Pratiksha]

Hi @Vinicius2,

1) Restart the mid server service on the windows machine 

2)Check if port 443 is open so that mid server can communicate with servicenow instance

3)If any proxy is been used check if you have given the correct proxy. (you can check this in agent folder- > config.xml file)

4)Lastly the user used for mid server is working( If you know the password try to log in and verify it works)

Regards,

Pratiksha Khanelwal

[delblack]

Our initial attempts to restart MID, Rekey, Invalidate/Validate did not work. After manually restarting the server the issue was resolved. 

Manually start, stop, and restart a MID Server 

Before manual restart

After manual restart

Note: The AMB Client (Asynchronous Message Bus Client) is primarily responsible for facilitating communication between the ServiceNow instance and its Mid Servers, so if the AMB Client is impacted, it can lead to disruptions in data synchronization, slow performance, and potential issues with workflows that rely on real-time updates between the server and mid-servers

[SD_Chandan]

@delblack ,
Hi rekey affect to any on going functionality ?

[Vinicius2 · Accepted solution]

Error was found, we reverted our MID Server script include used o Connector Definition back to Utah version.