(a customer's response:)

From: e...
Sent: Thursday, July 10, 2014 3:14 PM
To: Zbynek Zahradnik
Subject: My deployment problem...

... has been properly solved, thanks your prompt and correct answer!!!


Hello Zbynek,

I've done exactly what you suggested, first changed the platform into x86, everything worked properly!
Then I installed the OPC Core Component x64 and everything worked fine also with AnyCPU option.

The OpcEnum.exe was probably too old, therefore the BrowseOpcServers went to the Windows Registry directly and could get only the ClsIDs but nothing else.


[...] you helped a lot!!!

I wish you a good continuation of your holiday and all the best!

With my best regards,
E...



Best regards | Mit freundlichen Grüssen

E...

(investigation, and suggestions)

Determined that it is a 64-bit OS, and the app is running as 64-bit process (is compiled for AnyCPU).

The problem might cuased by the fact that OPC Core Components (OPCEnum) do not work well, and the BrowseServers method resorts to enumerating the servers from the registry.

Suggested to

1. Try compiling the app for 32-bits - this will cause it to use 32-bit OPCEnum which usually works well.

and/or

2. Install the latest OPC Core Components for x64 from OPC Foundation web site, or those that we redistribute with QuickOPC.

(a summary of customer's problem:)

In one of the deployments, the EasyDAClient.BrowseServers method returns a collection with the server elements, but the elements only have their CLSID filled in. The remaining pieces (such as ProgID) are empty.

This happens is on a computer where the application has been deployed manually (i.e. the QuickOPC installation program has not been run).