SERVER-X-1345: FreeObject detected corrupt preceeding redzone for object number.
Source:
Explanation:
Action:
SERVER-X-1346: FreeObject detected object number is already free.
Source:
Explanation:
Action:
SERVER-X-1353: FreeObject detected corrupt trailing redzone for object number,
object size size.
Source:
Explanation:
Action:
SERVER-X-1375: Invalid message file.
Source:
Explanation:
Possible Cause:
Action:
SERVER-X-1400: Error unloading killed loadable module.
Source:
Explanation:
Possible Cause:
Action:
SERVER.EXE
Memory might be corrupted.
Replace memory or contact your support provider.
SERVER.EXE
There is probably an internal programming error in the NLM.
Contact the NLM vendor.
SERVER.EXE
Memory might be corrupted.
Replace memory or contact your support provider.
SERVER.EXE
The message file for an NLM on the console was invalid.
The server might be using an outdated version of the file.
Determine why the file is invalid and replace it with a valid file.
SERVER.EXE
An error occurred while an NLM was being unloaded. The NLM is still
loaded. A preceding message should explain why the module could not be
unloaded.
The error might have occurred because another module is still referencing
public symbols or resources exported by this module. An NLM can be
unloaded only when all other NLM programs that use its global variables are
unloaded.
Check the preceding message to see why the NLM was not unloaded. If
necessary, unload the NLM that is using this module's public symbols or
resources; then unload this NLM.
SERVER Messages 555
Need help?
Do you have a question about the NETWARE 6-DOCUMENTATION and is the answer not in the manual?
Questions and answers