Skip to main content

Support

Support Request

Commmon Questions

If there is an issue with the Remote Update utilities randomly closing after about 10 seconds, then the computer may not have a complete installation of the KEYLOK libraries and executables. This issue is typically caused by the KEYLOK anti-debugging utility not being installed on the system. The KEYLOK Remote Update utilities automatically call the anti-debugger to protect the encryption/decryption of the AUTHORIZE.DAT file. To resolve this issue, run the KEYLOK installer, install.exe, on the problematic machine. 

If you find that the issue persists with the anti-debugger successfully installed (ppmon.exe in SYSWOW64 or ppmon64.exe in System32), please contact KEYLOK support at support@keylok.com. 

This issue is caused by the dongle being removed without calling the cleanup function TERMINATE. Each time a program authenticates with the dongle, the dongle creates a new session for that program. Due to this configuration, if TERMINATE is not called, the dongle will eventually run out of memory to keep track of sessions and start failing authentication.  This issue is made worse by unplugging and re-inserting the dongle repeatedly. The TERMINATE function disconnects the session associated with the program that called it and cleans up the dongle’s memory. If the TERMINATE function is called before re-authentication, then this issue is typically resolved. 

This issue typically occurs when an older version of the KEYLOK libraries is used. The older libraries have a dependency on the Visual C++ Redistributable for Visual Studio 2012. The issue can be resolved by either installing the latest version of the KEYLOK libraries using the KEYLOK installer (install.exe) or by installing the redistributable from Microsoft’s website. 

If the issue persists feel free to contact KEYLOK support at: support@keylok.com  

The RTC lasts for 3 years while unplugged. Our RRTC dongles recharge when connected to a USB port. The Fortress RTC is programmed with the date and time when we receive it from our manufacturer. Our manufacturer uses tools to set up the dongle for programming by KEYLOK, including setting the RTC. Our API does not support changing the RTC’s value. 

Yes, many of our customers protect applications and systems in virtual environments. Typically, there are multiple operating systems, hardware components, and virtual tools in our customers’ environments. Because iterations are endless, contact us to discuss your specific needs for application protection and licensing in virtual environments. KEYLOK is also partnered with SEH Technology, a provider of the well-known Dongle Server. This physical box hosts dongles, allowing virtual client machines to access a USB dongle as if it were physically attached. For additional options, please reach out to support at support@keylok.com

You can use KLTool.exe for programming your keys using the “Program Fortress” tab.

Cause: It may be that you're using the wrong KLTool.exe with the keys.

Solution: The tools that come with your Company Unique SDK are specific to your production keys and the tools that came with your DEMO SDK cannot be used with the production keys. You will need to install your Company Unique SDK and then test the keys with these tools.

Option A: Install Utility Command Line Arguments

Install.exe Utility
Delimiters

Valid command line delimiters are ‘/’ or ‘\’ or ‘-‘

A space is required before each delimiter and options cannot be combined (i.e. ‘/QN’ is illegal, but ‘/Q /N’ is legal).
/C

Install network Client files and USB drivers

Allows local USB dongle or remote USB or parallel port dongle
/F Install Fortress files only
/NF Install Fortress TCP/IP server networking files to allow remote access to a Fortress dongle via a TCP/IP network.
/Q Quiet mode install – displays only fatal errors
/S:<IP address> Valid only for a network client install. Forces the client to attempt to connect to the dongle server at <IP address>. You may also specify the network name of the server instead of its IP address.
/U

Uninstall 

Removes all previously installed files

Option B: Copy Applicable dll

Copy applicable dll (32/64/standalone/networking) into your application directory. If using anti-debugger, you’ll need to copy the anti-debugger software to the appropriate system directory.

Yes, you can run multiple Fortress keys with the same Company Unique Codes on the same machine. This feature is only available for Windows currently. If you need this functionality, please contact Technical Support to obtain sample code in your development language.

To run your existing application with Fortress, you will need to compile your application with the latest libraries. These libraries can be found on the SDK that came with your KEYLOK2 order. For more details please email support@keylok.com to receive our Fortress migration guide.