No errors that I know of but the server was rebooted around 7pm last night and the Ignition HMI server could not get any data until I logged into the KEPServerEX server and opened the KEPServerEX Configuration client. I did nothing else,
This has happened before. How do we make sure that the OPC UA connection survives a reboot?
I updated from 6.16 to 6.17 as this is a known issue. Would be nice to get a notice about a version that stops communicating or the like. Hopefully 6.17 fixes the similar known issue.
This is the info from support:
Please note that there is a similar known issue in the mentioned version, and our development team has fixed this in the 6.17 release. Here is the article about the same issue:
https://www.ptc.com/en/support/article/CS424828
The root cause of the issue is related to the order in which Kepware Server’s services attempt to start.
Also there is a workaround that you can apply to your current installations: you will need to copy and paste the following command (without quotes) into an Administrator command prompt:
“
sc config KEPServerEXLoggerV6 depend= KEPServerEXKeySvcV6
”
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
