- Posts: 71
- Thank you received: 10
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 COM
- Connections, Reconnections, COM/DCOM
- Issues connecting to DeltaV servers.
Issues connecting to DeltaV servers.
22 Feb 2019 18:38 #7129
by admin
Replied by admin on topic Issues connecting to DeltaV servers.
Thank you for letting us know. Yes, if your architecture allows you to isolate the client part into a separate 32-bit process, that is the way to overcome the issue.
If ever somehow I get access to the Emerson system, I would still like to investigate how it is set up, and whether it can't be made to work.
Best regards
If ever somehow I get access to the Emerson system, I would still like to investigate how it is set up, and whether it can't be made to work.
Best regards
Please Log in or Create an account to join the conversation.
22 Feb 2019 16:59 #7128
by MPick
Replied by MPick on topic Issues connecting to DeltaV servers.
For the sake of closure: we've opted to remove the OPC client component from our software and recompile it as its own 32-bit application. We looked into the OPC Data Link solution but it has its own separate licensing which we would be expecting our clients to purchase from Emerson to connect to use our product, and it looks like some care needs to be taken with the data link server and the normal server as to not overload the machine (according to the aforementioned knowledge base article)
Given that you mentioned its actually quite hard to build a 32bit server that cant accept connections from 64 bit clients it looks like Emerson may have done this intentionally to sell licenses for a product that would otherwise not be needed.
Given that you mentioned its actually quite hard to build a 32bit server that cant accept connections from 64 bit clients it looks like Emerson may have done this intentionally to sell licenses for a product that would otherwise not be needed.
Please Log in or Create an account to join the conversation.
10 Feb 2019 09:30 - 10 Feb 2019 09:30 #7075
by support
Replied by support on topic Issues connecting to DeltaV servers.
Hello,
what do you mean by " KEPServerEX could not access DeltaV OPC, with similar error" - what is the error then? I think that it is pretty significant that the error we are dealing with is "Class not registered", and if it was something else, it is likely to be a different problem.
KepServerEX runs as a service and that's why you can change its process' identity. When somebody uses QuickOPC in its project, it is up to him how the process is run. In most cases, this is simply a desktop app, which then runs under the current interactive user account - and you can't influence that using DCOMCNFG. If the account needs to be changed, the developer can decide to turn the app into a service, or simply run it under a different account for a single test, etc., or use command line tools to run it under spcific account - there are many options, it all depends on the specific usage case. This also applies to WIN-911: this part they have done themselves, and I do not know what and how they do. Anyway, security (Account) related issues usually do not manifest themselves through "Class not registered" error.
Best regards
what do you mean by " KEPServerEX could not access DeltaV OPC, with similar error" - what is the error then? I think that it is pretty significant that the error we are dealing with is "Class not registered", and if it was something else, it is likely to be a different problem.
KepServerEX runs as a service and that's why you can change its process' identity. When somebody uses QuickOPC in its project, it is up to him how the process is run. In most cases, this is simply a desktop app, which then runs under the current interactive user account - and you can't influence that using DCOMCNFG. If the account needs to be changed, the developer can decide to turn the app into a service, or simply run it under a different account for a single test, etc., or use command line tools to run it under spcific account - there are many options, it all depends on the specific usage case. This also applies to WIN-911: this part they have done themselves, and I do not know what and how they do. Anyway, security (Account) related issues usually do not manifest themselves through "Class not registered" error.
Best regards
Last edit: 10 Feb 2019 09:30 by support.
Please Log in or Create an account to join the conversation.
08 Feb 2019 16:18 #7073
by CZhong
Replied by CZhong on topic Issues connecting to DeltaV servers.
Thanks for sharing these insights. The KBA introduces how to install a separate DeltaV OPC Server, which will support 64 bit OPC client. I tried to use WIN911 (it also adopts OPC Labs component) to talk to DeltaV OPC server and encountered same "class not registered" error. I tried that separate OPC Server, called OPC Data Link, and it worked.
As you pointed out, maybe there is something else wrong. Interestingly, I also found KEPServerEX could not access DeltaV OPC, with similar error. Then I found a KBA from their website to resolve this issue. What I did is to open Component Services through DCOMCNFG command, and then change Identity to a specific DeltaV user for application KEPServerEX6.4 under DCOM Config.
I am wondering if a similar fix would also work for OPC Labs OPC DA Client. Could you please let me know which application (or application ID) under DCOM Config that WIN911 uses for its OPC DA Client?
As you pointed out, maybe there is something else wrong. Interestingly, I also found KEPServerEX could not access DeltaV OPC, with similar error. Then I found a KBA from their website to resolve this issue. What I did is to open Component Services through DCOMCNFG command, and then change Identity to a specific DeltaV user for application KEPServerEX6.4 under DCOM Config.
I am wondering if a similar fix would also work for OPC Labs OPC DA Client. Could you please let me know which application (or application ID) under DCOM Config that WIN911 uses for its OPC DA Client?
Please Log in or Create an account to join the conversation.
07 Feb 2019 05:42 - 07 Feb 2019 05:44 #7067
by support
Replied by support on topic Issues connecting to DeltaV servers.
Hello,
and thank you for the valuable information. Although I could tell from the analysis that this is the case (i.e. DeltaV not supporting 64 bit clients), I was not aware that it is somehow a known (or confirmed?) issue by Emerson. I do not know what the KBA you mentioned is, or how to access it (we are not Emerson customers; Googling it has not helped). If you can provide the text of it (even privately), I would appreciate it.
Anyway, although I could tell that DeltaV does not work from 64 bits clients, I wanted (and still want) to continue the investigation as to how this is possible. The reason for that being, it is actually *difficult* to write an OPC Server that would really not support 64 bit clients, aside from registration errors (as long as we are talking out-of-process servers, which is the case here). It looks like Emerson must have either made some simple mistake in server registration or development, or must have worked really hard to intentionally prevent the 64-bit clients from working.
Best regards
and thank you for the valuable information. Although I could tell from the analysis that this is the case (i.e. DeltaV not supporting 64 bit clients), I was not aware that it is somehow a known (or confirmed?) issue by Emerson. I do not know what the KBA you mentioned is, or how to access it (we are not Emerson customers; Googling it has not helped). If you can provide the text of it (even privately), I would appreciate it.
Anyway, although I could tell that DeltaV does not work from 64 bits clients, I wanted (and still want) to continue the investigation as to how this is possible. The reason for that being, it is actually *difficult* to write an OPC Server that would really not support 64 bit clients, aside from registration errors (as long as we are talking out-of-process servers, which is the case here). It looks like Emerson must have either made some simple mistake in server registration or development, or must have worked really hard to intentionally prevent the 64-bit clients from working.
Best regards
Last edit: 07 Feb 2019 05:44 by support.
Please Log in or Create an account to join the conversation.
06 Feb 2019 03:37 #7066
by CZhong
Replied by CZhong on topic Issues connecting to DeltaV servers.
Guys,
It is a known issue that DeltaV OPC server does not support 64bit OPC client. Emerson does provide a program called OPC Data Link to provide a new 64 bit OPC Server. Check Emerson's KBA NK-1600-0114 for more information.
Is there an easy way to tell if an OPC client is built for 64 bit or 32 bit?
It is a known issue that DeltaV OPC server does not support 64bit OPC client. Emerson does provide a program called OPC Data Link to provide a new 64 bit OPC Server. Check Emerson's KBA NK-1600-0114 for more information.
Is there an easy way to tell if an OPC client is built for 64 bit or 32 bit?
Please Log in or Create an account to join the conversation.
30 Jan 2019 17:17 #7048
by support
Replied by support on topic Issues connecting to DeltaV servers.
Thank you, now it is clearer, with the cached info not skewing the result. Unfortunately, connecting to the server from 64-bit process still isn't possible, with any combination of the flags.
In your new setup, will there still be two computers, or, will everything be on just one? Either way, will there be access to the computer where the actual server runs? Exploring its setup (mainly registry settings) is something we could not do so far.
Best regards
In your new setup, will there still be two computers, or, will everything be on just one? Either way, will there be access to the computer where the actual server runs? Exploring its setup (mainly registry settings) is something we could not do so far.
Best regards
Please Log in or Create an account to join the conversation.
29 Jan 2019 15:48 #7047
by MPick
Replied by MPick on topic Issues connecting to DeltaV servers.
Looks like you were correct, after restarting the machine the results are different.
I'm currently trying to set up a DeltaV test environment that reproduces the issue on a machine you would be able to do as you please with, is there certain software I could start installing to assist? (VS2017, git etc?)
I'm currently trying to set up a DeltaV test environment that reproduces the issue on a machine you would be able to do as you please with, is there certain software I could start installing to assist? (VS2017, git etc?)
C:\Users\[companyname]\Desktop\[companyname]\BuildOutput_2019-01-23\BuildOutput>ComCreateTest32.exe {C3B72AB1-6B33-11D0-9007-0020AFB6CF9F} CLSCTX_ALL,CLSCTX_ACTIVATE_32_BIT_SERVER
CLSID: c3b72ab1-6b33-11d0-9007-0020afb6cf9f
CLXCTX: 262167
Bitness: 32
Success
C:\Users\[companyname]\Desktop\[companyname]\BuildOutput_2019-01-23\BuildOutput>ComCreateTest32.exe {C3B72AB1-6B33-11D0-9007-0020AFB6CF9F} CLSCTX_ALL,CLSCTX_ACTIVATE_64_BIT_SERVER
CLSID: c3b72ab1-6b33-11d0-9007-0020afb6cf9f
CLXCTX: 524311
Bitness: 32
*** Error: Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))
C:\Users\[companyname]\Desktop\[companyname]\BuildOutput_2019-01-23\BuildOutput>ComCreateTest64.exe {C3B72AB1-6B33-11D0-9007-0020AFB6CF9F} CLSCTX_ALL,CLSCTX_ACTIVATE_32_BIT_SERVER
CLSID: c3b72ab1-6b33-11d0-9007-0020afb6cf9f
CLXCTX: 262167
Bitness: 64
*** Error: Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))
C:\Users\[companyname]\Desktop\[companyname]\BuildOutput_2019-01-23\BuildOutput>ComCreateTest64.exe {C3B72AB1-6B33-11D0-9007-0020AFB6CF9F} CLSCTX_ALL,CLSCTX_ACTIVATE_64_BIT_SERVER
CLSID: c3b72ab1-6b33-11d0-9007-0020afb6cf9f
CLXCTX: 524311
Bitness: 64
*** Error: Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))
C:\Users\[companyname]\Desktop\[companyname]\BuildOutput_2019-01-23\BuildOutput>Please Log in or Create an account to join the conversation.
27 Jan 2019 08:24 - 27 Jan 2019 08:24 #7043
by support
Replied by support on topic Issues connecting to DeltaV servers.
Thank you very much again. Unfortunately, the outcome is not as I have hoped. Specifically, the combination of 64-bit process with CLSCTX_ACTIVATE_32_BIT_SERVER has still not succeeded.
But, I also find the errors "The RPC server is unavailable" somewhat weird with the CLSCTX_ACTIVATE_64_BIT_SERVER option. Isn't it possible that all these latest results have been influenced by the previous network disconnection (cached)? If you are not completely sure, can you restart machine A and retest?
Note that this about my last option/idea. As I wrote earlier, most likely something is wrong with the server registration (or the way DCOM handles it - it can also be Microsoft problem). Without having the system, or its repro having the same issue (and I mean the whole system - including machine B ) available in the lab for investigation, I do not see how to proceed further then.
Best regards
But, I also find the errors "The RPC server is unavailable" somewhat weird with the CLSCTX_ACTIVATE_64_BIT_SERVER option. Isn't it possible that all these latest results have been influenced by the previous network disconnection (cached)? If you are not completely sure, can you restart machine A and retest?
Note that this about my last option/idea. As I wrote earlier, most likely something is wrong with the server registration (or the way DCOM handles it - it can also be Microsoft problem). Without having the system, or its repro having the same issue (and I mean the whole system - including machine B ) available in the lab for investigation, I do not see how to proceed further then.
Best regards
Last edit: 27 Jan 2019 08:24 by support.
Please Log in or Create an account to join the conversation.
25 Jan 2019 20:53 #7042
by MPick
Replied by MPick on topic Issues connecting to DeltaV servers.
Sorry again for the delay, here is the output for this test.
C:\Users\[companyname]\Desktop\[companyname]\BuildOutput_2019-01-23\BuildOutput>tests.bat
C:\Users\[companyname]\Desktop\[companyname]\BuildOutput_2019-01-23\BuildOutput>ComCreateTest32.exe {C3B72AB1-6B33-11D0-9007-0020AFB6CF9F} CLSCTX_ALL,CLSCTX_ACTIVATE_32_BIT_SERVER
CLSID: c3b72ab1-6b33-11d0-9007-0020afb6cf9f
CLXCTX: 262167
Bitness: 32
Success
C:\Users\[companyname]\Desktop\[companyname]\BuildOutput_2019-01-23\BuildOutput>ComCreateTest32.exe {C3B72AB1-6B33-11D0-9007-0020AFB6CF9F} CLSCTX_ALL,CLSCTX_ACTIVATE_64_BIT_SERVER
CLSID: c3b72ab1-6b33-11d0-9007-0020afb6cf9f
CLXCTX: 524311
Bitness: 32
*** Error: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
C:\Users\[companyname]\Desktop\[companyname]\BuildOutput_2019-01-23\BuildOutput>ComCreateTest64.exe {C3B72AB1-6B33-11D0-9007-0020AFB6CF9F} CLSCTX_ALL,CLSCTX_ACTIVATE_32_BIT_SERVER
CLSID: c3b72ab1-6b33-11d0-9007-0020afb6cf9f
CLXCTX: 262167
Bitness: 64
*** Error: Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))
C:\Users\[companyname]\Desktop\[companyname]\BuildOutput_2019-01-23\BuildOutput>ComCreateTest64.exe {C3B72AB1-6B33-11D0-9007-0020AFB6CF9F} CLSCTX_ALL,CLSCTX_ACTIVATE_64_BIT_SERVER
CLSID: c3b72ab1-6b33-11d0-9007-0020afb6cf9f
CLXCTX: 524311
Bitness: 64
*** Error: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
C:\Users\[companyname]\Desktop\[companyname]\BuildOutput_2019-01-23\BuildOutput>Please Log in or Create an account to join the conversation.
Moderators: support
- Forum
- Discussions
- QuickOPC-Classic in COM
- Connections, Reconnections, COM/DCOM
- Issues connecting to DeltaV servers.
Time to create page: 0.069 seconds