ProtectToolkit Installation Issues
This section describes solutions to some issues you might encounter while installing ProtectToolkit 5.9.1 software components.
NOTE Thales recommends using the Unix Installation Utility to install ProtectToolkit on a Unix/Linux system. If you experience issues while installing ProtectToolkit on Unix/Linux manually, uninstall all packages and begin a fresh installation using the Unix Installation Utility. For more information, refer to Installing ProtectToolkit on Unix/Linux.
The following table lists some commonly encountered installation issues by operating system:
| Operating System | Problem | Solution |
|---|---|---|
| Windows/Unix/Linux | The system locks up after installation of the ProtectServer PCIe 2 Access Provider device driver package. This may happen if a prior version of the device driver exists on the system. |
1.Power down and remove the adapter. 2.Power up. 3.Uninstall all versions (old and new) of the ProtectServer PCIe 2 Access Provider / device driver package. 4.Power down and reinstall the adapter. 5.Power up and reinstall the ProtectServer PCIe 2 Access Provider package. |
| Windows/Unix/Linux | Following reinstallation of a previously removed adapter or the addition of another adapter, the device driver cannot find the device or an adapter is not responding. | Confirm that the adapter(s) are firmly seated in the PCIe slot, then uninstall the ProtectServer PCIe 2 Access Provider package. Following this, perform a fresh install of the ProtectServer PCIe 2 Access Provider package. |
| Windows | When installing a Windows driver, you may receive a warning that the SafeNet driver is not signed. |
This message can safely be ignored. If you have received this message, the version you have received was released before it completed the Microsoft WHQL process. While we do submit the Windows versions of our drivers for Windows Hardware Quality Labs (WHQL) certification, we do not normally hold back a product release or an important update while validation is pending. NOTE This assurance applies only to software that you have received directly from Thales or via a trusted third-party seller. |
| Windows | The MSI (Microsoft Installer) application does not complete installation, or is left in an unstable state. | This fault can occur if there are no free IRQs that can be assigned to the device. Make sure the device is assigned an IRQ. The IRQs assigned to devices are usually displayed when a system is powered up. |
| Windows | When operating multiple adapters under Windows 2000 or later, the adapters run slowly or even stall. Some commands may work correctly on one adapter, but not the other. | This problem may be resolved by resetting the configuration data in the host system BIOS. |
| Unix/Linux | Packages to install or uninstall are not visible while using the Unix Installation Utility. | If no packages are shown to install or uninstall, close the utility, check that you are logged on as root, and ensure your current directory is on the DVD or directory before running the utility again. |
| Unix/Linux | The screen is confused or does not display correctly while using the Unix Installation Utility. |
This utility relies on the TERM environment parameter when creating colors and measuring screen size, so make sure this is set correctly. The most common values are xterm or vt100. For example, to set TERM to vt100: # TERM=vt100# export TERM >If the screen is confused, run the utility in “plain” mode as follows: # ./safeNet-install.sh -p >If the size of the terminal is not correctly set by termcap (for example: the headings disappear off the top of the screen), override the screen size with the -s option: # ./safeNet-install.sh -s 24x80 >If using an X system terminal window, do not resize the window while running the utility, as it cannot sense the change. |
| Unix/Linux | The backspace key does not operate correctly while using the Unix Installation Utility. |
On some terminals, the backspace key does not operate correctly. If, after typing a number and then backspace, the terminal returns “2^H” instead of an actual backspace: >Type the current KILL character (normally ^U) and then enter the desired number (you will need to do this each time a backspace is required) >Exit the utility (perhaps with ^C) and use the stty(1) command to correct the erase character before restarting the utility: # stty erase ^H where ^H is the character created by pressing the backspace key. This will fix the problem semi-permanently, for the current session in that terminal. |
