"); 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; } //-->

Issue 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.

Remember, a stand-alone installation is functionally the same as a server installation.

Diagnostic

When logged in with full rights to the server (such as Administrator), run "Semcount" on the server, and confirm that "NPLSecure Detected" is displayed. If the server cannot use NPLSecure, no clients will either.

Things to check upon failure:

· If startup fails, write down the error messages found in any message windows.

· Use the Services control panel on the server to make sure the NPLSecure service is installed, has been started and is set for automatic startup.

· Use the Event Viewer control panel (on the server) to check the Application Log for any error messages from NPLSecure.

· Use the DCOMCNFG command to check the access and launch permissions for NPLSecure and DCOM.

Example 1.A

Installed a new 5.10 RunTime over an existing older RunTime. This happened to be a stand-alone setup, but the same principles apply to network installations.

Installation ran from the CD-ROM without a problem. When installing security the error "Improper upgrade level, Error code 90" or "Invalid Checksum on Floppy" was received.

Solution

The old NIAKSER.DAT was still in the RunTime directory even though the old security was recalled. Rename (or delete) the old NIAKSER.DAT. Run Authorization Installation again.

Example 1.B

Customer had 5.10 installed and running on the server. The server drive crashed over a weekend. They replaced the hard drive and rebuilt the server. They re-installed the 5.10 RunTime from CD-ROM, and attempted to run the RunTime and pass security from the Gold Key diskette until they could get a reset to install security.

When they tried to run the RunTime they got NIAKSER.DAT missing or damaged. They didn't get prompted for the Gold Key.

Solution

In Release 5.10 the NIAKSER.DAT file is copied from the Gold Key diskette by the security installation program. Even though there are no installs left on the Gold Key floppy, the installation must be run and allowed to fail. The installation program will make the necessary modifications and copy NIAKSER.DAT into the RunTime directory. Then the Gold Key diskette will be requested to pass security.