NW 6.5 SP8: System Messages
This guide is a collection of the messages generated by some of the component modules contained in NetWare®. Each message documented might contain an explanation and one or more possible causes and actions for the message.
This document contains the following sections:
-
Section 1.0, Understanding System Messages
-
Section 2.0, Abend: SERVER Messages
-
Section 3.0, Authentication Messages for ConsoleOne
-
Section 4.0, BOOTPART Messages
-
Section 5.0, CAPTURE Messages
-
Section 6.0, CLIB Messages
-
Section 7.0, CNE2 Messages
-
Section 8.0, CNE2000 Messages
-
Section 9.0, CNE2_32 Messages
-
Section 10.0, CNE3200 Messages
-
Section 11.0, CNEAMD Messages
-
Section 12.0, CNTR2000 Messages
-
Section 13.0, CX Messages
-
Section 14.0, DSDIAGNOSTICS Messages
-
Section 15.0, DSI Messages
-
Section 16.0, DSKSHARE Messages
-
Section 17.0, DSREPAIR Messages
-
Section 18.0, EDIT Messages
-
Section 19.0, FILESYS - File System Messages
-
Section 20.0, FLAG Messages
-
Section 21.0, FPSM Messages
-
Section 22.0, FTP Server Messages
-
Section 23.0, HDETECT Messages
-
Section 24.0, ICMD Messages
-
Section 25.0, IDEATA.HAM Messages
-
Section 26.0, IDECD.CDM Messages
-
Section 27.0, IDEHD.CDM Messages
-
Section 28.0, IPXS Messages
-
Section 29.0, LANSUP-DOS Messages
-
Section 30.0, LFS - Logical File System Messages
-
Section 31.0, Lib0 Messages
-
Section 32.0, LOCALSEL Messages
-
Section 33.0, LOGIN Messages
-
Section 34.0, LOGOUT Messages
-
Section 35.0, MAP Messages
-
Section 36.0, INETCFG Messages
-
Section 37.0, MONITOR Messages
-
Section 38.0, NDPSM Messages
-
Section 39.0, NE1000-NW Messages
-
Section 40.0, NE2-NW Messages
-
Section 41.0, NE2000-NW Messages
-
Section 42.0, NE3200-NW Messages
-
Section 43.0, NIT Messages
-
Section 44.0, NLMLIB Messages
-
Section 45.0, NLSLSP Messages
-
Section 46.0, Novell Native File Access for UNIX Messages
-
Section 47.0, NSS Messages
-
Section 48.0, NWCONFIG Messages
-
Section 49.0, NWPA Messages
-
Section 50.0, NWSNUT Messages
-
Section 51.0, NWTAPE Messages
-
Section 52.0, Novell Certificate Server Messages
-
Section 53.0, Policy Manager Messages
-
Section 54.0, PSERVER Messages
-
Section 55.0, RConsoleJ Messages
-
Section 56.0, RCONAG6 Messages
-
Section 57.0, RCONPRXY Messages
-
Section 58.0, REQUESTR Messages
-
Section 59.0, RIGHTS Messages
-
Section 60.0, Runtime Libraries Messages
-
Section 61.0, SBCON Messages
-
Section 62.0, SERVER Messages
-
Section 63.0, SMDR Messages
-
Section 64.0, SMSDI Messages
-
Section 65.0, SPXS Messages
-
Section 66.0, STREAMS Messages
-
Section 67.0, TEXTUTIL-utility_name
-
Section 68.0, THREADS Messages
-
Section 69.0, TIMESYNC Messages
-
Section 70.0, TLI Messages
-
Section 71.0, TRXNET-DOS Messages
-
Section 72.0, TSA600 Messages
-
Section 73.0, TSANDS Messages
-
Section 74.0, TUI Messages
-
Section 75.0, VREPAIR Messages
-
Section 76.0, Shared Messages for LAN Drivers
-
Section 77.0, Common Workstation Utilities Error Messages
-
Section A.0, Troubleshooting the Workstation
IMPORTANT:OES 2 NetWare and NetWare 6.5 SP 7 share the same code base and are the same in every way. Installing the OES 2 NetWare product or associated support pack is the same as installing the simultaneously released NetWare 6.5 product or associated support pack.
Audience
The majority of this guide is intended for network administrators. A few sections include information for end users.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation included with this product. Please use the User Comments feature at the bottom of each page of the online documentation, or go to www.novell.com/documentation/feedback.html and enter your comments there.
Documentation Updates
For the most recent version of OES 2: System Messages for NetWare, see the Open Enterprise Server 2 Product Documentation Web site.
Documentation Conventions
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items within a cross-reference path.
A trademark symbol (®, ™, etc.) denotes a Novell® trademark. An asterisk (*) denotes a third-party trademark.
When a single path name can be written with a backslash for some platforms or a forward slash for other platforms, the path name is presented with a backslash. Users of platforms that require a forward slash, such as UNIX* and Linux*, should use forward slashes as required by your software.