Critical Message appears when servers are disconnected

[emaddocks]

Does anyone know of a way to avoid the 'Critical Message' popups that occur when you have done a DP connection and then the connected server fails? This is on a distributed system so the vision still runs as it is connected to the central servers.

The popup refers to the DP and that it "Could not send message DP_MSG_CONNECT". Sometimes a large number of these appear and we can't clear them so the process needs to be terminated.

We are running 3.18 P04 on RHEL 8.2

[dbindernagel]

I have never seen a popup window on a failed dpConnect().
Have you checked that these popup windows are not created by some code of your project?

The only place with a popup and distributed systems that I can think of is from the AES.
Have a look at the config entry "aesShowDistDisconnections".

[emaddocks]

It's not something we have created in out scripting. The dpConnect occurs fine while the server is available. It's once you shutdown / fail the servers that the popup appears. This is what the popup looks like:

[emaddocks]

We found the issue was in the Stdlib_3.18 project. It was throwing the error as well as opening a dialog. We have removed the lines of code in which it opens the dialog...a simple but effective band aid fix