Thanks for your reply.

The complete nodeset is sent the simulation-server-support@prosysopc.com. On the forum only interesting subset of nodeset was shared.

While importing the nodeset to Simulation Server complete nodeset was used.

Thanks!

This NodeSet is incomplete and invalid XML. It starts with the UANodeSet element as expect, but the element is missing it closing tag. Is this just the sharing site limiting the size of the shared file or is this also the case for the NodeSet file you attempted to import to Simulation Server? If the latter then naturally Simulation Server won't be able to import XML file that is invalid.

If the former, can you send the complete NodeSet to simulation-server-support@prosysopc.com so that we can investigate it?

I have these models in nodeset on this link https://sharetext.io/mvtho539 , when I try to import it I get error from Prosys simulation server "The model could not be loaded to server address space".

Probably there is something missing or wrong with the nodeset.

Please can anyone help to understand what is missing or wrong with the nodeset?

Thanks & regards!  

Matti Siponen said
Hello,

Can you send the NodeSet to simulation-server-support@prosysopc.com so that we can investigate it?  

Thanks for your reply. NodeSet is sent to simulation-server-support@prosysopc.com

Can you send the NodeSet to simulation-server-support@prosysopc.com so that we can investigate it?

I am importing nodeset file in the prosys simulation server. The server reported error: "Invalid string representation of a nodeId: ".

Is possible to find out which nodeId prosys simulation server is refering, so it can be easy to identify the error?

Are there any logs for nodeset import which can be analyzed to find the Invalid string representation of a nodeId?

Thanks !

Matti Siponen said
Hello,

Method Nodes do not have AccessLevel and UserAccessLevel Attributes. Are you referring to Executable and UserExecutable Attributes?

Regardless, Simulation Server doesn't currently allow setting values for AccessLevel and UserAccessLevel Attributes of Variables or Executable and UserExecutable Attributes of Methods.  

Thank you. Would it be possible to request the access control feature for the sim server.

Method Nodes do not have AccessLevel and UserAccessLevel Attributes. Are you referring to Executable and UserExecutable Attributes?

Regardless, Simulation Server doesn't currently allow setting values for AccessLevel and UserAccessLevel Attributes of Variables or Executable and UserExecutable Attributes of Methods.

I am able to add methods in the Object tab to a folder, but I am not unable to add or set attributes like 'AccessLevel' or 'UserAccessLevel' to allow only authorized calls on the method nodes.
Is attributes for methods specified in the protocol?
If so, is this supported by the implementation?
If not, is there a recommended workaround to achieve this?

Thank you!
Mithun,
Tridium Inc.

The certificate and the private key of Simulation Server were updated in version 5.3.0 (see https://downloads.prosysopc.co.....sion-5-3-0). Therefore, updating from 5.0.4 to 5.6.0 would also cause the application to switch its certificate. Please, make sure the the LDS trusts the new certificate and try again.

Which Server did you update and from which version? Can you provide more information on the Local Discovery Server you're using?

Product: Prosys OPC UA Simulation Server
Version: v5.6.0‑6
SDK: Prosys OPC UA SDK for Java 5.4.0‑201
License: Free license
Operating System: Windows (64‑bit)

During discovery registration, the server initially attempts to register using opc.tcp://localhost:4840, but the OPC UA stack automatically switches to an alternate endpoint URL using the machine’s fully qualified domain name (for example, opc.tcp://:4840). Despite successful TCP connections and completed handshakes, the discovery server immediately closes the connection, and the registration never persists.

Could someone let me know what's going wrong here? Everything used to work in the previous version of the server. I am seeing the issue after the server version upgrade.

Here is the details from the server log:

02/26/2026 16:11:24.898 INFO [DiscoveryRegistrationTimer] - localhost/127.0.0.1:4840 Connecting
02/26/2026 16:11:24.908 INFO [DiscoveryRegistrationTimer] - Connected (non-reverse), handshake completed
02/26/2026 16:11:25.126 INFO [DiscoveryRegistrationTimer] - 11 Closed
02/26/2026 16:11:25.126 INFO [TcpConnection/Read] - localhost/127.0.0.1:4840 Closed (graceful)

...

02/26/2026 16:11:26.392 INFO [DiscoveryRegistrationTimer]
Using an alternate endpoint URL
'opc.tcp://bgl7115win64.mathworks.com:4840'
instead of the requested 'opc.tcp://localhost:4840'

...

02/26/2026 16:21:27.183 WARN [TcpConnection/Read]
Bad_SecureChannelIdInvalid (0x80220000)
"The specified secure channel is no longer valid."

...

02/26/2026 16:56:26.442 ERROR
Failed to renew security token.
Bad_ServerNotConnected (0x800D0000)

Maybe we can some day add a flag when creating the node or provide additional attribute simulation or configurability, though not sure when or if this happens (you would need to talk with sales@prosysopc.com)

So if having static data would be enough then that loading via a nodeset is a workaround, though loading such amount of nodes could take hours depending on the distribution of types and instances etc. (in short inside the SDK if 'UaNodes' are being used then adding a new reference does check all references of that node first, types do have a reference to the instances of them). This would require creating such nodesets though. We have some future stuff https://prosysopc.com/blog/pla.....on-server/, that might make it easier to try to duplicate a server (though exporting this amount of nodes might be hard, memory might run out first). Also I should note that the playback feature itself most likely cannot scale to a very high node count. Anyway, if you wish to test, ask sales@prosysopc.com.

However, since you do have the SDK, it might be just easier to try to build something on top of the SampleConsoleServer. For node amounts of this many I would recommend going with the 'MyBigNodeManager' example route, though it should be noted that instances and references here must be modelled manually (i.e. it is more like a view to some existing data(base)).