vvoldsund

I have now reproduced something that looks a lot like the same issue using 6.2.313 with logging set to "Information" for the ADS servers. Monitoring the server in ADS monitor...

I have reproduced the issue again with debug as log level this time. Now it is the more expected port 27001 that fails again as you can see in the...

Reproduced the issue again. This time without the clients checking the state of the server instances creating noise in the log. The issue this time was again on the 27002...

An update on the environment. As we are using an older version of TwinCAT I tried to update to the latest. Unfortunately it made no difference. Issue is also reproducable...

I will update with the new package to see if I still get the issue / more information from the logs. **Regarding the first point:** I also have logs from...

That was a reference to my own code. From the logs it looked like the read command was logged, but the response was not. So just to mention that the...

I have now throughout the weekend with 16 virtual machines running 6.2.345 and three running 6.2.313. None of the 6.2.345 failed, so no log message recorded. One of the 6.2.313...

> Yes, unfortunately we seem to have introduced an issue with shutting down the AdsServer (the receiving loop remains). How do you close your AdsServer/AdsClient instance and connections? I will...

We have now deployed 6.2.345 to production. A bit early to say if we see the same issue, but we have a new one (possibly related). At one specific installation...