Using LimeLM in a webserver

We are using LimeLM in a standalone application and it works fine. I also wrote a standalone utility for handling LimeLM functionality on client machines and that works fine as well. We tried adding LimeLM to a webserver application and it returns a value we do not know the meaning of in Public Shared Function IsActivated() at the native.IsActivated call. When a client (via browser) accesses the server, the login page is served up. We added the IsActivated check in the code that serves up this page and for diagnostics we displayed the result of that call on the page.On the native.IsActivated(versionGUID) call it returns a 1. I do not see a case statement for a value of 1. (7=corrupt dat, 11=CoInitializedEx failed,17=running in a vm)Can someone tell me what a return value of 1 equals? And should we be able to use this activation check in a webapp running on iis?

As always, read the FAQ: https://wyday.com/limelm/help/faq/#useful-reports

You're using a particularly ancient version of TurboActivate. Upgrade to the latest version (again, that FAQ entry talks about how to determine the version you're using, how to properly upgrade, etc., etc., etc.).

Secondly, don't directly dig into native calls when we've written the wrapper. Use the interface as is.

So, after you've upgraded TurboActivate to 4.3.0, and upgraded the integration file (in your case, TurboActivate.vb -- again, see the FAQ), just call ta.IsActivated() and read the result (True or False). Also handle exceptions.

Follow the example.

Reply
Discard post