"InitCrypkey Error -103: NETWORK: REPLY FROM NETWORK DRIVER IS BAD" or "InitCrypkey Error -102: NETWORK: NETWORK DRIVER APPEARS TO NOT BE SERVING THIS DIRECTORY" (KB546)

There are two procedures for fixing this problem. Try Procedure 1 first, and if the license still has the same problem, try Procedure 2.

Procedure 1:

1. Confirm that the Windows Crypkey License service is started. To confirm, click Start > Control Panel > Administrative Tools > Services. Verify the Crypkey License status is Started. Also verify that the startup type is Automatic. If not, right-click the name and then click Start. Double-click the name to enter the properties dialog and change the startup type to Automatic. Close the Service window.
2. Confirm the Crypkey NetworkX driver is started by running C:\Program Files\Common Files\Microsoft Shared\MSInfo\Msinfo32.exe. Expand System Summary > Software Environment > System Drivers in the category tree in the left pane, then locate NetworkX in the right pane. Confirm that the State is Running and the Status is OK. Close the System Information window.
   

   If you cannot find these software components, uninstall the Echelon Software product, reboot, and reinstall the product. Anti-virus and Internet security software can interfere with the proper installation of the software. Disable such software before you re-install the Echelon software product.

3. At this point, if you are still unable to run your LonMaker or LNS application because of a License Access error message and if the Checklic license utility still reports a -102 or -103 error, follow the steps in Procedure 2.

Procedure 2:

Make sure you perform every step of this procedure.

1. Check to see if you have the following two files in the C:\Windows\LNS Licenses folder: setupex.exe and cks.exe
2. The LNS Licenses folder is hidden; if you do not see it, open the Windows Explorer Tools menu, click Folder Options, and in the View tab, select Show Hidden Files and Folders and clear Hide Protected Operating System Files (Recommended). If you don't see these files, download LicenseFix.zip and extract them to the C:\Windows\LNS Licenses folder.
3. Open a Windows command prompt by clicking Start > Run and typing in cmd (or command for Windows 98).
4. Type the following command to change your working directory: cd "\Windows\LNS Licenses"
5. Type the following command: setupex /U
6. Reboot your computer.
7. Repeat steps 3 and 4, and then type the following command: setupex
8. Reboot your computer.
9. For the LonMaker tool, open a Windows command prompt and enter: checklic lonmaker.vsl 
10. For other LNS tools, open a Windows commnad prompt and enter: checklic nsseng.exe 
11. If you don't see any errors, then you should be able to start your LNS application. Exit now.
12. If you see the GetAuthorization Error -4/GetAuthorization Error -1 error, which is expected, try opening/creating network. If you still get -4/-1 error, use the license wizard to request replacement credits. See KB545 for more information on the -4/-1 error.
13. If you still see an InitCrypkey Error -102/-103 error, delete the following files under C:\Windows\LNS Licenses:

• For the LonMaker tool:

• LonMaker.rst
• LonMaker.ent
• LonMaker.key
• LonMaker.41s
• For an LNS tool or application other than the LonMaker tool:
• nsseng.rst
• nsseng.ent
• nsseng.key
• nsseng.41s

Please note the files listed in step 12 and 13 are hidden operating system files so Windows Explorer may not show all the files (even when you activate the appropriate options in your Folder Options to see hidden files).

14. Delete esnecil.ind in the C:\windows\system32 folder.

15. Reboot your computer.

16. Run the Checklic license utility again.

17. If you see the GetAuthorization Error -4/GetAuthorization Error -1 error, which is expected, try opening or creating a network. If you still get -4/-1 error, use the license wizard to request replacement credits. See KB545 for more information on the -4/-1 error.