Warning: Creating default object from empty value in /var/www/vhosts/st4makers.com/httpdocs/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/slideshow_layerslider/slideshow_layerslider.php on line 28 st4makers.com
You have to configure DCOM to access remotely to the server, but is extremely difficult get this configurations working… My advice, try to keep server and client on the same computer and you can connect your final clientes directly to the KepServer via OPC-UA
Hi, try to use KepServerEX as a wrapper and then connect it to Ignition via OPC-UA, it worked for me.
I have experienced before similar issues trying to establish a OPC HDA connection to Ignition and the support services told me that:
The main issue we were having seemed to come from the fact that our application runs as a service, and the opc server expects to run as an interactive program. Normally when this is the case, we set the dcom settings on the server to specify that it should only run as the ‘interactive user’, which normally prevents multiple instances from running. In this case, however, the server continued launch a second instance. Unfortunately, since we’re using a java COM wrapper, it’s not easy, or sometimes impossible, for us to set more advanced COM security flags on startup. Therefore, some solution based on COM server settings would be the best. The problem may also be an environment issue on this particular windows installation, as we’ve never seen this issue before.
I do not know what does meant but the fact is that we never got the OPC server directly connected to Ignition