Online Forums
Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.
Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.
Do not use the Contact page for technical issues.
Issue in production PC with QuickOPC 5.63
Best regards
Please Log in or Create an account to join the conversation.
I found the issue, it was a typing errore in the licenseId of the Method.
I apologize for disturbing you unnecessarily.
Please Log in or Create an account to join the conversation.
- I used RegisterManagedResourceWithExistenceCheck Method and no exceptions are thrown.
- If I retrieve the serial number "1111111120" and using the example it gives me that the License is a Trial license.
- I tried using the IL DASM tool and the key matches the one used in the source code.
Please Log in or Create an account to join the conversation.
I followed every step of the troubleshooting section and:
-
Please Log in or Create an account to join the conversation.
Have you tried the Troubleshooting hints described here?: opclabs.doc-that.com/files/onlinedocs/OPCLabs-OpcStudio/Late...esource%20License%20Store.html (the URL is for latest QuickOPC version, but most of the information applies to your version as well).
Regards
Please Log in or Create an account to join the conversation.
I have a Multipurpose ultimate license for QuickOPC 5.63 version and I'm experiencing issues running executables in a production PC.
I'm using the "RegisterManagedResource" method in my Visual Studio project (development PC) but once I deploy the .exe and try to run it in a production PC it gives me back some errors (attached you can find the screenshot of the error).
The weird behaviour is that if I install the license (on production pc) with the license manager, everything works fine. But of course, I'm using the "RegisterManagedResource" method in the VS project just to avoid installing licenses on production PCs. As I read in your forum: "The main advantage of this method is that it does not require any additional actions during deployment. Also, because the Managed Resource License is the first one in the search order, you have a guarantee that if you properly place a specific valid license key into the managed resource license store, it will be the one actually used - it cannot be changed by License Manager, for example. The disadvantage of this method is that you need to put extra code and data into your application, before building it."
Is it there something that I'm missing?
Thanks.
Please Log in or Create an account to join the conversation.