Thank you. We will make a "caution" note in the documentation, although there are many possible ways and tools the customers can create the installation, and we cannot cover the "traps" presented by all these tools.

I am glad the cause is determined now. I got distracted by the claim that the license on your development computer was installed by the License Manager and still did not work, which in my understanding, in retrospective, was not correct (or maybe it was, but it was later overwritten by your own method).

Best regards

Thank you.

Yes, sure, please uninstall/reinstall the license. That is completely safe. It would not hurt trying.

Regards

I have now tested your license key, particularly with QuickOPC version 2017.1, and could not reproduce the problem. I have another bunch of questions - sorry for that but I am trying to narrow down the options.

1. Is there any computer on which the license works well for you?
2. Is your application running under 32-bit or 64-it process?

3. Let's focus on JUST the development computer for the remainder of these questions. Please confirm that you have used the License Manager to *install* (not just view!) the license on this computer.
4. Please confirm that you have tested the demo application (in your previous post) on THIS computer, and that it had the problem.
5. What operating system/version are you running there? Is it 32-bit or 64-bit?

Just to let you know, we are being approached with similar issue from customers repeatedly, from time to time. and it has never been a problem in the component. The problem has always boiled down to one of the following:

A. The customer is installing the license using License Manager, but under a wrong "Component" (the drop-down on the top).
B. The customer did not know that the license needs to be installed on the "target" computer, i.e. where the component is running, ad not just on the development computer.
C. The license was not installed using License Manager but by some manual method, and the customer has not properly put the license into both 32- and 64-bit parts of the registry.

It should be noted that the License Manager does only limited verification of the license. The actual verification is done by the component. It is therefore quite possible that when the license isn't properly installed, it still shows up in the License Manager.

Regards

Can you run the demo application (UI-based) that ships with the product, let it subscribe to some value, and run for over 30 minutes, to see if it has the same problem?

Thank you

Thank you.

What kind of project is your application? (desktop app, Windows service etc.)? Under which user account is running? I am asking this to verify that the process has access to the registry keys where the license is stored.

Regards