60.0 Runtime Libraries Messages

The following includes messages from CLIB.NLM, FPSM.NLM, NIT.NLM, NLMLIB.NLM, LIB0.NLM, REQUESTR.NLM, and THREADS.NLM.

Novell Runtime Libraries-X-001: Name (number) cannot be loaded until FPSM.NLM(number) is updated!

Source: Novell Runtime Libraries
Possible Cause: The Runtime Libraries and fpsm.nlm have different internal version numbers.
Action: Make sure that the runtime libraries (CLIB.NLM, FPSM.NLM, NIT.NLM, NLMLIB.NLM, LIB0.NLM, REQUESTR.NLM, and THREADS.NLM) are all the same version. These NLM programs are usually distributed as a set. To find a set of these NLM programs, refer to an authorized distribution source, such as.

Novell Runtime Libraries-X-002: Name (number) cannot be loaded until Lib0.NLM(number) is updated!

Source: Novell Runtime Libraries
Possible Cause: The Runtime Libraries and lib0.nlm have different internal version numbers.
Action: Make sure that the runtime libraries (CLIB.NLM, FPSM.NLM, NIT.NLM, NLMLIB.NLM, LIB0.NLM, REQUESTR.NLM, and THREADS.NLM) are all the same version. These NLM programs are usually distributed as a set. To find a set of these NLM programs, refer to an authorized distribution source, such as.

Novell Runtime Libraries-X-003: Name (number) cannot be loaded until Threads.NLM(number) is updated!

Source: Novell Runtime Libraries
Possible Cause: The Runtime Libraries and threads.nlm have different internal version numbers.
Action: Make sure that the runtime libraries (CLIB.NLM, FPSM.NLM, NIT.NLM, NLMLIB.NLM, LIB0.NLM, REQUESTR.NLM, and THREADS.NLM) are all the same version. These NLM programs are usually distributed as a set. To find a set of these NLM programs, refer to an authorized distribution source, such as.

Novell Runtime Libraries-X-004: Name (number) cannot be loaded until Requestr.NLM(number) is updated!

Source: Novell Runtime Libraries
Possible Cause: The Runtime Libraries and requestr.nlm have different internal version numbers.
Action: Make sure that the runtime libraries (CLIB.NLM, FPSM.NLM, NIT.NLM, NLMLIB.NLM, LIB0.NLM, REQUESTR.NLM, and THREADS.NLM) are all the same version. These NLM programs are usually distributed as a set. To find a set of these NLM programs, refer to an authorized distribution source, such as.

Novell Runtime Libraries-X-005: Name (number) cannot be loaded until NLMLib.NLM(number) is updated!

Source: Novell Runtime Libraries
Possible Cause: The Runtime Libraries and nlmlib.nlm have different internal version numbers.
Action: Make sure that the runtime libraries (CLIB.NLM, FPSM.NLM, NIT.NLM, NLMLIB.NLM, LIB0.NLM, REQUESTR.NLM, and THREADS.NLM) are all the same version. These NLM programs are usually distributed as a set. To find a set of these NLM programs, refer to an authorized distribution source, such as http://support.novell.com.

Novell Runtime Libraries-X-006: Name (number) cannot be loaded until NIT.NLM(number) is updated!

Source: Novell Runtime Libraries
Possible Cause: The Runtime Libraries and nit.nlm have different internal version numbers.
Action: Make sure that the runtime libraries (CLIB.NLM, FPSM.NLM, NIT.NLM, NLMLIB.NLM, LIB0.NLM, REQUESTR.NLM, and THREADS.NLM) are all the same version. These NLM programs are usually distributed as a set. To find a set of these NLM programs, refer to an authorized distribution source, such as http://support.novell.com.

Novell Runtime Libraries-X-007: Name (number) cannot be loaded until Clib.NLM(number) is updated!

Source: Novell Runtime Libraries
Possible Cause: The Runtime Libraries and clib.nlm have different internal version numbers.
Action: Make sure that the runtime libraries (CLIB.NLM, FPSM.NLM, NIT.NLM, NLMLIB.NLM, LIB0.NLM, REQUESTR.NLM, and THREADS.NLM) are all the same version. These NLM programs are usually distributed as a set. To find a set of these NLM programs, refer to an authorized distribution source, such as http://support.novell.com.

Novell Runtime Libraries-X-010: Name failed to allocate an internal resource tag: (name) There may not be enough server memory or server memory may be corrupted.

Source: Novell Runtime Libraries
Possible Cause: The library was unable to allocate memory for the resource.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

Novell Runtime Libraries-X-011: Name failed to allocate an internal resource tag: (name). Some functionality may not be available. This may be insignificant.

Source: Novell Runtime Libraries
Possible Cause: The library was unable to allocate memory for the resource.
Action: If necessary, increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

Novell Runtime Libraries-X-012: Name failed to allocate an internal mutex or semaphore: (name). There may not be enough server memory or server memory may be corrupted.

Source: Novell Runtime Libraries
Possible Cause: The library was unable to allocate memory for the resource.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

Novell Runtime Libraries-X-013: Name failed to allocate an internal mutex or semaphore: (name). Some functionality may not be available. This may be insignificant.

Source: Novell Runtime Libraries
Possible Cause: The library was unable to allocate memory for the resource.
Action: If necessary, increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.