Page Comparison

HASP key is not connected.

Connected HASP key serial number is different from
AutoCode Intellect serial number (a HASP key for
the software by another manufacturer is used).

Connect the HASP key with the correct serial
number.

Check if the HASP key that is being connected
is a network key (usually red) and, if not,
connect the network protection key.

HASP License Manager Service (hasplms.exe) is not
installed.

Install the license manager onto the computer
with the HASP key connected and launch it.

Blocked traffic at Port 475 where the HASP key
installed or protected module is running (network
dataflow may be blocked by Windows brandmauer
of, for example, antivirus software).

Disable all software that may block access to
HASP key.

No license for the Program Number/Feature ID is
added to the HASP key. The key firmware does not
match the registered build.

Two HASP keys with the same serial number
installed on the computer and the one detected does
not have the feature set.

Connect HASP keys one-by-one to see which
one works fine with the module.

C:\WINDOWS\system32\hasplms.exe is blocked
by the brandmauer or antivirus.

Add the module to the blocking exceptions
list.

HASP License Manager Service (hasplms.exe)
stopped working.

Occurs when terminal services are detected. For
example, Microsoft Terminal Server (including
Remote Desktop services), Citrix Winframe/
Metaframe etc.

HASP key should not be connected to a
computer that has active terminal software
installed. The manufacturer may control this
option by allowing or prohibiting operation
on terminal server. HASP key update is
required.