Log In
Home
02/18/2021
Offline
Hello all,
I tried to use the 64 bit Version of our self developed OPC server which works as 32 bit Version for years without any trouble, but the OPC client can’t find the server. Both applications running on the same Win 64 PC.
I installed the newest OPC core components, deleted the DCOM configuration service entry of the 32 bit OPC server, and also cleaned the associated registry entries. Nothing helped.
I am grateful for any ideas.
05/30/2017
Offline
To use 64-bit COM apps you too need the 64but version of Core Components which includes a 64 bit version of OpcEnum.
02/18/2021
Offline
Thanks for the answer.
I installed the OPC Core Components Redistributable (x64) 3.00.108.msi, which is the newest package I found.
05/30/2017
Offline
Is the client using direct registry access to find hosts?
Many clients did and it would prevent them from seeing x64 servers.
Clients should always use OpcEnum to find servers.
02/18/2021
Offline
The OPC Client is a commercial product and works with 64 Bit OPC Servers according to the manufacturer.
In addition, I have tried the Matrikon OPC Explorer, also without success.
Is there a certain sequence that has to be followed when changing an OPC server from the 32 bit variant to the 64 bit variant? So the same application with the same name?
05/30/2017
Offline
Do you have access to this download:
https://opcfoundation.org/deve…..e-servers/
It has sample code that registers servers used to test OpcEnum.
It appears it does not have x64 code.
02/18/2021
Offline
I’m sorry, it looks like that I do not have access to this download.
05/30/2017
Offline
The issue is this: the server registers its component categories in its bitness but only clients with the same bitness can see them. OpcEnum installs a component that allows OpcEnum to Enumerate the categories in a different bitness.
Your server is likely not registering its component categories properly.
I suggest you use regedit to compare the registry entries of servers that do work and your server.
This may allow you to find what is missing.
02/18/2021
Offline
Thanks for the support. I’ll look for another 64 bit OPC server and check the registry entries.
02/18/2021
Offline
The following registry keys were not present. After adding this parts manually, the OPC Client was able to connect to our 64-bit OPC server.
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\AppID\{E421E9FD-C93E-43E0-81A8-293BFF85A35E}]
@=”My OPC DA Server”
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\My_OPC_DA_Server]
@=”My OPC DA Server”
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\My_OPC_DA_Server\CLSID]
@=”{E421E9FD-C93E-43E0-81A8-293BFF85A35E}”
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\My_OPC_DA_Server\OPC]
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\My_OPC_DA_Server\OPC\Vendor]
@=”the”
I copied this registry keys from another PC, where our 64-bit OPC server runs fine and is found by the OPC client application. Basically, the 64-bit variant works, but there must be differences between the two installations. So I am looking for any hint why our OPC server once will be registered properly and once not.
For example, is there a defined procedure for switching an OPC Server from one target platform to another, thus from 32- to 64-bit?
Is it necessary to first unregister the 32-bit OPC server instance and then register the new 64-bit instance?
05/30/2017
Offline
The missing WOW6432Node key registered your x64 server in the 32-bit registry.
The other entries register you server in the 64 but registry. It is not clear why it worked with 64 bit clients without them.
Maybe the issue is you registered your 64 bit server in the 32 bit registry and messed up the COM infrastructure.
1 Guest(s)
Usage Policy