FAQ - Error messages

  • At the start of TAP/KiTAP/TAP-M the error message "Error 7 - Hardlock wurde nicht gefunden" appears.Screenshot
  • This error message may occur with TAP programs that use the so called Hardlock encryption (blue USB or black parallel port dongle) and may have several causes:  
    • The dongle is not connected to the computer
    • In this case just plug in the dongle ;-)
    • The dongle is connected, but the red control light (USB version only) at the end of the dongle isn't illuminated, i.e. the dongle is not ready for operation
    • Most likely the driver for the dongle isn't installed corrrectly or not installed at all.
      You'll find a separate installation file for the driver in the download section.
      In case this also doesn't lead to an operational dongle, only a defect of the USB interface or the dongle itself remains as a plausible cause of failure. In that case please contact us directly.
    • The installed version of the TAP program doesn't match the encoding of the dongle.
    • The serial number of the installed version must match the serial number on the dongle.
      If several licenses are in use at your institution, a mix-up of the dongle is most likely the cause for this error.
      In any other case dongle and/or encoding are faulty. In that case please contact us directly.
  • During work and often at the end of a subtest the error message "Error 14 - Hardlock-Treiber kann nicht geladen werden" appears
  • This error message also only occurs using the so called Hardlock encryption (see above) and has appeared only on Windows 2000 until today.
    In many cases the error message "freezes" and the program has to be killed using the Windows task manager. According to our experience the problem can only be reliably solved by switching to the newer HASP encryption system.
    Please contact us directly for the necessary exchange delivery.
  • At the start of TAP/KiTAP/TAP-M the error message "Error 7: HASP HL Key nicht gefunden"Screenshot or "Error 7: HASP HL Key not found"Screenshot appears
  • This error message may occur with TAP programs that use the so called HASP encryption (green USB dongle) and has to plausible causes:  
    • The dongle is not connected to the computer
    • In this case just plug in the dongle ;-)
    • The dongle is connected, but the red control light at the end of the dongle isn't illuminated, i.e. the dongle is not ready for operation
    • Most likely the driver for the dongle isn't installed correctly or not installed at all.
      You'll find a separate installation file for the driver in the download section.
      In case this also doesn't lead to an operational dongle, only a defect of the USB interface or the dongle itself remains as a plausible cause of failure. In that case please contact us directly.
  • At the start of TAP/KiTAP/TAP-M or a subtest the error message "Error 31: Feature nicht gefunden"Screenshot or "Error 31: Feature not found"Screenshot appears
  • This error message also only occurs using the so called HASP encryption (see above).
    The cause is, that the encoding of the installed version of the TAP program doesn't match the encoding on the dongle (the serial numbers must match).
    If several licenses are in use at your institution, a mix-up of the dongle is most likely the cause for this error.
    In any other case dongle and/or encoding are faulty. In that case please contact us directly.
  • At the start of TAP/KiTAP/TAP-M and a subtest the error message "Can't open the TVicHW32 driver" appears Screenshot
  • This message is most likely caused by a problematic default value in the settings of the driver for the reaction keys and appears more often on Windows Vista/7 and when using a user account on Windows XP.
    The "guilty" value is located in the Windows registry in the branch "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TVicHW32" ("HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TVicHW64" on 64-bit systems). In this branch change the value of the parameter "Start" from "3" to "2" and reboot the system.
    For your convenience or if you are not familiar with editing the Windows registry manually you'll find an appropriate file for correcting the value in the download section.
    Another possible cause of this error message is the missing installation of the driver in general; therefore please make sure that the selection ""Install the parallel port driver" is activated during installation of the TAP program (which is the default setting).
    If the TAP program is used on a 64-bit version of Windows (XP-64, Vista-64 oder 7-64), this error message may also occur. Then the installation program hasn't all the necessary 64-bit drivers. In that case please contact us directly.
  • When calling up a test result the error message "can't open file <Pfad zur pdt-Datei>(error2: das System kann die angegebene Datei nicht finden.)" appears Screenshot
  • This message appears due to the fact that the personal data file belonging to a subject can't be found. The probable cause is that a point has been set at the end of the subject's name.
    The data storing procedure of the TAP programs requires a folder with the name of the subject - but points at the end of a folder name are silently ignored by Windows, whereas they are allowed at the end of a file name.
    Therefore the TAP program can't locate the personal data file matching the folder's name.
    You'll find the corresponding file inside the storing directory of the TAP program (by default "My files" inside the subfolder "tap"/"kitap"/"tapm"), down to the folder of the examiner (extension ".vl") and then to the folder of the subject.
    There you should find a corresponding file with the extension ".pdt", where most likely an unnecessary point has slipped in.
  • After a subtest has finished a warning message appears: "SetPriorityClass(256) failed" Screenshot 1Screenshot 2
  • This warning message indicates that the real-time priority for the subtests is not available. This usually occurs when a TAP program is run under a user account with limited rights, which hasn't been added to the TAP group yet.
    For more information and instructions to fix the problem see this separate item in the FAQ and the manual Setting up the TAP group in the download section.
    Within Windows Vista/7 this message also occurs with activated user account control and usage of an administrative account. See this separate item in the FAQ and the manual Using Windows Vista/Windows 7 in the download section.
  • When calling "Options>reaction keys" and starting a subtest the error message "Parallel port not found..." appears Screenshot
  • This message occurs if the TAP program can't determine any suitable parallel ports. If you are using an upgraded parallel port please make sure that it's installed correctly and that the card is plugged in before program start.
  • When starting a subtest the error message "lpt/set_port: Invalid argument" appears Screenshot
  • This message occurs if the LPT port chosen within "Options>reaction keys" contains an invalid address ("0x0000"). Then choose the correct parallel port (by default LPT 1 with the address "0x0378").
    If the address "0x0000" is shown for every parallel port, an upgraded parallel port has yet to be set up manually. An appropriate manual is available in the download section.
    Also note that this setting is user account specific. When changing the Windows user account you should check this setting and change it if necessary.
  • When choosing "Profile" beneath the results list to call up a test profile the error message "No corresponding test found." appears Screenshot
  • This message may occur on the one hand if there is indeed no corresponding (read: normed) test result available for the selected subject, on the other hand if there are general problems with the output of normative values. There could be several causes in turn. You'll find details in this separate item of the FAQ.

Top