WinCC OPC UA unable to auto connect

Hi There
We are using WinCC OPC-UA connection for one of our ignition project
but incase of any network disruption or WinCC OPC-UA machine restart ignition OPC-UA does not auto connect.

To validate further we have checked no subscription tag configured against WinCC OPC UA instance

Further we have added another instance of same OPC-UA without configuring any tags, this OPC-UA instance connect auto incase of any failure

Error Message

UaException: status=Bad_ConfigurationError, message=no matching endpoints found
at com.inductiveautomation.ignition.gateway.opcua.client.ClientManager.initializeObject(ClientManager.kt:118)
at com.inductiveautomation.ignition.gateway.opcua.client.ClientManager$initializeObject$1.invokeSuspend(ClientManager.kt)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(Dispatched.kt:241)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)

Refer below snapshots

This error on your second connection means you have one or more of these configured incorrectly, and there is no matching endpoint returned by the server:

  • endpoint URL
  • security policy / message security mode
  • authentication (anonymous vs username/password)

The reconnect issue would need to be diagnosed with logs and/or Wireshark. I know in a more recent version of Ignition a workaround was implemented for reconnecting to some faulty servers that would close the connection instead of return an error when they didn’t support one of the steps the reconnect flow that happens.

You’re on quite an old version of Ignition and should consider upgrading. Hopefully your license has upgrade protection and you can go all the way to 8.1.19.

Thanks Kevin for update
We have done similar configuration both above mentioned OPC-UA but still only instance is not connecting when it has assigned to some tags.

I found solution

There were few transaction group running based on subscription
We have changed them into Read mode