What are the possible causes and remedies for appearance of the status code in the OPC UA Client when using subscriptions?
|Status code||Possible cause||Remedy|
|BadTooManyMonitoredItems||The maximum number of monitored elements in a subscription has been reached.|
You have to create a new subscription to register more elements.
|Request with too many elements||Pay attention on the server to the specified maximum numbers in the "ServerCapabilities" object.|
|BadOutOfMemory||Maximum quantity framework of the OPC US server has been exceeded|
Reduce the number of elements registered via OPC UA.
Using an OPC UA Server Diagnostics Tool (UaExpert of Unified Automation, for example) make sure that there are no inactive sessions and subscriptions. As a countermeasure you can select the corresponding timeouts (Subscription Timeout <= Session Timeout) in the Client.
|BadTooManySubscriptions||The maximum number of subscriptions has been exceeded||Create a subscription in a new session.|
More information is available in the following entries: