Reinstalling the SafeNet Authentication Client
This guide is meant for users who are currently encountering issues with their installation of the SafeNet Authentication Client (SAC), users are advised to follow-through this guide prior to the reinstallation of the SafeNet Authentication Client.
Step 1: Close/Exit SafeNet Authentication Client
Click on the System Tray
Step 2:
Right-Click on the SafeNet Authentication Tool icon and click on 'Exit'
Step 3:
A pop-up will appear confirming that the SafeNet Authentication Client will be terminated, click on 'OK'.
-------------------------------------
Start the un-installation of the existing SafeNet Authentication Client (SAC)
Step 1: Click on the 'Add or remove programs' from within the Start Menu
Step 2: Locate the SafeNet Application Client from within the 'Add/Remove Programs' functionality
Step 3: Close the SafeNet Authentication Client, if not already closed.
Step 4a: Click on 'No' when asked to save the existing configuration settings
Step 4b: Take note of the following prompt as a restart is required
Step 5a: *Important* Upon completion of the uninstallation of the existing SafeNet Authentication Client, do restart your computer.
Failure to do so will result in a corrupted installation of the SafeNet Authentication Client.
Step 5b: Following the restart, navigate to the following path: 'C:/Windows/System32' and delete the files, 'eToken.dll', 'eTPKCS11.dll' and 'dkck201.dll', where applicable.
Do note that there is a possibility that not all files are present for deletion, in this case - do proceed with the deletion of any residual files.
eToken.dll
eTPKCS11.dll
dkck201.dll
*NOTE*: This step is only applicable to users running on a 64-bit variant of Windows, if you are running a 32-bit variant of Windows - proceed to skip to Step 6 instead.
Step 5c: navigate to the following path: 'C:/Windows/SysWOW64' and delete the files, 'eToken.dll', 'eTPKCS11.dll' and 'dkck201.dll', where applicable.
Do note that there is a possibility that not all files are present for deletion, in this case - do proceed with the deletion of any residual files.
eToken.dll
eTPKCS11.dll
dkck201.dll
Step 6: Perform a reinstallation of the latest available version of the SafeNet Authentication Client available on the Netrust Download Page.
Related Articles
Configuring nSign Desktop to use Proxy and configure NTLM Authentication
[Guide] Configuring nSign Desktop to use Proxy and configure NTLM Authentication (if required) This guide is meant for the following user groups, a) Users who utilizes work-issued laptop/Network which does not allow internet access and will require a ...nSign Desktop Troubleshooting Ticket Submission Guide
Enabling Debug Mode Logging Upon encountering an error, this step is to be done to log more details encountered by the end-user to aid with the troubleshooting process. 1. Go to the Path: C:\Program Files\Netrust\nSign\config\log4j2.xml (or the ...nSign Desktop troubleshoot with Windows Security prompt
Certificate Entry Check 1. Open Microsoft Edge or IE, navigate to Settings and search for Manage certificates 2. Click on Manage certificates, a list of certificates should appear. Check that when the USB token is plugged in, the certificates issued ...[nSign Desktop] Add Service Provider (ELS2.0) Troubleshooting Guide
Problem: "Error adding service provider" or "Add service provider server failed" The connection from the client to the server endpoint is blocked. Troubleshooting steps 1. Check that the service provider is whitelist in your network. Review your ...[nSign Desktop] Add Service Provider (CSMS) Troubleshooting Guide
Problem: "Error adding service provider" or "Add service provider server failed" The connection from the client to the server endpoint is blocked. Troubleshooting steps 1. Check that the service provider is whitelist in your network. Review your ...