Troubleshooting

When installing SafeNet ProtectToolkit-C with an encryption adapter card such as the ProtectServer, the most common problems encountered are due to the access provider software being loaded incorrectly.

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, however, that this assurance applies only to software that you have received directly from SafeNet or via a trusted third-party seller.

If you encounter any difficulties:

>Check that you have followed all the installation instructions in this Guide and any associated manuals for the hardware and access provider software

>Follow any troubleshooting guidance given in the hardware and access provider manuals

Should you encounter any difficulties with the gctadmin and kmu utilities, the Java runtime might not have been installed prior to SafeNet ProtectToolkit-C. Uninstall both packages and reinstall them in the correct order.

If the issue is still not resolved please see Support Contacts to contact SafeNet Technical Support.