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.
- Forum
- Discussions
- QuickOPC-Classic in .NET
- ‘Access denied’ + The client method called was 'BrowseProperties'.
‘Access denied’ + The client method called was 'BrowseProperties'.
The screenshot of the "other error" is missing. However, OPC analyzer isn't suitable to troubleshoot issues like this, because putting it in middle completely changes precisely the part that needed to be diagnosed.
I am not saying it is a "DCOM issue"; I wanted to say it might be possible to resolve by tweaking DCOM, even when other clients do not need it.
There really isn't anything else I can offer.
Note: I am on vacation this week, replies take longer.
Best regards
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Now, interestingly, running the OPC Data Client app as Admin yields a different error (See screenshot). Would this provide you with more clues on what could be happening here? The customer seems to think that this is an issue with the toolkit since he has been able to get every other OPC DA client to connect without any issue, so I would appreciate it if you could explain what could be the issue here. Thank you in advance.
Attachments:
Please Log in or Create an account to join the conversation.
The only remaining option is to re-check the DCOM configuration. It is possible that somewhat different setting might be needed for .NET-based clients, but I do not have more concrete hint. Attempt to set the security completely open to "everyone", and if it starts working, tighten it up. But I cannot think of anything else.
Best regards
Please Log in or Create an account to join the conversation.
Thank you for the suggestions. However, it seems like the setting is not changing the behavior. do you have any other suggestions? Attached, I will include the code (frmDACleint_UI.vb) just in case it helps. Please let me know if you need anything else. Thank you very much for your support.
Please Log in or Create an account to join the conversation.
I know that the issue is related to DCOM - basically, we sometimes require different settings from what other OPC clients need, due to internal implementation, plus the proper combination of these parameters - but unfortunately I do not have a concrete recommendation on how they should like like in particular situation.
Here is one more thing to test out:
Please have the customer put the following right after the creation of the EasyDAClient object (important: *before* any actual OPC operation is done) into the code:
client.InstanceParameters.EnableNativeClient = false;
This switches parts of the internal implementation to a different code which should behave more closely to "traditional" OPC client. I am normally hesitant to suggest this, because there is a slight risk that some other behavior changes and something in the client's app gets broken.
Best regards
Please Log in or Create an account to join the conversation.
Unfortunately, the customer tried all 8 combinations when changing the parameters suggested on the post you suggested and he still getting the same Access Denied issue.
Do you have any other suggestions that we could try so that we can borrow down the issue?
Please Log in or Create an account to join the conversation.
Can the customer please try the different settings of EasyDAClient.ClientParameters.UseCustomSecurity , TurnOffActivationSecurity and TurnOffCallSecurity as listed here?: www.opclabs.com/forum/connections-reconnections-com-dcom/124...-remote-machines-via-code#1392 .
Note that different combinations cannot be tried in the same run of the program.
Best regards
Please Log in or Create an account to join the conversation.
I am currently working with a customer that is encountering an Error whenever trying to connect to WinCC OPC DA server. Basically, in his code, he is subscribing to multiple tags but the application returns this error:
*7/20/2021 10:08:59 AM DA_Client1 Error Itemchanged-: System.UnauthorizedAccessException Access is denied. + The client method called was 'ItemChanged'.
So, I had him test with the EasyDA Client Demo and connectivity explorer and he is getting the same issue as you can see in the screenshots attached.
Now, the weird part is that he is able to communicate to that sam server using Matrikon OPC Explorer so I am not sure what is happening here. I did have the chance to read over this post in this forum >www.opclabs.com/forum/browsing/3226-error-access-is-denied-t...or-event-callback-invoked#9808< But the customer is running the latest version and I am not sure he is using an appsettings.json in his application.
Do you have any ideas on what could be happening here? Please do let me know if you need anything else. Thank you in advance.
Customer's environment:
Microsoft Visual Studio Community 2019
Version 16.10.2
VisualStudio.16.Release/16.10.2+31410.357
Microsoft .NET Framework
Version 4.8.04084
OPC Data Client V 5.61.241.1
Please Log in or Create an account to join the conversation.
- Forum
- Discussions
- QuickOPC-Classic in .NET
- ‘Access denied’ + The client method called was 'BrowseProperties'.