Professional OPC
Development Tools

logos

lupa

Online Forums

Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.

Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.

Do not use the Contact page for technical issues.

  1. Forum
  3. Discussions
  5. QuickOPC-UA in COM
  7. Reading, Writing, Subscriptions
  9. SubscribeMonitoredItem errors

SubscribeMonitoredItem errors

More
04 Nov 2024 16:26 #13262 by support
Replied by support on topic SubscribeMonitoredItem errors
The errors might be occurring e.g. because it takes the server too long to respond to a message from the OPC client (QuickOPC). They are both very similar, just have to do with different stages of what has to be done in order to perform the OPC operation.

But, SubscribeMonitoredItem does not throw any exception. It reports errors through the event/callbacks. In addition, one of the errors indicates it is from BrowseXXXX call. So what you reported here is grossly imprecise.

Anyway, with high likeliness this is either a problem in the communication path (network), or on the server side. If you have indication to the contrary, using a network analyzer such as WireShark might be a way to troubleshoot deeper.

Regards

Please Log in or Create an account to join the conversation.

More
04 Nov 2024 15:54 #13260 by adaml@trunovate.com
SubscribeMonitoredItem errors was created by adaml@trunovate.com
When I call the SubscribeMonitoredItem function, I encounter two different errors.
Sometimes, one error is thrown; other times, the second error appears.
Why each of these errors might be occurring? What is the difference between them?

The errors:
1. OpcLabs.EasyOpc.UA.OperationModel.UAException: An OPC-UA operation failure with error ID 'OpcLabs.UAEngine=4417' occurred, originating from '' and with depth of 1. The inner exception, of type "OpcLabs.EasyOpc.UA.Engine.UAEngineException", contains details about the problem. ---> OpcLabs.EasyOpc.UA.Engine.UAEngineException: Timeout connecting the OPC-UA client session. The total timeout value was 60000 milliseconds, and we have waited for 0 milliseconds. The actual waiting time is lower than the total timeout (or even zero) if the connection operation has already started earlier.
+ The client method called (or event/callback invoked) was 'BrowseMultiple[1]'.

2. OpcLabs.EasyOpc.UA.OperationModel.UAException: An OPC-UA operation failure with error ID 'OpcLabs.UAEngine=1' occurred, originating from 'Opc.Ua.Core' and with depth of 2. The inner exception, of type "OpcLabs.EasyOpc.UA.Engine.UAEngineException", contains details about the problem. ---> OpcLabs.EasyOpc.UA.Engine.UAEngineException: UA SDK error (Opc.UA.ServiceResult=0x80850000) in 'DiscoveryClient.GetEndpoints'. OPC UA service result - Error establishing a connection: BadRequestTimeout.
+ The error occurred when preselecting an endpoint for discovery URL "opc.tcp://...".
+ Connection attempt #3; last connected at 1/1/0001 12:00:00 AM (local); unconnected for 00:01:01.5620000.
+ If this error happens during connection to a server: Is the server running and fully operational?
+ The client method called (or event/callback invoked) was 'ServerConditionChanged'. ---> OpcLabs.EasyOpc.UA.UAServiceException: OPC UA service result - Error establishing a connection: BadRequestTimeout.

Please Log in or Create an account to join the conversation.

Moderators: support
  1. Forum
  3. Discussions
  5. QuickOPC-UA in COM
  7. Reading, Writing, Subscriptions
  9. SubscribeMonitoredItem errors
Time to create page: 0.044 seconds