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 or issues. You do not have to own a commercial license in order to use the OPC Labs support. Our team is actively monitoring the forums, and provides replies as soon as possible.
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.
VB.NET app suddenly has no item changes | OPC-DA | COM
I have some additional questions/comments..
1. Are you connecting to an OPC server on the same machine as the client, or remote?
2. It is *critical* to know *with absolute certainty* whether the Windows Event log entries with RPC_E_TOO_LATE for this application have or have not appeared even *before* you started observing the problem. Please check that. It is quite possible that they were there before too, because they can indicate a harmless condition. And we do not want to be hunting for something that is not actually related to the current issue.
3. I do not see any logging at the code branch where it is needed most. For troubleshooting this, you should log e.Exception.Message as soon as .Succeeded is not True (in this case, the .Exception is actually never Nothing). Only then we can tell whether the ItemChanged was not called at all.
Best regards
Please Log in or Create an account to join the conversation.
my OPC client developed with QuickOPC was working just fine until one day no item changes where processed anymore. I saw that my EventHandler for the
After some digging around i found your thread about COM management:COM security initialization (process "OPC Interface WTEB" Id 38660, application domain "OPC Interface WTEB.exe" Id 1) for requestor 'ComSecurityInitializingEasyDAClient' failed; the initialization object was: (Default).
CoInitializeSecurity failure (0x80010119): Die Sicherheit muss initialisiert werden, bevor Schnittstellen gemarshallt oder unmarshallt werden. Änderungen können nach der Initialisierung nicht vorgenommen werden.
+ This error (RPC_E_TOO_LATE) is not uncommon in hosted .NET applications. Depending on various factors, it might be possible to prevent it, or safely ignore it (if COM works as intended). Consult the product documentation.
+ Current thread name: "", from thread pool: yes, managed thread Id: 19, apartment state: MTA.
COM management - OPC Labs Knowledge Base
I applied all the suggestions but nothing seems to restore the behaviour. So here is some code:
Startup:
ComSetup (was first introduced after the issue occured but didn't change anything)
Handling subscriptions and item changes (i can guarantee that we have items being subscribed with Handles)
Initialization of EasyDAClient
More useful information
- When calling ComSetup.Initialize() directly after steping into Main() we still get the message with RPC_E_TOO_LATE
- The apartment state is MTA
- I have tried changing the Authentication level to Packet Integrity (haven't restarted the PC though)
- No errors are thrown after subscribing via the EasyDAClient
- im using the OpcLabs.QuickOpc nuget package version 5.83.477
- i have tried different combinations of the SecurityParameters
- i have reinstalled QuickOPC and with that the Kit server which i am trying to communicate with
- i have another QuickOPC application which is working just fine which makes this even less understandable
I am not an expert when it comes to COM and i assume this is the root cause as all of the other logic of my client is working just fine, so i would greatly appriciate your help.
Best Regards
Tom
Please Log in or Create an account to join the conversation.
