52.0 Novell Certificate Server Messages

The following includes messages from PKI.NLM.

NOVELL CERTIFICATE SERVER-X-1: PKI.NLM could not initialize cryptographic services, or cryptographic services are not available

Source: PKI.NLM
Possible Cause: The server does not have a valid server base license. A Master License Agreement (MLA) is not sufficient to enable NICI.
Action: Install a valid license, and ignore any errors that indicate that you already have a server license installed.
Possible Cause: The U.S./Canada or Worldwide cryptographic engine is not installed and the Null cryptographic engine is loaded.
Action: Install the U.S./Canada or Worldwide version of NICI 1.3.1 or later.
Possible Cause: Some errors or problems occurred in NICI or in the Novell Controlled Cryptography Services (CCS) during the boot process.
Action: Look in the console log for alert messages that were issued by NICI or CCS during the boot process, and resolve them. In order for PKI.NLM to load, these errors must be resolved.

NOVELL CERTIFICATE SERVER-X-2: PKI.NLM could not initialize double-byte tables.

Source: PKI.NLM
Possible Cause: The double-byte tables or low-level interface functions failed to initialize.
Action: Ensure that the NetWare® installation was correct and complete.

NOVELL CERTIFICATE SERVER-X-3: PKI.NLM could not get country and code page identifiers.

Source: PKI.NLM
Possible Cause: The Unicode* tables that the server was configured to use (when the server was installed) have become corrupted or have been deleted.
Possible Cause: Read errors occurred on the Unicode file.
Possible Cause: The Unicode file specified by the code page does not exist.
Possible Cause: The internal contents of the Unicode translation file have become corrupted or are invalid.
Action: Ensure that the files in the SYS:LOGIN\NLS directory are those from the NetWare® installation and that they are not corrupted. The file that could not be read from this directory is<code page ID>_UNI.001 or UNI_<code page ID>.001, where <code page ID> is the three- or four-digit decimal number corresponding to the server’s code page (such as, 437 for the U.S., or 850 for most of Europe). If these files are missing or corrupted, you might need to restore this directory.
Possible Cause: The server has insufficient memory.
Possible Cause: Too many files are opened, so the Unicode file cannot be opened.
Action: Do one or more of the following until the problem is resolved:

  • Add memory to the server.

  • Unload any unnecessary NLM™ programs.

  • If possible, reconfigure the server’s SET parameters to provide more memory to the server, then reload PKI.NLM.

Possible Cause: PKI.NLM does not have rights to read the Unicode file.
Action: Ensure that the NetWare installation was correct and complete and that the file access rights for the SYS:LOGIN\NLS directory are set to Public Read.

NOVELL CERTIFICATE SERVER-X-4: PKI.NLM could not initialize Unicode translation tables.

Source: PKI.NLM
Possible Cause: The Unicode* tables that the server was configured to use (when the server was installed) have become corrupted or have been deleted.
Possible Cause: Read errors occurred on the Unicode file.
Possible Cause: The Unicode file specified by the code page does not exist.
Possible Cause: The internal contents of the Unicode translation file have become corrupted or are invalid.
Action: Ensure that the files in the SYS:LOGIN\NLS directory are those from the NetWare® installation and that they are not corrupted. The file that could not be read from this directory is<code page ID>_UNI.001 or UNI_<code page ID>.001, where <code page ID> is the three- or four-digit decimal number corresponding to the server’s code page (such as, 437 for the U.S., or 850 for most of Europe). If these files are missing or corrupted, you might need to restore this directory.
Possible Cause: The server has insufficient memory.
Possible Cause: Too many files are opened, so the Unicode file cannot be opened.
Action: Do one or more of the following until the problem is resolved:

  • Add memory to the server.

  • Unload any unnecessary NLM™ programs.

  • If possible, reconfigure the server’s SET parameters to provide more memory to the server, then reload PKI.NLM.

Possible Cause: PKI.NLM does not have rights to read the Unicode file.
Action: Ensure that the NetWare installation was correct and complete and that the file access rights for the SYS:LOGIN\NLS directory are set to Public Read.

NOVELL CERTIFICATE SERVER-X-5: PKI.NLM could not initialize NCP handling.

Source: PKI.NLM
Possible Cause: A third-party NLM™ program is using the NetWare® Core Protocol™ (NCP™) verb number that has been assigned to PKI.NLM.
Action: Unload any unnecessary, untested, or unapproved NLM programs, then reload PKI.NLM.
Possible Cause: The NetWare operating system does not have enough resources (most likely memory) to run PKI.NLM.
Action: Do one or more of the following until the problem is resolved:

  • Add memory to the server.

  • Unload any unnecessary NLM™ programs.

  • If possible, reconfigure the server’s SET parameters to provide more memory to the server, then reload PKI.NLM.

NOVELL CERTIFICATE SERVER-X-6: PKI.NLM could not create an NDS context.

Source: PKI.NLM
Possible Cause: The NetWare® operating system does not have enough resources (most likely memory) to create an Novell eDirctory® context.
Action: Do one or more of the following until the problem is resolved:

  • Add memory to the server.

  • Unload any unnecessary NLM™ programs.

  • If possible, reconfigure the server’s SET parameters to provide more memory to the server, then reload PKI.NLM.

Possible Cause: Too many eDirectory contexts have already been opened by the server.
Action: Unload any unnecessary NLM programs, or add more memory to the server.
Possible Cause: Some eDirectory errors or problems occurred during the boot process.
Action: Look in the console log for alert messages that were issued by eDirectory during the boot process, and resolve these errors. In order for PKI.NLM to remain loaded, these errors must be resolved.

NOVELL CERTIFICATE SERVER-X-7: PKI.NLM could not set the NDS context.

Source: PKI.NLM
Possible Cause: An old version of PKI.NLM is being used.
Action: Upgrade to the latest version of Novell® Certificate Server.

NOVELL CERTIFICATE SERVER-X-8: PKI.NLM could not log in.

Source: PKI.NLM
Possible Cause: An old version of PKI.NLM is being used.
Action: Upgrade to the latest version of Novell® Certificate Server.

NOVELL CERTIFICATE SERVER-X-9: PKI.NLM is unloading because of errors during initialization.

Source: PKI.NLM
Possible Cause: Any of the Novell® Certificate Server messages numbered 1 through 8 were issued.
Action: Resolve the specific problem indicated by the preceding Novell Certificate Server error message, then reload PKI.NLM. If it is necessary to call Novell Technical Support, please be ready to report the entire text of the preceding error message, including any numbers appearing after the text of the PKI error message.