User Guide

SERVER Messages 537
System Messages
103-000150-001
August 29, 2001
Novell Confidential
Manual 99a38 July 17, 2001
SERVER-X-202: Detected user thread hogging the CPU.
Source: SERVER.EXE
Explanation: A thread running in a protected address space has not relinquished the CPU,
causing the address space to fault.
Action: How the server responds to the fault depends on whether the Memory
Protection Fault Cleanup parameter is set to On or Off and whether the address
space is restartable. See Memory Parameters and Managing Server Memory
in the Server Operating System Administration Guide. Treat the problem as an
abend: review the abend.log file in sys:\system; break into the debugger to
find more information (press Shift + Shift + Alt + Esc); if necessary, perform
a core dump. For more information, see Resolving Abends in the Server
Operating System Administration Guide.
SERVER-X-286: Invalid resource tag passed to api_name.
Source: SERVER.EXE
Explanation: There could be a bug in the NLM, or the NLM might be corrupted.
Action: Contact the NLM vendor.
SERVER-X-312: Invalid resource tag passed to api_name.
Source: SERVER.EXE
Explanation: There could be a bug in the NLM, or the NLM might be corrupted.
Action: Contact the NLM vendor.
SERVER-X-276: Invalid screen ID passed to screen manager. Module: name. Code
offset in module: offset.
Source: SERVER.EXE
Explanation: See “SERVER-X-6: Invalid screen ID passed to screen manager. Module:
name. Code offset in module: offset.” on page 535.
SERVER-X-384: This module is using one outdated API call. You should upgrade to a
newer module when it becomes available.
Source: SERVER.EXE
Possible Cause: The operating system displays this message whenever an NLM is loaded that
is using old API calls. NetWare renamed some of the APIs as additional