31.0 Lib0 Messages

The following includes messages from LIB0.NLM.

Lib0-X-001: It was not possible to register NLMs with Network management. There may be no NetWare management agent present.

Source: LIB0.NLM
Explanation: The Network Management agent (an NLM™ program running on the server) responsible for gathering statistics on a software module was not available or did not respond to the lib0 program's attempt to register. The lib0 program will continue to perform correctly, although Network Management will be unable to gather statistics on it.
Action: Use a different version of this NLM program. To get a different version, contact the vendor of this NLM program a Novell support provider.

Lib0-X-002: Lib0 failed to create call gates in support of user address spaces under NetWare with memory protection. Lib0 will still support other NLMs, but no NLMs can be loaded in protected domain until Lib0 is unloaded and reloaded without this message appearing. Contact your Novell software distributor.

Source: LIB0.NLM
Explanation: This message appears if the operating system is NetWare® 4.11, which does not support memory protection. It can also appear if certain functions that normally run in protected memory could not be registered or if system memory is low.
Action: Load NLM programs in the kernel address space, instead of in a protected address space. Check server memory and add more memory if necessary. If the operating system is NetWare 5 or later and server memory is adequate, contact a Novell Authorized Reseller or Novell Technical Support.

Lib0-X-003: RegisterTrackedResource() for BSD Sockets failed, rc=number. An internal system error has occurred. There may not be enough server memory, or server memory may be corrupted.

Source: LIB0.NLM
Explanation: A call to RegisterTrackedResource() failed. The LIB0.NLM program cannot load at this time due to memory constraints.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

Lib0-X-004: Unable to register console command (name).

Source: LIB0.NLM
Explanation: Lib0 could not register a console command with the server operating system, probably because memory is low. If memory is adequate, there might be a problem with the operating system.
Action: Check server memory. If necessary, increase the memory available to the server. (See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.) If memory is adequate, contact a Novell Authorized Reseller or Novell Technical Support.

Lib0-X-081: Lib0 failed to allocate the internal memory resource tag for the Berkeley Sockets Mutexes. There may not be enough server memory, or server memory may be corrupted.

Source: LIB0.NLM
Explanation: System resources are so low that the library could not provide the needed memory resource tag.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

Lib0-X-082: Lib0 failed to initialize the Berkeley Socket mutexes. An internal system error has occurred.

Source: LIB0.NLM
Explanation: System resources are so low that the library could not provide the needed memory.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.