E-Lock Client Software Installation and Troubleshooting Guide
E-Lock Client Software Installation and Troubleshooting Guide
E-Lock Client Software Installation and Troubleshooting Guide
3. To download ElockClientNSE.exe login to Member Portal --Trading members (go to Inspection >> Internal
Audit>> Help Documents) and Auditors(go to INSPECTION-INTERNAL AUDIT >> Internal Audit>>Help
Documents).
4. The browser versions supported for Browser Compatible Digital Signature solution are Internet Explorer
11, Edge, Google Chrome v.50 and above, Mozilla Firefox v.47 and above
5. Kindly disable antivirus during installation of E-Lock components
6. Browser Compatible version of ElockClientNSE.exe is supported on Windows 7 and above operating systems
9. To use Digital Signature on Mozilla Firefox, it should be installed before installing E-Lock.
To enable Firefox browser for signing then after the installation of ElockClientNSE.exe is complete, you need
to click on “Enable Firefox” menu from Start “E-Lock SuperSigner Plus Client” once. In every user’s context
on that machine, it just needs to be done once.
Reported Issues and their Resolutions
Almost all the issues that customer face are because of one or more of the following:
• Installation was done without full Admin privileges
• Anti-virus prevented proper execution of the installer
• The browser being used is not a compatible browser
• An older version of the E-Lock client software is being used
If the above problems are avoided and the steps mentioned in the earlier section are followed, you should not face
any issues in installing or using E-Lock client software for signing.
Troubleshooting steps
The following helps in troubleshooting if the E-Lock Client software has been installed but is giving errors during
signing.
Installation Troubleshooting
Problem faces during installation are:
• You get errors during installation (e.g., could not create Menu / shortcut, or Could not run the script)
• The “C:\Program Files\E-Lock\SuperSigner Plus Client” (for 32 bit machines) or “C:\Program Files
(x86)\ELock\SuperSigner Plus Client” (for 64 bit machines) path does not exist
• The path exists but does not have SignApp.exe, Validate.exe or other files
• The files exist but SignApp.exe does not start (neither is started automatically, nor does it start on double
clicking on the file here)
• Files like DeskSign.dll, DeskLicense.dll are not present in “c:\windows\system32” (for 32 bit machines) or
“c:\windows\SysWow64” (for 64 bit machines) path
• The files exist but doing “regsvr32 desksign.dll” from an Administrator Command Prompt gives some error
In all such cases, the resolution is to:
• Login as Administrator
• Disable Anti-virus
• Uninstall E-Lock Client (either from Control Panel Programs and Features, or from “Completely Remove E-
Lock” from Start “E-Lock SuperSigner Plus Client”)
Make sure you do not get any error messages during installation. Also make sure that you wait till you get
“Installation Complete” message. If you do get some error message apart from message about AddFirefoxcert.vbs,
even though the user doing the installation has full Administrator rights, Anti-virus is disabled, Browser and all the
other Application. If u still have the problem with signing kindly report it to inspection_it@nse.co.in.
General troubleshooting
1. If you get a message like “Could not connect to E-Lock SignApp…”? go through the following steps:
o Start Task Manager. Is SignApp.exe running in background processes?
If yes, most likely cause is that you are not using a supported browser. Make sure you use a
supported browser
If you are using a supported browser and you are still getting this error, go to Connection
Troubleshooting
o If SignApp.exe is not running in the background, try “Restart SignApp’ menu from “Start All
Programs E-Lock SuperSigner Plus Client”. Check if SignApp is seen in Task Manager.
o If SignApp is
still not running, or if the “Restart SignApp” gives some error, most likely there is some problem with
your installation. See installation Troubleshooting.
o If SignApp is seen in the task manager, try signing again. If it still gives the error like “Could not
connect to E-Lock SignApp…” and you are using a supported browser, go to Connection
Troubleshooting
2. Is certificate selection dialog coming and is it showing the DSC, but you get some error while signing? In such
cases, the error is usually of the form “Microsoft Crypto API internal error…” or “Cannot access cryptographic
provider for private key…” If yes, your E-Lock software installation is fine but cause is some issue with token
or token driver or the key / certificate on the token. Check with token vendor.
3. If not, are you getting a message like “Please ensure that you have a non-expired certificate…”?
If yes, your E-Lock software installation is fine but cause is that either your token is not connected or token
driver is not installed or the token does not have a valid certificate.
Connection Troubleshooting
Usual causes for “Could not connect to E-Lock SignApp…” kind of errors despite the SignApp running in the
background (Task Manger Process) are:
• You are using Chrome 56 onward and your Client installation is old (older than 4.7.5.7), or
• You are using latest Internet Explorer i.e. IE-11 but your Client installation is old (older than 4.7.5.7), or
• You are using Internet Explorer version older than 11, or
• You are using Internet Explorer 11 or later but the “connect2nse.com” is added in compatibility mode.
• You are using Firefox 47 or later, but have never clicked on “Enable Firefox” menu from Start “E-Lock
SuperSigner Plus Client”
If the above does not solve the “Could not connect to E-Lock SignApp…” problem, please contact to support at
“inspection_it@nse.co.in” with details.