Hello support,

I am just updating my server from Java SDK 3.2.0 to 4.3.0. This server is only used in test environment. For instance it creates nodes which are read by other OPCUA server.
My server contains that simple method to create an instance of BaseDataVariableType. In my test case a value does not matter.

When I use toolkit version 3.2.0 everything is fine. All attributes of this node can be read by any OPCUA client. When I use toolkit version 4.3.0 instead than only a Prosys client can read this node. All other clients return a BadEncongError/BadDecodingError.

The list of clients:
* CTT 1.2.336.254: BadEncodingError
* UA Expert 1.5.1 (base on C/C++ toolkit 1.4.6): BadEncodingError
* Softing dataFeed Client 1.43.0: Session ReadNode error Unexpected error processing response..
* Softing .Net Standard SDK 2.10: BadDecodingError Cannot decode unknown type in Variant object (0x18).
* Unified Automation .Net Toolkit 3.0.4.0: BadDecodingError [TapTcpConnection.OnMessageReceived] Error raising MessageReceived event.|StatusException|Cannot decode unknown type in Variant object (0x18).
* The OPCUA server that wants to read nodes on my server is built using Softing C++ toolkit 5.62.2. It also fails reading my server’s node.

When I use Prosys OPCUA Client 3.2.0 I can sucessfully read all attributes of this node:
* NodeId = “ns=4;s=ABCD”
* NodeClass = Variable
* BrowseName = “4:ABCD”
* DisplayName = “ABCD”
* Description = “”
* WriteMask = 0
* UserWriteMask = 0
* Value = { Value = null, StatusCode = Good, SourceTimestamp = 08/31/20 09:57:38.5400000 GMT, ServerTimestamp = 08/31/20 09:57:38.5220000 GMT }
* DataType = “i=11” (Double)
* ValueRank = -2 (Any)
* ArrayDimensions = null
* AccessLevel = 3 (CurrentRead, CurrentWrite)
* UserAccessLevel = 3 (CurrentRead, CurrentWrite)
* MinimumSamplingInterval = -1.0
* Historizing = false

All attribute values (except timestamps) are the same for toolkit 3.2.0 as well as 4.3.0. The only difference is that I can read my server’s node only with Prosys client.

This affects only nodes created at runtime. Static node created from model (node set file upload) are not affected and can successfully read.
I have no idea why my nodes are treated as erroneous by so many other clients.

Thomas Reuther