You are welcome

It would be nice to share here the steps, or just the basic info about what you needed to do to make it work, so that others can benefit from that information in the future.

Yes, I think that it is the OPC server that is reporting "Class is not licensed for use", we are just delivering this error to you.

We have seen following issue with some FactoryTalk products earlier. It may (or may not) be the issue you are facing.

Vast majority of OPC server are so-called out-of-process servers, i.e. they are implemented in an EXE and run in a separate process. Some/all? Rockwell servers are in-process, i.e. implemented in a DLL that gets loaded into the client process. And, they sometimes have a licensing requirement that only allows you to run them locally, i.e. the OPC client must be on the computer as the OPC server.

For *remote* connections to servers that are implemented in a DLL, Microsoft DCOM automatically provides a host process ("surrogate"), and loads the DLL into this process. Apparently, Rockwell uses this knowledge to detect that the OPC server is being used remotely: If it is loaded into a surrogate process and not licensed for remote usage, it will issue "Class is not licensed for use" error.

So far so good. But the DLL is 32-bit, and OPC clients (on 64-bit systems) can now be either 32-bit or 64-bit. This is not a problem with EXE-based servers, because they run in separate processes and communicate over (L)RPC provided by Microsoft COM. But when the server is implemented in a 32-bit DLL, it *cannot* be loaded into a 64-bit client. In this case, Microsoft COM still allows it work. Similarly as with the remote situation, it will provide a 32-bit surrogate process for the DLL, and run it in this process.

In this case, i.e. when the OPC client is 64-bit, the Rockwell server thinks it is also being used remotely - because it runs in a surrogate.

In the past, the workaround was to run the OPC client in a 32-bit process. This can be done either by building it for "x86" instead of "AnyCPU", or by modifying the EXE after it is built, using the CorFlags.exe tool.

Regards

Error code -2147221230 (0x80040112) corresponds to "Class is not licensed for use". This time, however, it not "our" error. It is a common, Microsoft-defined COM error code that comes from the server itself.

So, you may need to look into licensing on the server side.

In addition, because you have mentioned FactoryTalk and we have seen similar issues with it in the past, can you please answer following questions:

1. Is your .NET application compiled for "AnyCPU", or for x64 or x86?
2. Is the operating system you are running on 32-bit or 64-bit?
3. I assume the server and the client are on the same machine - please confirm.
4. If you have moved your application/server from a different computer, was the original system 32-bit or 64-bit?

Thank you

The actual error code is -1073419774 as it was in your original email (the minus sign is significant). It corresponds to 0xC004EA02.

We do not provide a list of error codes. There is an error message and more details that come with each error. The code could you the Exception property, to provide that information. Had it done that, the error message would be:

Not allowed to run by the license. You might be using a trial license, and the version of the software you are using is obsolete. Obtain a recent version to resolve this problem.

I need a picture of the License Manager screen with the license installed. You can post it here, or send by email.

Best regards