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.
System.NotSupportedException: Specified method is not supported
Not a specific idea at the moment. But what we can do is that we can improve the error diagnostics in this particular case, as it is sub-optimal at the moment, and it does not expose some important information about where precisely the error happened.
I need to assign this to the developer. When it is finished, we will have a new build and I will ask you to re-build your software with it and reinstall on the customer site. I suppose you are on the latest QuickOPC version (2025.1), because that's what we will be updating. Please allow some time for this.
Regards
Please Log in or Create an account to join the conversation.
The customer installed the 64 bit version of the OPC Core components, but the problem persists. Any other idea?
Thank you.
Michael
Please Log in or Create an account to join the conversation.
I suggest to change it in your Installshield (there is a 64-bit merge module in the same ZIP as well).
On the particular customer's computer, it is fine to just uninstall the 32-bit components (if they appear in Add/Remove programs), and install the 64-bit components form .MSI again.
I cannot be sure whether it fixes the problem, bit there is a strong relation (it appears as missing OPC proxy for 64-bits).
Best regards
Please Log in or Create an account to join the conversation.
Thank you for your answer.
We are using the following merge module in InstallShield:
OPC COM ProxyStub Merge Module (x86) - OPC COM ProxyStub MergeModule (x86).msm
Version 3.00.108.
This is the 32bit version of the OPC Core components, not the 64 bits.
Please advise how to proceed.
Thank you.
Michael
Please Log in or Create an account to join the conversation.
Can you please ask the customer to install/reinstall OPC Core Components, making sure they use the 64-bit package?
The file is here: opcfoundation.org/developer-tools/samples-and-tools-classic/core-components/ , name is "OPC Core Components Redistributables (ZIP/MSI/MSM)".
After unpacking, double-click on "OPC Core Components Redistributable (x64) 3.00.108.msi" and let it install for all users.
Best regards
Please Log in or Create an account to join the conversation.
Our client is using the DeltaV OPC DA server. When he tries to browse for OPC items, he is getting the following error. Browsing with Matrikon OPC Explorer works fine.
Exceptions
Type: OpcLabs.BaseLib.Browsing.BrowseException
Data: ErrorId_{045406CD-8EEA-4F21-B3D6-DC9DB5A34E58}: OpcLabs.{6468EA80}
HelpLink:
HResult: -2146233088 (0x80131500)
InnerException:
System.NotSupportedException: Specified method is not supported.
+ The client method called (or event/callback invoked) was 'BrowseNodes'.
at OpcLabs.EasyOpc.Implementation.NetApi.NetApiOpcServer`2.ConnectToServer(WebProxy proxy, Server server, NetworkCredential credentials, String connectionGroupName, EasyClientConnectDataParameters easyClientConnectDataParameters, ServerCategories serverCategories)
at OpcLabs.EasyOpc.Implementation.NetApi.NetApiOpcServer`2.Connect(Boolean doOnlyIfGoodStatus, Boolean callGetStatus, Exception& exception)
Data:
OpcLabs.EasyOpc.Implementation.NetApi.NetApiErrorHarmonization.Processed: True
OpcLabs.EasyOpc.Implementation.ClientErrorEnhancement.Processed: True
OpcLabs.EasyOpc.Implementation.DAClientErrorEnhancement.Processed: True
HelpLink:
HResult: -2146233067 (0x80131515)
InnerException:
Message:
Specified method is not supported.
+ The client method called (or event/callback invoked) was 'BrowseNodes'.
Source: OpcLabs.EasyOpcClassic
StackTrace:
at OpcLabs.EasyOpc.Implementation.NetApi.NetApiOpcServer`2.ConnectToServer(WebProxy proxy, Server server, NetworkCredential credentials, String connectionGroupName, EasyClientConnectDataParameters easyClientConnectDataParameters, ServerCategories serverCategories)
at OpcLabs.EasyOpc.Implementation.NetApi.NetApiOpcServer`2.Connect(Boolean doOnlyIfGoodStatus, Boolean callGetStatus, Exception& exception)
TargetSite: Void ConnectToServer(System.Net.WebProxy, Opc.Server, System.Net.NetworkCredential, System.String, OpcLabs.EasyOpc.Implementation.NetApi.EasyClientConnectDataParameters, OpcLabs.EasyOpc.ServerCategories)
DeclaringType: OpcLabs.EasyOpc.Implementation.NetApi.NetApiOpcServer`2[TNetApiOpcServer,TServer]
Module: OpcLabs.EasyOpcClassic.dll
Assembly: OpcLabs.EasyOpcClassic, Version=5.80.192.1, Culture=neutral, PublicKeyToken=6faddca41dacb409
CustomAttributes:
FullyQualifiedName: C:\Program Files (x86)\Control-See\UCME-OPC\BIN\OpcLabs.EasyOpcClassic.dll
MDStreamVersion: 131072
MetadataToken: 1
ModuleHandle: System.ModuleHandle
MDStreamVersion: 131072
ModuleVersionId: f48df173-6b5a-4a46-9d9a-48d760525f02
Name: OpcLabs.EasyOpcClassic.dll
ScopeName: OpcLabs.EasyOpcClassic.dll
Message: Problem browsing OPC Data Access (OPC-DA) branches.
Source:
StackTrace:
TargetSite:
We are using:
OPC Studio 2024.1 (5.80.278.1)
OpcLabs.QuickOpc Nuget version 5.80.192
Thank you.
Michael
Please Log in or Create an account to join the conversation.