"); gbWndPopupLinks.document.close(); if (!s_bNS3 && gbWndTemp != null) { gbWndTemp.close(); }else { gbWndPopupLinks.focus(); } return true; } return false; } onload = BSSCOnLoad; document.onclick = BSSCOnClick; onunload = BSSCOnUnload; onerror = BSSCOnError; function reDo() { if (innerWidth != origWidth || innerHeight != origHeight) location.reload(); } if ((parseInt(navigator.appVersion) >= 4) && (navigator.appName == "Netscape")) { origWidth = innerWidth; origHeight = innerHeight; onresize = reDo; } //-->

Common Problems

In order for the NPLSecure security method to work, the following criteria must be met. Follow the links for a discussion of each requirement, problems that might be encountered, diagnostic methods, and common (and not so common) examples.

1) Setup: The RunTime setup must have been run on the server and on each workstation, and the NPLSecure installation method must have been chosen each time. Further, "Authorization Installation" or "Upgrade License" must have been successfully run on the server.

2) License File: The RunTime must be able to find and read the license file.

3) Name Resolution: The workstation must be able to resolve the fully qualified server name, which is found in the license file, to an IP address.

4) Communication: The workstation must be able to communicate with the server.

5) User Rights: The workstation user must have enough rights on the server to be able to communicate with the NPLSecure service.

See also: Error Codes

Operational Notes

- The new install creates a subdirectory 'Enable' containing the file called 'ENABLED'. To use RTIWIN32 you must copy the ENABLED file to the installation directory.

- All terminals show the same #TERM: it may be because you have not set NIAKWA_RUNTIME, but have choosen to copy the license file instead - see the section titled Setting NIAKWA_RUNTIME vs. Copying the License File for more information.

- After installing / recalling on a completely clean system the following bits and pieces are left behind:

  ATL.DLL may remain installed in WINDOWS\SYSTEM[32] directory.

- If you accidentally uninstall NPL without recalling authorization, you can reinstall NPL and then recall the authorization.

- If you run setup more than once without uninstalling, this will work (you can still uninstall) but it may inhibit removal of files for some installed DLL's and EXE's.

- If you copy the license file (or other files) to the installation directory after installing, the uninstall procedure does not delete these files, or remove the directories they are in.