- Posts: 13
- Thank you received: 0
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.
Access violation when setting AllowedMessageSecurityModes
Now I have upgraded this also and everything is working great

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

Please Log in or Create an account to join the conversation.
Note: Any non-trial license covers all previous versions, so if you purchased now, you could use 2017.2 temporarily just fine.
Please Log in or Create an account to join the conversation.
and I don't get the error (just the message about 2017.2 being expired when I try to read a string).
Back to 2018.2 and the error returns.
Alex
Please Log in or Create an account to join the conversation.
Yes I re-created the units after switching to the new version.
If I comment out this statement I get no more errors but the program just freezes when I try to read from the machine but no errors.
I also get the same if I try to set:
OPCClientConfig.AdaptableParameters.SessionParameters.EndpointSelectionPolicy.AllowZeroSecurityLevel := true;
so I seems to be anything under EndpointSelectionPolicy.
Alex
Please Log in or Create an account to join the conversation.
I have a question - have you re-created the Delphi units from the type libraries, after switching to the new version? ( opclabs.doc-that.com/files/onlinedocs/QuickOpc/Latest/User%2...20Libraries%20to%20Delphi.html ).
And, if you comment out this one statement, does it work then, or do you get similar exceptions later down the road? The statement isn't actually necessary, because UAMessageSecurityModes_All is the default value.
Best regards
Please Log in or Create an account to join the conversation.
on version 2017.2 the below worked fine for me:
but since upgrading to 2018.2 I get the error "Access violation at address 04CF7EBA in module 'TestProject.exe'. Read of address 00007530." when trying to set the AllowedMessageSecurityModes.
Alex
Please Log in or Create an account to join the conversation.