home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
os2pt2.exe
/
REQH.MSG
(
.txt
)
< prev
next >
Wrap
OS/2 Message File
|
1996-08-27
|
62KB
|
843 lines
MKMSGF
reqh.msg
Cause: An error occurred during attempt to get shared memory.
DDAEMON.EXE attempted to access the daemon's shared memory, but
failed. At this point, the program has verified that the shared
memory exists, but is unable to access it. This may be an internal
program error.
Action: Try rebooting your system. If the problem persists,
call your Novell Authorized Reseller.
Cause: An error occurred during attempt to allocate a shared segment.
DDAEMON.EXE tried to create shared memory, but none is available. This
error usually occurs when the device drivers and applications currently
running on your system require more memory than your system has available.
Action: Try adding RAM, reducing your configuration options in the
CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing
optional device drivers from the CONFIG.SYS file, and freeing up some
hard disk space by deleting unnecessary programs. If you are using
multiple disk partitions, consider moving the OS/2 swapper file to a
larger partition. Disk compression utilities may also be available
that can help resolve this problem. After completing these actions,
shut down OS/2; then reboot the system. If the problem persists, contact
your Novell Authorized Reseller.
Cause: The daemon cannot access the Link Support Layer.
Error: <code>. DDAEMON.EXE cannot find the Link Support device driver LSL.SYS.
Action: Make sure that the device driver LSL.SYS has been properly entered
in the CONFIG.SYS file. If so, check the messages displayed by the LSL for
any errors or warnings, and correct the problems indicated. Try again.
If this error persists, call your Novell Authorized Reseller.
Cause: The DDAEMON is already loaded. DDAEMON.EXE tried to create shared
memory for the first time, but the memory already exists. Another daemon
is already running. The attempt to create shared memory is terminated.
Action: Make sure that you are not trying to run multiple copies of the
daemon. Typically the daemon is run from the CONFIG.SYS file at system
startup and does not need to be executed again.
Cause: The system does not have enough memory for socket tables.
OS/2 lacks sufficient system memory for IPX to allocate memory for
its socket tables.
Action: Try adding RAM, reducing your configuration options in the
CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing
optional device drivers from the CONFIG.SYS file, and freeing up some
hard disk space by deleting unnecessary programs. If you are using
multiple disk partitions, consider moving the OS/2 swapper file to a
larger partition. Disk compression utilities may also be available
that can help resolve this problem. After completing these actions,
shut down OS/2; then reboot the system. If the problem persists,
contact your Novell Authorized Reseller.
Cause: The LAN support module could not be installed. Either the
LSL.SYS driver failed to load, or the "DEVICE=" statement is missing
from the CONFIG.SYS file.
Action: Either correct the problem that kept the LSL.SYS driver from
loading (indicated in an error message preceding this one), or add the
"DEVICE=" statement to the CONFIG.SYS file.
Cause: The IPX MLID could not be installed. Either the Multiple Link
Interface Driver (MLID) specified in the CONFIG.SYS failed to load, or
the "DEVICE=" statement for an MLID is missing from the CONFIG.SYS file.
Action: Either correct the problem that kept the MLID from loading
(indicated in an error message preceding this one), or add the "DEVICE="
statement to the CONFIG.SYS file.
Cause: The configured LAN-A driver does not support IPX. The Multiple
Link Interface Driver (MLID) to which IPX.SYS attempted to bind does not
support IPX-based data transmissions.
Action: Bind IPX to an MLID that supports IPX-based data transmissions.
Cause: The IPX protocol handler cannot be registered. IPX cannot register
with the LSL.SYS driver because the LSL is servicing its maximum number of
protocol stacks.
Action: Remove the "DEVICE=" statements for any unnecessary protocol
stacks from the CONFIG.SYS file.
Cause: The IPX entry point cannot be initialized. The IPX and link support
layer (LSL) versions may not be compatible versions.
Action: Make sure that the IPX.SYS driver and LSL.SYS driver are compatible.
If they are not, obtain compatible drivers from your Novell Authorized
Reseller. If this is not the problem, contact your Novell Authorized Reseller
for customer assistance.
Cause: An internal error occurred. The IPX router socket cannot be opened.
IPX was unable to open the router socket due to an internal program error.
Action: Try again. If the problem persists, contact your Novell Authorized
Reseller.
Cause: An internal error occurred. A router selector cannot be allocated.
IPX was unable to allocate an OS/2 router selector due to an internal program
error.
Action: Try again. If the problem persists, contact your Novell Authorized
Reseller.
Cause: The system has insufficient memory to allocate a router.
OS/2 cannot access sufficient system memory for IPX routing purposes.
Action: Try adding RAM, reducing your configuration options in the
CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing
optional device drivers from the CONFIG.SYS file, and freeing up some
hard disk space by deleting unnecessary programs. If you are using
multiple disk partitions, consider moving the OS/2 swapper file to a
larger partition. Disk compression utilities may also be available
that can help resolve this problem. After completing these actions,
shut down OS/2; then reboot the system. If the problem persists,
contact your Novell Authorized Reseller.
Cause:
Router memory is exhausted. IPX did not have enough memory previously
allocated for routing purposes.
Action: Increase the size of the IPX router memory in the NET.CFG
"ROUTER MEM" statement.
Cause: An internal error prevented CGroup variable initialization.
An internal program error has occurred. IPX was unable to initialize
internal variables.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: An internal error prevented DosHlp variable initialization.
OS/2 internal variables were either incomplete or invalid.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: IPX cannot register with OS/2 for PDD-to-VDD communications.
This is an internal program error. IPX cannot register with OS/2 for
VIPX.SYS driver support.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: The IPX device driver is not running. Either IPX.SYS
encountered a fatal error during system initialization, or the
"DEVICE=(path)IPX.SYS" statement was missing from the CONFIG.SYS
file. If the problem is a fatal error, another message should
precede this one that identifies the specific error that occurred.
Action: Either resolve the fatal problem (indicated in a preceding
message), or add the "DEVICE=" statement to the CONFIG.SYS file;
then try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause:
The default protocol configuration option is not used
for IPX. IPX cannot be configured as a default protocol stack.
Action: Remove this option statement from the NET.CFG file.
Cause: The prescan protocol configuration option is not used for IPX.
IPX cannot be configured as a prescan protocol stack.
Action: Remove this option statement from the NET.CFG file.
Cause: The OS/2 version number cannot be found; OS/2 v2.0 is assumed.
IPX's query of OS/2 for the version number returned a value that did
not match the value it expected to receive.
Action: Make sure the OS/2 version installed on the machine is v2.0
or later.
Cause: An LSL error occurred. NET.CFG buffers are too big for ECB pool.
The configured buffer size for the Link Support component is too large.
Total available buffer space is around 60 KB, but the Link Support Layer
(LSL) is unable to allocate even one buffer of the requested size in its
buffer space. See "Link Support Layer" in Concepts for more information
about LSL.
Action: Reduce the Link Support component's buffer size in the NET.CFG
file. It is more important to have several smaller buffers available
than one large one. It is a waste of system memory to configure buffers
much larger than the communications media can support.
Cause: The Link Support module (LSL) could not install the AES timer.
The Link Support Layer (LSL) could not register its timer handler with
the operating system because the maximum number of handlers have already
been installed. This timer handler is a critical component of NetWare
Client for OS/2, and none of the Novell-supplied communication handlers
can be expected to work properly without it. See "Link Support Layer"
in Concepts for more information about LSL.
Action: Previously installed device drivers (those entered before LSL.SYS
in the CONFIG.SYS file) have used all available timer resources. Identify
those device drivers and either remove or reconfigure them. Since the
Requestor's communications handlers all use a common timer service in the
LSL, only one available timer handler is required for proper operation.
If you are unable to resolve this problem, contact your Novell Authorized
Reseller.
Cause: The Link Support module could not initialize its call gate. The
Link Support module could not register its entry point with the operating
system. This entry point is vital to most of NetWare Client for OS/2's
communications components, and its absence will cause them to fail. The
most likely cause of this error is a previously loaded device driver that
is using too many kernel resources.
Action: Try removing application device drivers installed before LSL.SYS
in the CONFIG.SYS file. It is highly unlikely that a device driver from
the OS/2 base system has caused this error. If the problem persists,
contact your Novell Authorized Reseller.
Cause: NetBIOS error occurred. Link Support module cannot be installed.
NetBIOS could not open or communicate with the Link Support LINKSUP_ device
driver. This can happen if the Link Support Layer (LSL) driver has not
been properly installed or if you are using the wrong version of the driver.
See "Link Support Layer" in Concepts for more information about LSL.
Action: Make sure that the device driver LSL.SYS has been properly entered
in the CONFIG.SYS file. If so, check the messages displayed by the LSL for
any errors or warnings, and correct the problems indicated. NetBIOS and
Link Support are usually installed together from a single installation
diskette. Try reinstalling them. If the problem persists, contact your
Novell Authorized Reseller.
Cause: NetBIOS error occurred. The IPX module is not installed.
NetBIOS could not open or communicate with the Link Support LINKSUP_
device driver. This can happen if the Link Support Layer (LSL)
driver has not been properly installed or if you are using the wrong
version of the driver. See "Link Support Layer" in Concepts for more
information about LSL.
Action: Make sure that the device driver LSL.SYS has been properly
entered in the CONFIG.SYS file. If so, check the messages displayed
by the LSL for any errors or warnings, and correct the problems indicated.
If the Link Support device driver is initializing properly, the problem is
with incompatible versions of the software. NetBIOS and Link Support are
usually installed together from a single installation diskette. Try
reinstalling them. If the problem persists, contact your Novell Authorized
Reseller.
Cause: The NetBIOS call gate cannot be initialized. This is an internal
program error.
Action: Try again. If the problem persists, contact your Novell Authorized
Reseller.
Cause: NETBIOS error occurred. The program cannot initialize local NCBs.
Insufficient memory is available for the NCBs requested. Usually this
error is caused by incorrect configuration information in the NET.CFG file.
However, the underlying problem could also be a lack of global system
resources in the OS/2 Global Descriptor Table.
Action: Reduce the number of commands in the NetBIOS section of the
CONFIG.SYS file. (The default number of commands is 12; the maximum
allowed is 25.) You also might be able to reduce the number of node
names (possible range is 0-126). Additional possibilities include
adding RAM, reducing your configuration options (for example, reducing
the size of DIRCACHE) or removing optional device drivers from the
CONFIG.SYS file, and freeing up some hard disk space by deleting
unnecessary programs. If you are using multiple disk partitions,
consider moving the OS/2 swapper file to a larger partition. Disk
compression utilities may also be available that can help resolve
this problem. After completing these actions, shut down OS/2 and
then reboot the system. If the problem persists, contact your Novell
Authorized Reseller.
Cause: NetBIOS emulator parameters are too large for the memory pool.
Insufficient memory is available for all of the control tables needed
by the NetBIOS emulator.
Action: The amount of table space available to the NetBIOS emulator
cannot be increased. The only way to solve this problem is to reduce
the number of NetBIOS resources you are requesting. You can do this
by modifying the NETBIOS parameters in the NET.CFG file. If the problem
persists, contact your Novell Authorized Reseller.
Cause: Incompatible versions of OS/2 and NetBIOS are running. You
are attempting to run NetBIOS V2.10 on some version of OS/2 earlier
than OS/2 v2.1.
Action: Either install OS/2 v2.1 to run with netBIOS v2.10, or install
a different version of NetWare NetBIOS to match your OS/2 version.
Cause: The SPX module is not installed. The NMPIPE.SYS driver could not
open or communicate with the SPX.SYS driver.
Action: Make sure that the SPX.SYS driver has been properly entered in
the CONFIG.SYS file. If so, check the messages displayed by the driver
for any errors or warning, and correct the problems indicated; then try
again. If the problem persists, contact your Novell Authorized Reseller.
Cause: The IPX module is not installed. NMPIPE.SYS could not open or
communicate with the IPX.SYS driver.
Action: Make sure that the IPX.SYS driver has been properly entered in
the CONFIG.SYS file. If so, check the messages displayed by the driver
for any errors or warnings, and correct the problems indicated; then try
again. If the problem persists, contact your Novell Authorized Reseller.
Cause: An incorrect OS/2 version is being used. Either the
DosGetVersion call failed (an internal program error), or the
OS/2 version currently running is not v2.0 or later.
Action: Make sure the client OS and NMPIPE.SYS driver are compatible
versions. If the problem persists, contact your Novell Authorized Reseller.
Cause: The driver cannot register the PDD for VDD-to-PDD communications.
NMPIPE.SYS could not register IPX as a PDD so that PDD to VDD communication
may take place.
Action: Make sure the IPX.SYS driver has been properly entered in the
CONFIG.SYS file. If so, check the messages displayed by the driver for
any errors or warnings, and correct the problems indicated. Also make
sure the OS/2 version is v2.0 or later; then try again. If the problem
persists, contact your Novell Authorized Reseller.
Cause: Invalid characters were specified in COMPUTERNAME. The
Names Pipes server name specified after NPDAEMON.EXE is invalid.
Action: Make sure the server name is not more than 15 characters
and is composed of letters, numbers, and these special characters:
!#$%&()-.@^_{}~
Cause: An error occurred during attempt to initialize NPCALLS.DLL.
The NPDaemon could not initialize NPCALLS.DLL.
Action: Make sure the NPCALLS.DLL file in the NetWare Client for
OS/2 directory is included in the LIBPATH statement of the CONFIG.SYS
file. If you are running Named Pipes, make sure the NMPIPE.SYS driver
and NPSERVER.SYS are correctly configured in the CONFIG.SYS file.
Cause: The named Pipes daemon could not be registered. Error: <code>.
The NPDaemon could not open or communicate with the NMPIPE.SYS driver.
Action: Make sure the NMPIPE.SYS driver has been properly entered in
the CONFIG.SYS file. If so, check the messages displayed by the driver
for any errors or warnings, and correct the problems. Try again. If
the problem persists, contact your Novell Authorized Reseller.
Cause: An error occurred during attempt to allocated shared memory.
The NPDaemon could not allocate shared memory.
Action: Try adding RAM, reducing your configuration options in
the CONFIG.SYS file (for example, reducing the size of DIRCACHE),
removing optional device drivers from the CONFIG.SYS file, and
freeing up some hard disk space by deleting unnecessary programs.
If you are using multiple disk partitions, consider moving the OS/2
swapper file to a larger partition. Disk compression utilities may
also be available that can help resolve this problem. After completing
these actions, shut down OS/2; then reboot the system. If the problem
persists, contact your Novell Authorized Reseller.
Cause: An error occurred during attempt to allocate the ECB pool.
The NPDaemon could not allocate memory for the ECB pool.
Action: Try adding RAM, reducing your configuration options in the
CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing
optional device drivers from the CONFIG.SYS file, and freeing up some
hard disk space by deleting unnecessary programs. If you are using
multiple disk partitions, consider moving the OS/2 swapper file to
a larger partition. Disk compression utilities may also be available
that can help resolve this problem. After completing these actions,
shut down OS/2; then reboot the system. If the problem persists,
contact your Novell Authorized Reseller.
Cause: An error occurred during attempt to create a system semaphore.
A DosCreateSem call failed. An internal program error may have occurred.
Action: Try again. If the error persists, contact your Novell Authorized
Reseller.
Cause: An error occurred during attempt to create a thread. A
beginthread call failed. An internal program error may have occurred.
Action: Try again. If the error persists, contact your Novell Authorized
Reseller.
Cause: A dynamic socket could not be opened. Error: <code>.
The NPDaemon failed to open a dynamic socket.
Action: Increase the socket count specified in the NET.CFG file;
then reboot the system and try again. If the problem persists,
contact your Novell Authorized Reseller.
Cause: A well-known socket could not be opened. Error: <code>.
The NPDaemon could not open Netware's registered Named Pipe socket;
the socket may already be in use.
Action: Increase the SPX socket count in the NET.CFG and shut
down OS/2; then reboot the system.
Cause: The NPDaemon cannot get the internet address. Error: <code>.
An IpxGetInternetworkAddress call failed.
Action: Make sure the IPX.SYS driver has been properly entered
in the CONFIG.SYS file. If so, check the messages displayed by
the driver for any errors or warnings, and correct the problems
indicated. Also make sure the IPXCALLS.DLL file is in the NetWare
Client for OS/2 directory; then try again. If the problem persists,
notify your Novell Authorized Reseller.
Cause: The NPDaemon cannot get the local target. Error: <code>.
An IpxGetLocalTarget call failed.
Action: Make sure the IPX.SYS driver has been properly entered
in the CONFIG.SYS file. If so, check the messages displayed by
the driver for any errors or warnings, and correct the problems
indicated. Also make sure the IPXCALLS.DLL file is in the NetWare
Client for OS/2 directory; then try again. If the problem persists,
contact your Novell Authorized Reseller.
Cause: The service advertising function failed. Error: <code>.
An IpxSend call to advertise this workstation as Named Pipe Server
failed.
Action: Make sure the IPX.SYS driver has been properly entered in
the CONFIG.SYS file. If so, check the messages displayed by the
driver for any errors or warnings, and correct the problems indicated.
Also make sure the IPXCALLS.DLL file is in the NetWare Client for
OS/2 directory; then try again. If the problem persists, contact your
Novell Authorized Reseller.
Cause: The broadcast socket cannot be opened. Error: <code>.
The broadcast socket cannot be opened. This is a registered socket
by which SAPs can be received. Possibly this socket has already been
opened.
Action: Increase the socket count in the NET.CFG file and shut down
OS/2 and then reboot the system. If the problem persists, contact
your Novell Authorized Reseller.
Cause: An error occurred during attempt to get code page information.
A call to DosGetCtryInfo failed. This may be an internal program error.
Action: Make sure the OS/2 is version 2.0 or later. If so, and the
problem persists, contact your Novell Authorized Reseller.
Cause: Memory cannot be allocated for turbo buffers. The NPDaemon
could not allocate memory for turbo buffers.
Action: Try adding RAM, reducing your configuration options in
the CONFIG.SYS file (for example, reducing the size of DIRCACHE),
removing optional device drivers from the CONFIG.SYS file, and
freeing up some hard disk space by deleting unnecessary programs.
If you are using multiple disk partitions, consider moving the OS/2
swapper file to a larger partition. Disk compression utilities may
also be available that can help resolve this problem. After completing
these actions, shut down OS/2; then reboot the system. If the problem
persists, contact your Novell Authorized Reseller.
Cause: A connection thread died abnormally. Error: <code>.
The connection controller thread died unexpectedly.
Action. Make sure that the SPX.SYS driver has been properly entered
in the CONFIG.SYS file. If so, check the messages displayed by the
driver for any errors or warnings, and correct the problems indicated.
Also make sure all of your Named Pipe drivers are within the same major
version (for example, v2.x); then try again. If the problem persists,
contact your Novell Authorized Reseller.
Cause: The specified computer name is already registered on the
internet. The Named Pipes server name specified in the CONFIG.SYS
file has already been used on the network.
Action: Use a different server name.
Cause: The receive buffer manager died abnormally. Error: <code>.
The receive buffer manager thread died unexpectedly.
Action: Make sure that your Named Pipes drivers are within the same
major version (for example, v2.x). If so, try adding RAM, reducing
your configuration options in the CONFIG.SYS file (for example,
reducing the size of DIRCACHE), removing optional device drivers
from the CONFIG.SYS file, and freeing up some hard disk space by
deleting unnecessary programs. If you are using multiple disk
partitions, consider moving the OS/2 swapper file to a larger partition.
Disk compression utilities may also be available that can help resolve
this problem. After completing these actions, shut down OS/2; then
reboot the system. If the problem persists, contact your Novell
Authorized Reseller.
Cause: General Service Query for Named Pipe Servers failed.
Error: %1. A call to IpxSend to issue a general service query
for named Pipe Servers failed.
Action: Make sure the IPX.SYS driver has been properly entered
in the CONFIG.SYS file. If so, check the messages displayed by
the driver for any errors or warnings, and correct the problems
indicated. Also make sure the IPXCALLS.DLL file is in the NetWare
Client for OS/2 directory. Try again. If the problem persists,
contact your Novell Authorized Reseller.
Cause: An error occurred while obtaining the IPX card table.
A call to the npserver.sys driver to obtain the IPX card table failed.
Action: Make sure the IPX.SYS driver and the NPSERVER.SYS driver
have been properly entered in the CONFIG.SYS file. If so, check
the messages displayed by the drivers for any errors or warnings,
and correct the problems indicated. Also make sure the IPXCALLS.DLL
and NPCALLS.DLL files are in the NetWare Client for OS/2 directory.
Try again. If the problem persists, contact your Novell Authorized
Reseller.
Cause: The SPX module is not installed. The Named Pipes daemon
could not open or communicate with the SPX.SYS driver.
Action: Make sure that the SPX.SYS driver has been properly
entered in the CONFIG.SYS file. If so, check the messages displayed
by the driver for any errors or warnings, and correct the problems
indicated; then try again. If the problem persists, contact your
Novell Authorized Reseller.
Cause: The IPX module is not installed. The Named Pipes daemon
could not open or communicate with the IPX.SYS driver.
Action: Make sure that the IPX.SYS driver has been properly entered
in the CONFIG.SYS file. If so, check the messages displayed by the
driver for any errors or warnings, and problems indicated; then try
again. If the problem persists, contact your Novell Authorized Reseller.
Cause: An incorrect OS/2 version is being used. The DosGetVersion
call failed (which would indicate an internal program error) or the
OS/2 version currently running is not v2.0 or later.
Action: Make sure that the client OS and NMPIPE.SYS driver are
compatible; then try again. If the problem persists, contact your
Novell Authorized Reseller.
Cause: The program cannot get code page information. Error: <code>.
The OS/2 system is not returning code page information. This may be
an internal program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: The Requester device driver and daemon are incompatible
versions. The most likely cause of this problem is that NWDAEMON.EXE
and NWREQ.SYS driver were not installed from the same installation disk.
Action: Install NetWare Client for OS/2 driver again, making sure it
is from the correct installation disk.
Cause: The worker DLL cannot be registered. Error: <code>.
The NWWORKER.DLL could not register with NetWare Client for OS/2.
This may be an internal program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: The broadcast handler cannot be registered. Error: <code>.
This may be an internal program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: The program cannot get system information. Error: <code>.
The OS/2 system is not returning system information. This may be
an internal program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: The janitor thread priority cannot be set. Error: <code>.
The janitor thread is set to run at regular priority. The system
had trouble setting the priority.
Action: Ignore the error.
Cause: The janitor daemon cannot be registered. Error: <code>.
This may be an internal program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: The program cannot get the current drive map. Error: <code>.
The OS/2 system is not returning the current drive map. This may be
an internal program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: The program cannot set the current drive map. Error: <code>.
The OS/2 system is not setting the current drive map. This may be an
internal program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: The program cannot get the connection ID. Error: <code>.
NetWare Client for OS/2 tried to locate a NetWare server when it
initialized. Either no servers are currently running or a cabling
problem exists.
Action: Make sure the NetWare server is running and functioning properly.
Also make sure the OS/2 machine has a working connection to the network;
then try again. If the problem persists, contact your Novell Authorized
Reseller.
Cause: An error occurred during attempt to initialize the cache. The
caching function is not working. This may be an internal program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: The daemon could not boost the thread priority. The thread is set
to run at a greater priority. The system had trouble setting the priority.
Action: Ignore the error.
Cause: The daemon could not register the DosBox handler. This may be
an internal program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: Not enough memory for diagnostic daemon. Error: <code>.
The NWDaemon program tried to allocate memory from the system for the
diagnostic thread to use as a stack, but the system returned an error.
Action: Try adding RAM, reducing your configuration options in the
CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing
optional device drivers from the CONFIG.SYS file, and freeing up some
hard disk space by deleting unnecessary programs. If you are using
multiple disk partitions, consider moving the OS/2 swapper file to a
larger partition. Disk compression utilities may also be available that
can help resolve this problem. After completing these actions, shut down
OS/2; then reboot the system. If the problem persists, contact your
Novell Authorized Reseller.
Cause: The diagnostic daemon cannot be started. Error: <code>.
The NWDaemon tried to start the diagnostic thread but the system
encountered an error condition. The system may have too many threads
already running, or this may be an internal program error.
Action: Try closing other applications that are currently running.
If the problem persists, contact your Novell Authorized Reseller.
Cause: The diagnostic daemon priority cannot be changed. Error: <code>.
The diagnostic thread is set to run a regular priority. The system had
trouble setting the priority.
Action: Ignore the error.
Cause: Not enough memory to start a new thread. Error: <code>.
The NWDaemon could not allocate memory from the system to create a
thread for a new task.
Action: Try adding RAM, reducing your configuration options in the
CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing
optional device drivers from the CONFIG.SYS file, and freeing up some hard
disk space by deleting unnecessary programs. If you are using multiple
disk partitions, consider moving the OS/2 swapper file to a larger partition.
Disk compression utilities may also be available that can help resolve
this problem. After completing these actions, shut down OS/2; then reboot
the system. If the problem persists, contact your Novell Authorized Reseller.
Cause: The SPX send thread cannot be started. Error: <code>.
This may be an internal program error.
Action: Try again. If the problem persists, contact your Novell Authorized
Reseller.
Cause: The SPX receive thread cannot be started. Error: <code>.
This may be an internal program error.
Action: Try again. If the problem persists, contact your Novell Authorized
Reseller.
Cause: The SFT 3 handler cannot be registered. This may be an internal
program error.
Action: Try again. If the problem persists, contact your Novell Authorized
Reseller.
Cause: Packet Burst cannot be initialized. This may be an internal program
error.
Action: Try again. If the problem persists, contact your Novell Authorized
Reseller.
Cause: Not enough memory for a network management thread (<error code>).
The NWDaemon tried to allocate memory from the system for a thread to
initialize network management, but memory was not available. Network
management cannot be initialized.
Action: Try adding RAM, reducing your configuration options in the
CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing
optional device drivers from the CONFIG.SYS file, and freeing up some
hard disk space by deleting unnecessary programs. If you are using
multiple partitions, consider moving the OS/2 swapper file to a larger
partition. Disk compression utilities may also be available that can
help resolve this problem. After completing these actions, shut down
OS/2; then reboot the system. If the problem persists, contact your
Novell Authorized Reseller.
Cause: A named pipe cannot be started for network management (<error code>).
The NWDaemon could not allocate a named pipe. Network management will not
be supported until the computer is rebooted. This error could result from
a variety of causes. Named Pipes or SPX may not be loaded, one of your
drivers may have opened too many Named Pipes already, you may not have
enough memory or disk space, or it may be an internal program error.
Action: Make sure that Named Pipes and SPX are loaded and that your system
has enough memory. (If you suspect a memory problem, see the discussion
for message 0843.) After completing these actions, reboot the system and
try again. If the problem persists, contact your Novell Authorized Reseller.
Cause: Not enough memory to run network management (<error code>).
The NWDaemon program tried to allocate memory from the system to run
network management, but memory is not available. Network Management
will not run until memory is available and the system rebooted.
Action: Try adding RAM, reducing your configuration options in the
CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing
optional device drivers from the CONFIG.SYS file, and freeing up some
hard disk space by deleting unnecessary programs. If you are using
multiple disk partitions, consider moving the OS/2 swapper file to a
larger partition. Disk compression utilities may also be available
that can help resolve this problem. After completing these actions,
shut down OS/2; then reboot the system. If the problem persists,
contact your Novell Authorized Reseller.
Cause: The NWREQ.SYS driver is not loaded. NetWare Client for OS/2
cannot be initialized until the driver is loaded.
Action: Load the NWREQ.SYS driver.
Cause: The program cannot allocate selectors for the workspace table.
All available memory selectors are being used by the system or by
previously loaded device drivers.
Action: Remove optional or unneeded device drivers from the CONFIG.SYS
file and try again. If the problem persists, contact your Novell Authorized
Reseller.
Cause: The program cannot allocate memory for the workspace table.
All available system memory is in use. NetWare Client for OS/2 cannot
load properly.
Action: Try adding Ram, reducing your configuration options in the
CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing
optional device drivers from the CONFIG.SYS file, and freeing up some
hard disk space by deleting unnecessary programs. If you are using
multiple disk partitions, consider moving the OS/2 swapper file to a
larger partition. Disk compression utilities may also be available that
can help resolve this problem. After completing these actions, shut
down OS/2; then reboot the system. If the problem persists, contact
your Novell Authorized Reseller.
Cause: Memory is not available for the cache table. Caching is disabled.
All available system memory is in use by the system. NetWare Client for
OS/2 cannot load properly.
Action: Try adding RAM, reducing your configuration options in the
CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing
optional device drivers from the CONFIG.SYS file, and freeing up some
hard disk space by deleting unnecessary programs. If you are using
multiple disk partitions, consider moving the OS/2 swapper file to a
larger partition. Disk compression utilities may also be available that
can help resolve this problem. After completing these actions, shut
down OS/2; then reboot the system. If the problem persists, contact
your Novell Authorized Reseller.
Cause: An incorrect OS/2 version is being used. The major versions of
NetWare Client for OS/2 and OS/2 do not match.
Action: Upgrade NetWare Client for OS/2 or OS/2.
Cause: The Requester driver version does not match the IFS version.
NWIFS.IFS and NWREQ.SYS were not installed from the same installation disk.
Action: Install NetWare Client for OS/2 again. If the problem persists,
contact your Novell Authorized Reseller.
Cause: The LAN support module is not installed. NetWare Client for OS/2
driver requires the LSL.SYS driver to be running when it loads. Either
the "DEVICE=C:\NETWARE\LSL.SYS" line is missing from the CONFIG.SYS file
or the LSL encountered an error while loading.
Action: Check the CONFIG.SYS file for the LSL.SYS driver. If this is not
the problem, contact your Novell Authorized Reseller.
Cause: A NetWare server cannot be found. NetWare Client for OS/2 tries to
locate a NetWare server when it initializes. Either no servers are currently
running or there is a cabling problem.
Action: Make sure that the NetWare server is running and operating properly.
Also make sure that the OS/2 machine is connected to the network.
Cause: The program cannot allocate selectors for the connection table.
All available memory selectors are being used by the system or by previously
loaded device drivers.
Action: Remove optional or unneeded device drivers from the CONFIG.SYS
file and try again. If the problem persists, contact your Novell Authorized
Reseller.
Cause: The program cannot allocate memory for the connection table. All
available system memory is in use. NetWare Client for OS/2 cannot load
properly.
Action: Try adding RAM, reducing your configuration options in the
CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing
optional device drivers from the CONFIG.SYS file, and freeing up some
hard disk space by deleting unnecessary programs. If you are using
multiple disk partitions, consider moving the OS/2 swapper file to a
larger partition. Disk compression utilities may also be available that
can help resolve this problem. After completing these actions, shut
down OS/2; then reboot the system. If the problem persists, contact
your Novell Authorized Reseller.
Cause: An incorrect OS/2 version is being used. The major version of
NetWare Client for OS/2 and OS/2 do not match.
Action: Upgrade NetWare Client for OS/2 or OS/2.
Cause: The config file cannot be parsed. Default parameters will be used.
NetWare Client for OS/2 driver could not read parameters in the NET.CFG file.
Action: Make sure the syntax for the NetWare Client for OS/2 section of
the file is correct.
Cause: An unrecoverable error occurred. The driver was not loaded. The
driver could not load properly. This is probably an internal program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: The program cannot allocate selectors for worker support. All
available memory selectors are being used by the system or by previously
loaded device drivers.
Action: Remove optional or unneeded device drivers from the CONFIG.SYS
file. Then try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: The program cannot allocate memory for the error message buffer.
All available system memory is in use by the system. NetWare Client for
OS/2 cannot load properly.
Action: Try adding RAM, reducing your configuration options in the
CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing
optional device drivers from the CONFIG.SYS file, and freeing up some
hard disk space by deleting unnecessary programs. If you are using
multiple disk partitions, consider moving the OS/2 swapper file to a
larger partition. Disk compression utilities may also be available
that can help resolve this problem. After completing these actions,
shut down OS/2; then reboot the system. If the problem persists,
contact your Novell Authorized Reseller.
Cause: The Requester could not send to NetWare server <number> as <number>.
Netware Client for OS/2 waits for a response from the server after each
request. If the server does not respond within a certain amount of time,
NetWare Client for OS/2 times out.
Action: Make sure that the server is still running and functioning properly.
Also make sure that all routers between the workstation and the server are
still running. If the problem persists, contact your Novell Authorized
Reseller.
Cause: The Requester timed out waiting for reply from server <number>.
NetWare Client for OS/2 waits for a response from the server after each
request. If the server does not respond within a certain amount of time,
NetWare Client for OS/2 times out.
Action: Make sure that the server is still running and functioning properly.
Also make sure that all routers between the workstation and the server are
still running. If the problem persists, contact your Novell Authorized
Reseller.
Cause: Server <number> did not respond to a request. NetWare Client for
OS/2 waits for a response from the server after each request. If the
server does not respond within a certain amount of time, NetWare Client
for OS/2 times out. This error can also occur if the server responds
with an unexpected response.
Action: Make sure that the server is still running and functioning
properly. Also make sure that all routers between the workstation and
the server are still running. If the problem persists, contact your
Novell Authorized Reseller.
Cause: Connection to NetWare server <number> as <number> is now invalid.
NetWare Client for OS/2 waits for a response from the server after each
request. If the server does not respond within a certain amount of time,
NetWare Client for OS/2 times out.
Action: Make sure that the server is still running and functioning
properly. Also make sure that all routers between the workstation and
the server are still running. If the problem persists, contact your
Novell Authorized Reseller.
Cause: Routing to NetWare server <number> has been disrupted. The
network route to the server has been disrupted.
Action: Make sure that the server is still running and functioning
properly. Also make sure that all routers between the workstation
and the server are still running. If the problem persists, contact
your Novell Authorized Reseller.
Cause: Routing to NetWare server <number> has been disrupted. The
network route to the server has been disrupted.
Action: Make sure that the server is still running and functioning
properly. Also make sure that all routers between the workstation
and the server are still running. If the problem persists, contact
your Novell Authorized Reseller.
Cause: The SPDaemon cannot get the SPX version. Error: <code>.
The SpxGetVersion call failed. This may be an internal program error.
Action: Make sure that the SPX.SYS driver has been properly entered
in the CONFIG.SYS file. If so, check the messages displayed by the
driver for any errors or warnings, and correct the problems indicated.
Check for a mismatch of driver versions. If the problem persists,
contact your Novell Authorized Reseller.
Cause: The SPX driver and the SPX daemon are incompatible versions.
The SPX.SYS driver and SPDAEMON.EXE versions may not match.
Action: Make sure that the client SPX.SYS driver and SPDAEMON.EXE
are compatible versions. If the problem persists, contact your Novell
Authorized Reseller.
Cause: The SPX driver entry cannot be obtained. Error: <code>.
The SPDaemon could not get a handle to the SPX.SYS driver. This may
be an internal program error.
Action: Make sure that the client SPX.SYS driver and SPDAEMON.EXE
versions are compatible. If the problem persists, contact your Novell
Authorized Reseller.
Cause: The SPX daemon is already loaded. Error: <code>.
The SPDAEMON.EXE has already registered with the SPX.SYS driver,
which means it is already loaded.
Action: Make sure that the daemon SPDAEMON.EXE has not been
entered in the CONFIG.SYS file more than once.
Cause: The daemon cannot register with the SPX driver. Error: <code>.
The SPDaemon cannot communicate with the SPX.SYS driver.
Action: Make sure that the SPX.SYS file has been properly entered in
the CONFIG.SYS file. If so, check the messages displayed by the driver
for any errors or warnings, and correct the problems indicated. Check
for a mismatch of driver versions. If the problem persists, contact
your Novell Authorized Reseller.
Cause: The SPX device handle cannot be closed. Error: <code>.
The SPDeamon cannot close the device handle. This may be an internal
program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: The SPDaemon cannot wait on semaphore. Error: <code>.
A DosSemSetWait call failed. This may be an internal program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: System information segments cannot be obtained. Error: <code>.
The DosGetInfoSeg call failed. This may be an internal program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: Priority for the lock thread cannot be set. Error: <code>.
The DosSetPrty call failed. This may be internal program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: The SPX driver cannot be accessed. Error: <code>.
The SPDaemon was not able to access SPX.SYS through the call gate.
Action: Make sure that the SPX.SYS driver has been properly entered
in the CONFIG.SYS file. If so, check the messages displayed by the
driver for any errors or warnings, and correct the problems indicated.
Also check for a mismatch of driver versions; then try again. If the
problem persists, contact your Novell Authorized Reseller.
Cause: Priority for an AES thread cannot be set. Error: <code>.
The DosSetPrty call failed. This may be an internal program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: Priority for a watchdog thread cannot be set. Error: <code>.
The DosSetPrty call failed. This may be an internal program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: Priority for a session thread cannot be set. Error: <code>.
The DosSetPrty call failed. This may be an internal program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: The SPXCALLS.DLL cannot register with the SPX driver. The
SPXCALLS.DLL cannot communicate with the SPX.SYS driver.
Action: Check to see if the SPX.SYS driver has been properly entered
in the CONFIG.SYS file. If so, check the messages displayed by the
driver for any errors or warnings, and correct the problems indicated.
Check for a mismatch of driver versions; then try again. If the problem
persists, contact your Novell Authorized Reseller.
Cause: The driver cannot initialize the CGroup Data variables.
Normally, key data variable are stored in the driver's CGroup
for easy and reliable access. However, in this instance the
variables could not be initialized due to a memory-related error.
Action: Try adding RAM, reducing your configuration options in
the CONFIG.SYS file (for example, reducing the size of DIRCACHE),
removing optional device drivers from the CONFIG.SYS file, and
freeing up some hard disk space by deleting unnecessary programs.
If you are using multiple disk partitions, consider moving the
OS/2 swapper file to a larger partition. Disk compression utilities
may also be available that can help resolve this problem. After
completing these actions, shut down OS/2; then reboot the system.
If the problem persists, contact your Novell Authorized Reseller.
Cause: The driver cannot configure SPX. The driver in conjunction
with the NWCONFIG.DLL failed to parse the NET.CFG file for the SPX
parameters.
Action: Make sure the format of the NET.CFG file is correct.
Cause: The driver failed to get support hooks from the LSL or IPX.
SPX could not open or communicate with either the LINKSUP_ (LSL.SYS)
or the IPX_ (IPX.SYS) drivers. The most likely cause of this error
is that one or both of these drivers has been improperly installed.
Action: Make sure that the device drivers LSL.SYS and IPX.SYS have
been properly entered in the CONFIG.SYS file. If so, check the messages
displayed by the driver for any errors or warnings, and correct the
problems indicated. Check for a mismatch of driver versions; then try
again. If the problem persists, contact your Novell Authorized Reseller.
Cause: The OS/2 version cannot be obtained; OS/2 v2.0 is assumed. The
DosGetVersion call failed (an internal program error), or the OS/2
version currently running is not v2.0 or later.
Action: Make sure that OS/2 and the SPX.SYS driver are compatible
versions. If this is not the problem, contact your Novell Authorized
Reseller.
Cause: The driver cannot get OS/2 DOS variables. The SPX.SYS driver
could not obtain either the system or local information segment. This
may be an internal program error.
Action: Try again. If the problem persists, contact your Novell
Authorized Reseller.
Cause: The driver cannot initialize the SPX call gate. The SPX.SYS
driver could not register a call gate with the LSL.SYS driver.
Action: Make sure that the LSL.SYS driver has been properly entered
in the CONFIG.SYS file. If so, check the messages displayed by the
driver for any errors or warnings, and correct the problems indicated.
Check for a mismatch of driver versions; then try again. If the problem
persists, contact your Novell Authorized Reseller.
Cause: The driver cannot allocate memory for SPX use. The system does
not have enough memory to run SPX.
Action: Try adding RAM, reducing your configuration options in the
CONFIG.SYS file (for example, reducing the size of DIRCACHE), removing
optional device drivers from the CONFIG.SYS file, and freeing up some
hard disk space by deleting unnecessary programs. If you are using
multiple disk partitions, consider moving the OS/2 swapper file to a
larger partition. Disk compression utilities may also be available that
can help resolve this problem. After completing these actions, shut down
OS/2; then reboot the system. If the problem persists, contact your
Novell Authorized Reseller.
Cause: The application cannot initialize named pipes. The application
could not open or communicate with the NMPIPE.SYS driver. Most likely,
the NMPIPE.SYS driver is not entered in the CONFIG.SYS file.
Action: Make sure that the NMPIPE.SYS driver have been properly entered
in the CONFIG.SYS file. If so, check the messages displayed by the driver
for any errors or warnings, and correct the problems indicated. If the
problem persists, contact your Novell Authorized Reseller.