Knowledgebase Home > LM-X License Manager > LM-X Developer > Usage | Favorites | Login Knowledgebase Home | Favorites | Login
Search the Knowledgebase Browse by Category or Article ID

[Advanced Search]
View Articles by Category
There are no sub categories
Usage rss button
Answers to developers' commonly asked questions about using LM-X.
 (Page 1 of 2)     «« |  Prev | 1 | 2 | Next | »»
There were 31 articles found in this category:
  1. questionHow do I report a bug I've found in LM-X License Manager?
    To report a bug in LM-X, please follow the procedure below so that we can best understand and resolve the problem: Create a reproduction of the bug that includes a small example demonstrating the problem. Include instructions on how to use your reproduction. If needed, you may send your own ap ...

  2. questionWhat Linux compilers does LM-X License Manager support?
    For Linux (x86 and x64), LM-X supports the use of GCC (GNU Compiler Collection). Other compilers that use output compatible with GCC, including custom compilers, will also work but are not officially supported.

  3. questionCan I use dongles with LM-X License Manager?
    Yes, dongles may used with LM-X, and can be a particularly good option for licensing virtual machines. You may use 3rd-party dongles, which require some custom programming, or purchase dongles from X-Formation (provided by Aladdin) that work out of the box, without need for further customization.

  4. questionCan LM-X License Manager detect virtual enviroment?
    With LM-X you can allow or forbid to use your application in a virtual enviroment. LM-X detects most of virtualization technologies including VMWare, Microsoft Virtual Server, VirtualBox. Virtual machine environments are typically undesirable for use with software licensing. Normally, operating ...

  5. questionHow does software protected by LM-X License Manager find a license file?
    Every LM-X protected application has a search path for licenses. The application will search for licenses in the following order: 1. Preset path and/or automatic server discovery (this information is provided by your application vendor). 2. The environment variable VENDOR_LICENSE_PATH. The VEND ...

  6. questionHow to use the LM-X License Manager pay-per-use licensing model
    The LM-X pay-per-use licensing model lets you bill your customers based on their actual usage of your software. To determine the usage, you ask the customer to write the usage information to a pay-per-use SQLite database each month (or other period) and send the database file to you. (You can f ...

  7. questionUsing dongles under Linux x64 with LM-X License Manager v3.3 and v3.31
    For LM-X v3.3 and 3.31, we updated our dongle library from Hasp HL to Sentinel HASP v5.0. Our supplier, Aladdin, does not compile the dongle library under Linux x64 using the -fPIC flag. Unfortunately, this means that you cannot use our shared object liblmx-vendor.so together with dongles. To ma ...

  8. questionRestricted access licensing
    LM-X License Manager enables you to precisely control which users are authorized to access your application. Software integrated with LM-X is bound to a license file that enforces usage restrictions and is designed to accommodate standard industry scenarios, such as the following. Node-locked/ma ...

  9. questionHow can I troubleshoot and fix a "System clock has been set back" error?
    If a user experiences a "System clock has been set back" error (see the article, "Why do I get a "System clock has been set back" error?"), the solution is normally to reset the system clock to the correct time. If this does not help, software vendors may resolve the problem by using the resetsy ...

  10. questionHow to use LmxLicenseProvider as an implementation of the abstract base class provided by .NET LicenseProvider
    If you’ve ever used .NET LicenseProvider for your licensing model, you probably know that the default implementations of this abstract class offer only basic features that are unlikely to satisfy today’s needs for security and flexibility. This is where LmxLicenseProvider can help yo ...

  11. questionWhy do I get "Unable to use license server" error when I run a .NET application on 64 bit machine?
    The article concerns 32 bit .NET applications protected with 32 bit LM-X library (lmxnet.dll). When run on a 32 bit machine everything works fine but on an 64 bit system the following error might occur: "Unable to use license server." The problem is that .NET will run the 64 bit version of the ...

  12. questionDongle use on Red Hat Enterprise Linux 4.x not supported
    X-Formation supports dongle use on Red Hat Enterprise Linux 5.x and newer; however, dongle use on Red Hat Enterprise Linux 4.x is not supported. This applies to Fedora Core 4 as well. Enabling dongle support on Red Hat Enterprise Linux 4.x using the SetOption function will cause compilation err ...

  13. questionLicensing your software to run on virtual machines
    LM-X detects most virtualization technologies, including VMWare, Microsoft Virtual Server, and VirtualBox. Virtual machine environments are typically undesirable for licensed software due to the inherent risk of overuse. With LM-X, you can choose to allow or prohibit your application to run in a ...

  14. questionShould I lock my license to only one hostid or use multiple hostids?
    In most cases, locking to an Ethernet card, BIOS or harddisk hostid is enough. If you need more security, you may lock to multiple hostids using one of the following methods: Multiple hostids with 1:1 matching. For example, you might lock a feature to the license server machine hostname, Ethern ...

  15. questionWhich hostid should I use to lock my floating license application to a particular license server machine?
    A good choice for locking a floating license to a particular server machine is to use the Ethernet hostid (the MAC address of the Ethernet card). Almost all machines have an Ethernet card, and information about the Ethernet hostid is available on all platforms. For optimal security, locking to t ...

  16. questionWhich hostid should I use to lock my node-locked license application to a particular machine?
    A good choice for locking a node-locked license to a particular machine is to use the Ethernet hostid (the MAC address of the Ethernet card). Almost all machines have an Ethernet card, and information about the Ethernet hostid is available on all platforms. For optimal security, locking to the B ...

  17. questionLM-X v3.3 now uses non-obfuscated hostids
    With LM-X v3.3, hostids are no longer obfuscated, thereby making it easier to determine to what hardware item the license is locked and how the licensing is performed. For example, versions of LM-X previous to v3.3 used a 16-digit Ethernet hostid (the obfuscated MAC address of the Ethernet card) ...

  18. questionWhy does LMX_Free hang when used within a dll file?
    When you have a dll, you typically have initialization code like the following: BOOL APIENTRY DllMain( HANDLE hModule, DWORD ul_reason_for_call, LPVOID lpReserved) { switch (ul_reason_for_call) { case DLL_PROCESS_ATTACH: case DLL_THREAD_ATTACH: case DLL_THREAD_DETACH: case DLL_PROCESS_DETACH: br ...

  19. questionWhy do I get the message "0x000006BA: RPC server unavailable" when debugging an application in which LM-X is integrated?
    You may see messages similar to the following when debugging an application in which LM-X is integrated: 0x000006BA: The RPC server is unavailable 0xC000001D: Illegal Instruction 0xC0000096: Privileged instruction These messages are part of the virtual machine detection that LM-X performs. This ...

  20. questionWhy do I get a "system time differs more than 24 hours" error in my lmx-server log?
    If your lmx-server.log file reports an error similar to the following, there is a significant discrepancy between the LM-X license server and license client. [2008-09-24 11:44:07] CHECKOUT by pcuratolo@pcuratolo: FRONTEND [2008-09-24 11:44:33] FAIL: Client pcuratolo@pcuratolo system time differs ...

(Page 1 of 2)     «« |  Prev | 1 | 2 | Next | »»
All Content Copyright © 2002-2012 X-Formation. All Rights Reserved.