Log In
Home
03/04/2014
Offline
I am writing a 64-bit OPC DA classic server. I can connect to it without trouble with a 64-bit DA client. However, I cannot connect with a 32-bit client. The attempt to open the connection from the 32-bit client produces “Server execution failed”. The 64-bit server is already running.
I have installed the latest version of OPCEnum, 64-bit version (V3.00.107).
The 32-bit client can see the 64-bit server in OPCEnum, so it is not a problem with OPCEnum.
Is there something that I need to do to register the 64-bit server in the Windows registry? A 32-bit server registers in HKCR\Wow3264Node\CLSID, while a 64-bit server registers in HKCR\CLSID. Does a 64-bit server need to appear in both places in the registry?
Is there some other reason why a 32-bit client cannot connect but a 64-bit client can? For what it’s worth I’ve tried several 32-bit clients and they all fail in the same way.
05/30/2017
Offline
It depends on how the 64-bit server registers itself. If it manually creates keys then they will need to manually create registrations in both locations. If it used Microsoft provided ATL APIs the the dual registration may occur automatically (not sure about this).
No matter which I believe the dual registration is required because, from the perspective of a 32-bit application, the 64-bit registry keys do not exist.
Note that a 32-bit process cannot load a 64-bit inproc DLLs and could have problems launching a 64-bit EXE (the 64-bit Program Files also does not exist). I would try testing with a pre-started 64 bit EXE and see if that makes a difference.
03/04/2014
Offline
Thank you, Randy. I added the registry entries manually to Wow3264Node and I was able to make the connection. Now I just need to figure out how to add them through code. It does not appear that the ATL registration functions are going to do it for me automatically.
1 Guest(s)
Usage Policy