OPC UA server not exposing Tags

Ignition
1

Ignition 8.1.38 configure as OPC-UA server for third program to read tags. but no tags are exposed, cant even see them on Quick Clint in Ignition, when I try to expand the folder Tag Providers nothing shows up. If I use UAExpert i got the error "Failed ns=2....... BadNodeIdUnknown"

The bind adress is set to 0.0.0.0

I have the same settings on another server were everything is working fine.

I have restarted the OPc UA module and ignition service but still the same issue.

this is the logs when i try the quick client

failed to get browse attributes for: NodeId{ns=2, id=Tag Providers}

java.util.concurrent.CompletionException: UaException: status=Bad_NodeIdUnknown, message=The node id refers to a node that does not exist in the server address space.
at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(Unknown Source)
at java.base/java.util.concurrent.CompletableFuture.completeThrowable(Unknown Source)
at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(Unknown Source)
at java.base/java.util.concurrent.CompletableFuture.postComplete(Unknown Source)
at java.base/java.util.concurrent.CompletableFuture.completeExceptionally(Unknown Source)
at org.eclipse.milo.opcua.sdk.server.api.AsyncOperationContext.failure(AsyncOperationContext.java:65)
at org.eclipse.milo.opcua.sdk.server.api.AddressSpaceComposite.lambda$browse$3(AddressSpaceComposite.java:214)
at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(Unknown Source)
at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(Unknown Source)
at java.base/java.util.concurrent.CompletableFuture.postComplete(Unknown Source)
at java.base/java.util.concurrent.CompletableFuture.completeExceptionally(Unknown Source)
at org.eclipse.milo.opcua.sdk.server.api.AsyncOperationContext.failure(AsyncOperationContext.java:65)
at com.inductiveautomation.ignition.gateway.opcua.server.extags.ExposedTagsNamespace$browse$1.invokeSuspend(ExposedTagsNamespace.kt:192)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
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)
Caused by: org.eclipse.milo.opcua.stack.core.UaException: status=Bad_NodeIdUnknown, description=The node id refers to a node that does not exist in the server address space.
at com.inductiveautomation.ignition.gateway.opcua.server.extags.ExposedTagsNamespace.browseTag(ExposedTagsNamespace.kt:237)
at com.inductiveautomation.ignition.gateway.opcua.server.extags.ExposedTagsNamespace.access$browseTag(ExposedTagsNamespace.kt:74)
at com.inductiveautomation.ignition.gateway.opcua.server.extags.ExposedTagsNamespace$browseTag$1.invokeSuspend(ExposedTagsNamespace.kt)

2

Try the "Browse Device" feature and test if you can browse the tags from the Tag Browser

image
image181×192 6.5 KB

Pull in a tag and look at its "OPC Item Path" to ensure the Namespace number is correct.

3

I just found an issue in our tracker that matches this behavior... it seems that if you have Tag Read Permissions configured on any provider, it breaks the browsing to all of them...

(unless, presumably, the user you are connected with has read access to all of them?)

IGN-11017 for reference.

4

I can browse all the tags, the problem is not with the clients. it is from a 3rd opc client to read tags from Ignition

5

i have a tag read only tag provider, so i will see when i can change this and test again. Thanks, will update after I test!

I checked the Ignition OPC-UA server and is not read only, and the user for the ignition opc server is ReadWrite, but one tag provider is read Only