REMOTE MHS MESSAGES
------------------


Novell, Inc. makes no representations or warranties with respect
to the contents or use of this manual, and specifically disclaims
any express or implied warranties of merchantability or fitness for
any particular purpose. Further, Novell, Inc. reserves the right
to revise this manual and to make changes to its content, at any
time, without obligation to notify any person or entity of such
revisions or changes.

Further, Novell, Inc. makes no representations or warranties with
respect to any NetWare software, and specifically disclaims any
express or implied warranties of merchantability or fitness for any
particular purpose. Further, Novell, Inc. reserves the right to
make changes to any and all parts of NetWare software, at any time,
without any obligation to notify any person or entity of such
changes.

Novell, NetWare and the N design are registered trademarks and
Remote MHS, FirstMail, Global MHS, NetWare Remote MHS, NetWare
Global MHS, NetWare MHS, NetWare Loadable Module, and NLM are
trademarks of Novell, Inc.

April 1993



REMOTE MHS MESSAGES
-------------------

Remote MHS log messages have the following format:

<c><nnnn> <message>

where <c> is the error code (for a list of valid codes, see the
following table), <nnnn> is the message number, and <message> is
the message text.



Error Codes

	F	Fatal error. Remote MHS has detected an unrecoverable
error which prevents Remote MHS from continuing.

	E	Error. Remote MHS has detected an error which prevents
it from completing an operation.

	I	Information. Remote MHS displays informational messages
indicating the action or function being performed. No
action is required.

	W	Warning. An error occurred, but Remote MHS continues
processing. Remote MHS makes assumptions but lets you
know what they are.

This section lists and explains log messages. Messages are sorted
by message number. When searching for an error message, disregard
the error code (that is, the "E," "F," "I," or "W").



1313 Not enough memory

EXPLANATION: The workstation does not have enough free system
memory to run RMHS.

ACTION: Check to see whether the workstation has sufficient main
memory (refer to Chapter 2, "Installing and Configuring NetWare
Remote MHS," to find out how much you need). If it does have
sufficient memory, review the contents of the AUTOEXEC.BAT and
CONFIG.SYS files to determine whether there are any resident
programs conflicting with the RMHS program. If you have run RMHS
from a shell, exit the shell and run RMHS without it.


1322/1328 Connectivity Server aborted, error <nn>

EXPLANATION: RMHS was unable to continue because of a fatal error.
This is usually the last message in a series of two or more
messages.

ACTION: Check the RMHS log for error messages to find out what
action to take.


1329 Please set the clock

EXPLANATION: Remote MHS suggests that the system clock be set
correctly.

ACTION: Set the remote workstation to the current date and time.


1332 Can't find Routing Directory

EXPLANATION: The NETDIR.TAB or the NAMES.INF files, which contain
routing tables, is missing, or the environment variable is set
incorrectly.

ACTION: Ensure that the MV variable is pointing to the MHS\EXE
directory (use the DOS SET command). If it is, confirm that
NETDIR.TAB and NAMES.INF files are in the MHS\MAIL\PUBLIC
directory. If they are not, restore them from a backup copy or
reinstall Remote MHS.


1337 Illegal serial number

EXPLANATION: Remote MHS determined that the serial numbers in some
of your executable programs do not match.

ACTION: Check the validity of your installation diskettes. If the
problem persists, verify that Remote MHS was installed correctly.
If necessary, reinstall Remote MHS using the INSTALL program.


1338 File open error: MAIL\PUBLIC\NETMGR.QUE
1339 NETMGR.QUE: Could not read record #<nn>
1340 NETMGR.QUE: File is corrupt (missing messaging server
`<server>')

EXPLANATION: An error occurred while Remote MHS was attempting to
open a file. This error can occur for one of the following reasons:

1.	Remote MHS is not properly installed.

2.	The NETMGR.QUE file does not exist (it might have been deleted).

3.	RMHS cannot access NETMGR.QUE.

4.	A disk error occurred.

ACTION: To resolve the problem:

1.	Verify that Remote MHS is properly installed. If necessary,
reinstall Remote MHS using the INSTALL batch file.

2.	Check the MHS\MAIL\PUBLIC directory to see if the NETMGR.QUE
file exists. If it does not, restore it from backup.

3.	If the NETMGR.QUE file exists, ensure there are no resident
programs accessing it.

4.	Use the CHKDSK command to check for disk errors. If there are no
disk errors, restore Remote MHS from backup or reinstall Remote
MHS.


1343 NETMGR.QUE: Version <nn> does not match the current version
<nn>

EXPLANATION: The Remote MHS NETMGR.QUE file is corrupt, or the MV
environment variable is pointing to the wrong directory.

ACTION: Ensure the MV environment variable is pointing to the path
containing the MHS directory. If it is, make sure the NETMGR.QUE
file exists. If the NETMGR.QUE does not exist, restore Remote MHS
from backup or reinstall it.


1345 NETMGR.QUE: File is corrupt (header count <nn>, actual count
<nn>)

EXPLANATION: The NETMGR.QUE file contains information that does not
coincide with information contained in the one or more of the other
database files. This is known as being in an inconsistent state.

ACTION: Contact Novell Technical Support.


1347 NETMGR.QUE: Write error on record #<nn>

EXPLANATION: Remote MHS tried to write to a record associated with
the specified record number. This error occurs if you have the DOS
read-only flag set on the NETMGR.QUE file, or you are running out
of disk space.

ACTION: Check to make sure that NETMGR.QUE file does not have the
DOS read-only flag set. If NETMGR.QUE is writable,check to see
whether the workstation has sufficient main memory (refer to
Chapter 2, "Installing and Configuring NetWare Remote MHS,"  to
find out how much you need). If the workstation does not have
sufficient memory, review the contents of the AUTOEXEC.BAT and
CONFIG.SYS files to determine whether there are any resident
programs that can be removed to free additional memory.


1349 NETMGR.QUE: Could not update queue info for messaging server
<server>

EXPLANATION: Remote MHS failed to update information for the server
after performing a function on the server's queue. This error can
occur if the NETMGR.QUE file is corrupt, or if a disk error has
occurred.

ACTION: Use the CHKDSK command to check for disk errors. If there
are no disk errors,restore NETMGR.QUE from backup or reinstall.


1350 Could not open NETMGR.QUE file

EXPLANATION: An error occurred while Remote MHS was attempting to
open a file. This error can occur for one of the following reasons:

1.	Remote MHS is not properly installed.

2.	The NETMGR.QUE file does not exist (it might have been deleted).

3.	RMHS cannot access NETMGR.QUE.

4.	A disk error occurred.

ACTION: To resolve the problem:

1.	Verify that Remote MHS is properly installed. If necessary,
reinstall Remote MHS using the INSTALL batch file.

2.	Check the MHS\MAIL\PUBLIC directory to see if the NETMGR.QUE
file exists. If it does not, restore it from backup.

3.	If the NETMGR.QUE file exists, ensure there are no resident
programs accessing it.

4.	Use the CHKDSK command to check for disk errors. If there are no
disk errors, restore Remote MHS from backup or reinstall Remote
MHS.


2520 NAMP connect negotiation failed. Possible causes of this error
are: Noisy/bad telephone connection, incorrect password,
incompatible server software, server configuration error, or for
RMHS, incorrect setting of Full/Part-time remote mode. Examine
configuration and try again.

EXPLANATION: Remote MHS timed out while waiting for agreement from
the server on which protocol to use. Possible causes of this error
are:

1.	Noisy or bad telephone connection

2.	Incorrect password was submitted.

3.	Incompatible server software

4.	Server configuration error

5.	Incorrect setting of full-time/part-time remote mode.

ACTION: To resolve the problem:

1.	Check for loose connections.

2.	Ensure the correct password was submitted.

3.	Ensure you are running MHS 2.0 Rev B or greater on your server.

4.	Ensure the server is configured correctly.

5.	Ensure that you have selected the correct type of Remote
operation.


2522 Sorry, your SMF version <nn> is not supported by this server

EXPLANATION: Remote MHS could not connect to the server because
your SMF version does not match the SMF version supported by the
server.

ACTION: Report the problem to the server administrator. Change the
SMF version specified on the Remote MHS Configuration screen to
match the SMF version supported by the server to allow a connection
to be made.


2523 Terminating connection, server <server> has an unsupported SMF
version <nn>

EXPLANATION: Remote MHS tried to connect with the specified server,
but the connection was terminated because the server has an SMF
version number that is not supported by Remote MHS.

ACTION: Report the problem to the server administrator. Change the
SMF version specified for the server to match the SMF version
supported by Remote MHS.


2530 NAMP: Too many connect negotiate retries

EXPLANATION: Remote MHS tried to connect to another server, but
failed.

ACTION: Check the modem configuration and line connections. If the
problem persists, call Novell Technical Support.



2531 NAMP: Timeout waiting for reply from server

EXPLANATION: Remote MHS timed out while waiting for a reply from
the server.

ACTION: Check the modem configuration and line connections. Refer
to your modem documentation for configuration requirements. If the
problem persists, call Novell Technical Support.


2532 NAMP: Unexpected character while receiving negotiation frame

EXPLANATION: An unexpected character arrived during the NAMP
connect negotiate process. (The NAMP connect negotiate process is
where Remote MHS and the server agree on which asynchronous
protocol to use.) This problem might result from line noise or a
bad connection.

ACTION: Ensure the modem is properly configured, and ensure the
line connections are working. If the problem persists, call Novell
Technical Support.


2533 NAMP: Connect negotiate CRC error

EXPLANATION: The checksum contained in the NAMP connect negotiate
frame sent by Remote MHS does not match the checksum received by
the server. (A NAMP connect negotiate frame is a message sent
between Remote MHS and the server to allow them to agree on which
asynchronous protocol to use.) This problem might result from line
noise or a bad connection.

ACTION: Check the modem configuration and line connections. If the
problem persists, call Novell Technical Support.


2534 NAMP: Connect negotiate frame version mismatch

EXPLANATION: Remote MHS tried to connect to a server that does not
support the same format of NAMP connect negotiate frame. (A NAMP
connect negotiate frame is a message sent between Remote MHS and
the server to allow them to agree on which asynchronous protocol
to use.)

ACTION: Ensure that the modem is configured correctly. Refer to
your modem documentation for this information. If it is, check the
telephone line connections. If the problem persists, call Novell
Technical Support.


2535 NAMP: Connect negotiate messaging server type mismatch

EXPLANATION: A frame arrived with an incorrect value in the host
type field. This problem might result from line noise.

ACTION: Check the telephone line connections. If the problem
persists, call Novell Technical Support.


2536 NAMP: Connect negotiate frame rejected by remote server

EXPLANATION: The remote messaging server does not support the
version numbers described in the NAMP connect negotiate frame. (A
NAMP connect negotiate frame is a message sent between Remote MHS
and the server to allow them to agree on which protocol to use.)

ACTION: Check the modem configuration and line connections. If the
problem persists, call Novell Technical Support.


2537 NAMP: Unexpected character received waiting for response

EXPLANATION: While waiting for a response, the NAMP connect
negotiate process received a character that it was not expecting.
(The NAMP connect negotiate process is the process during which
Remote MHS and the server establish an agreement about which
asynchronous protocol to use.) This problem might result from line
noise.

ACTION: Ensure that the telephone line connection is working. If
the problem persists, call Novell Technical Support.


2538 NAMP: Insufficient memory

EXPLANATION: Remote MHS ran out of memory while trying to allocate
memory for a NAMP connect negotiate frame. (A NAMP connect
negotiate frame is a message sent between Remote MHS and the server
during an asynchronous connection to allow them to agree on which
protocol to use.)

ACTION: Check to see whether the workstation has sufficient main
memory (refer to the "Getting Started with Remote MHS" manual to
find out how much you need). If it does have sufficient memory,
review the contents of the AUTOEXEC.BAT and CONFIG.SYS files to
determine whether there are any resident programs that can be
removed to free additional space.


2550 Error in modem definition file

EXPLANATION: The text file, <modem>.MDF, that specifies commands
and responses for the modem, contains an invalid keyword or is
damaged.

ACTION: Restore the modem definition file, <modem>.MDF from backup.
If the problem persists, contact the supplier of the modem
definition file.


2553 Timeout waiting for modem response

EXPLANATION: The receiving modem did not respond as expected to a
command from the modem definition file (the text file that
specifies commands and responses for the sending modem).

ACTION: Verify that the correct Modem Type is selected on the
Remote MHS Configuration screen. Reset the modem and retry sending
the message. If the problem persists, call Novell Technical
Support.


2554 Unsupported modem speed (<nnnn> bps)

EXPLANATION: The Modem Speed selected in the Remote MHS
Configuration screen is not supported by your modem.

ACTION: Enter a valid modem speed.


2555 Modem is not responding

EXPLANATION: The modem is not responding to commands from the modem
definition file (the text file that specifies commands and
responses for the sending modem).

ACTION: Verify that the correct Modem Type is specified on the
Remote MHS Configuration screen and reset the modem. If the problem
persists, call Novell Technical Support.


2556 Invalid modem response

EXPLANATION: The modem response did not match the expected response
in the modem definition file (the text file that specifies commands
and responses for the sending modem).

ACTION: Verify that the correct Modem Type is selected on the
Remote MHS Configuration screen and reset the modem. If the problem
persists, call Novell Technical Support.


2557 Modem indicates an error has occurred

EXPLANATION: The modem returned a response indicating an incorrect
match between the text file that specifies commands and responses
for the modem and the modem being used.

ACTION: Verify that the correct Modem Type is specified on the
Remote MHS Configuration screen and reset the modem.


2558 Adjusting modem speed to nnnn bps

EXPLANATION: This message indicates MHS is adjusting the modem
speed of the sending modem to match the speed of the receiving
modem.

ACTION: No action is required.


2559 Carrier still active, hangup failed

EXPLANATION: RMHS failed to hang up the modem.

ACTION: Verify that the correct Modem Type is selected on the
Remote MHS Configuration screen and reset the modem. If the error
recurs, check the modem cables and line connections.


2560 Speaker command failed

EXPLANATION: RMHS failed to adjust the modem speaker state.

ACTION: Verify that the correct Modem Type is selected on the
Remote MHS Configuration screen and reset the modem. If the error
recurs, check the modem cables and line connections.


2561 Protocol command failed

EXPLANATION: RMHS failed to issue a command to use one or more of
the modems advanced features such as data compression and error
detection.

ACTION: Verify that the correct Modem Type is selected on the
Remote MHS Configuration screen and reset the modem.


2563 Initialization command failed

EXPLANATION: RMHS failed to send an initialization command to the
modem.

ACTION: Verify that the correct Modem Type is specified on the
Remote MHS Configuration screen and reset the modem.


2564 Dial speed command failed

EXPLANATION: RMHS failed to send a dial speed command to the modem.

ACTION: Verify that the correct Modem Type is specified on the
Remote MHS Configuration screen and reset the modem.


2565 One or more modem commands failed

EXPLANATION: RMHS failed to send a command to the modem.

ACTION: Verify that the correct Modem Type is selected on the
Remote MHS Configuration screen and reset the modem.


2566 Could not change modem speed to <nnnn> bps

EXPLANATION: RMHS failed to adjust the communications port speed
of the sending modem to match the speed of the receiving modem.

ACTION: Verify that the correct Modem Type is specified on the
Remote MHS Configuration screen. Also, check the modem setting for
mismatches.


2567 Inconsistent modem configuration

EXPLANATION: An internal program error occurred.

ACTION: Call Novell Technical Support.


2568 Out of memory in modem layer

EXPLANATION: RMHS ran out of memory while allocating memory to
store the modem definition file (the text file that specifies
commands and responses for the sending modem).

ACTION: Check to see whether the workstation has sufficient main
memory (refer to Chapter 2, "Installing and Configuring NetWare
Remote MHS," to find out how much you need). If it does have
sufficient memory, review the contents of the AUTOEXEC.BAT and
CONFIG.SYS files to determine whether there are any resident
programs that can be removed to free additional space.


2569 Dialing nnn-nnnn at nn bps, tone|pulse dial, negotiation
off|on

EXPLANATION: This is an informative message that displays when your
messaging server dials another server. It displays the telephone
number, the speed, the type of dialing system and whether
negotiation is off or on.

ACTION: No action is required.


2570 Modem dial failed

EXPLANATION: RMHS failed to send a dial command to the modem.

ACTION: Verify that the correct Modem Type is specified on the
Remote MHS Configuration screen and reset the modem


2573 I/O error during open|read operation in <filename>.MDF

EXPLANATION: A DOS file Input/Output error has occurred.

ACTION: Check to make sure that the specified file exists. If it
does exist, check to make sure there is enough disk space. If enough
disk space is available, check to make sure you have sufficient
access rights to the file. Finally, check your network connections.


2574 Modem could not detect carrier

EXPLANATION: RMHS placed a call and the answering modem did not
respond with a carrier signal.

ACTION: Have your administrator verify that the remote server is
configured to answer calls. If it is, verify that the phone number
is correct. If it is, check the modem settings specified on the
Remote MHS Configuration screen to make sure they are correct for
the modem type selected. If the problem persists, call Novell
Technical Support.


2575 Modem could not detect dialtone

EXPLANATION: When preparing to place a call, RMHS detected that the
phone line did not have a dialtone.

ACTION: Check the phone line connection and verify that it is
working. If it is, check the modem settings specified on the Remote
MHS Configuration screen. If the problem persists, call Novell
Technical Support.


2576 Modem detected a busy signal

EXPLANATION: RMHS could not complete a call to the server because
the line was busy.

ACTION: Try calling again in a few minutes, the line may be engaged.
If the line continues to report a busy signal, verify that the phone
number specified on the Remote MHS Configuration screen is correct.
If the phone number is correct, verify that the phone line is
working. If the phone line is working, check the modem settings.
If the modem settings are correct, have the administrator verify
that the server is configured to answer calls. If the problem
persists, call Novell Technical Support.


2577 Called server is not answering

EXPLANATION: The server did not answer a call from Remote MHS.

ACTION: Verify that the remote server is configured to answer
calls. If it is, verify that the phone number specified on the
Remote MHS Configuration screen is correct. If the phone number is
correct, verify that the phone line is working. If it is working,
check the modem settings on the Remote MHS Configuration screen.
If the problem persists, call Novell Technical Support.


2578 Modem detected human voice instead of carrier

EXPLANATION: RMHS detected a human voice instead of a carrier
signal when calling the messaging server.

ACTION: Verify that the phone number specified on the Remote MHS
Configuration screen is correct. If the phone number is correct,
verify that the phone line is working. If it is working, check the
phone line connect and modem settings. If the problem persists,
call Novell Technical Support.


2580 Waiting for modem connection...

EXPLANATION: MHS answered an incoming call or placed an outgoing
call and is awaiting further data.

ACTION: No action is required.


2581 High-speed connection established

EXPLANATION: MHS has connected to another messaging server at a
rate greater than 9600 bps.

ACTION: No action is required.


2582 High-speed connection with protocol established

EXPLANATION: MHS has connected to another messaging server at a
rate exceeding 9600 bps. Error correction, or data compression, or
both, are enabled.

ACTION: No action is required.


2583 Established nn bps connection

EXPLANATION: MHS has connected to another messaging server at the
specified connection rate.

ACTION: No action is required.


2584 Established nn bps connection with protocol

EXPLANATION: MHS has connected to another messaging server at the
specified connection rate. Error correction, or data compression,
or both, are enabled.

ACTION: No action is required.


2585 Could not establish modem connection

EXPLANATION: The calling and answering modems failed to establish
a connection.

ACTION: Verify that the correct Modem Type is specified on the
Remote MHS Configuration screen, and that the Remote MHS and server
modems are compatible. Refer to your modem documentation for more
information.


2586 Text of the display

EXPLANATION: A display command (DISP) has been specified in the
host or data network login script and the text entered is
displayed.

ACTION: No action is required.


2587 Out of memory executing script. Could not allocate script
handle

EXPLANATION: Remote MHS ran out of memory while allocating the data
structures required to run a data network login script.

ACTION: Check to see whether the workstation has sufficient main
memory (refer to Chapter 2, "Installing and Configuring NetWare
Remote MHS," to find out how much you need). If it does have
sufficient memory, review the contents of the AUTOEXEC.BAT and
CONFIG.SYS files to determine whether there are any resident
programs that can be removed to free additional space.


2588 Script file `<filename>' cannot be compiled

EXPLANATION: The host or data network login script file specified
by <filename> contains a syntax error.

ACTION: Contact the author of the script file and have them verify
that the script file has not been damaged.


2589 Error executing script file `<filename>'

EXPLANATION: Remote MHS failed to execute a data network login
using the specified script.

ACTION: Verify the data network configuration and parameters are
correct.


2600 Timeout sending data to serial port

EXPLANATION: RMHS failed to transmit data using your communications
hardware.

ACTION: Verify the port settings.


2601 Invalid value returned error code <nnnn> sending data to the
serial port

EXPLANATION: Remote MHS received an invalid value while sending
data to the serial port.

ACTION: Verify that the port and driver interface settings for your
modem are correct. You will obtain this information from your modem
documentation. If you are using a third-party device driver,
contact your supplier to determine whether it is compatible with
Remote MHS.


2602 Out of memory allocating serial port data structures

EXPLANATION: RMHS ran out of memory while allocating serial port
data structures.

ACTION: Check to see whether the workstation has sufficient main
memory (refer to Chapter 2, "Installing and Configuring NetWare
Remote MHS," to find out how much you need). If it does have
sufficient memory, review the contents of the AUTOEXEC.BAT and
CONFIG.SYS files to determine whether there are any resident
programs that can be removed to free additional space.


3000 Connecting to server [server] at nn...

EXPLANATION: Your messaging server is connecting to another server
at nn bps.

ACTION: No action is required. However, if you want to prevent the
connection, press <Esc>.


3001 < No answer [<nn>:<nn>]

EXPLANATION: The server did not answer the call and returned an
internal error code. The attempted connection was terminated.

The number <nn>:<nn> indicates the layer of the file transfer
protocol where the disconnection was first detected.

ACTION: Check the modem connections and try the call again. If the
connection continues to fail, ensure that the modem hardware and
the telephone lines are working properly.


3003 Attempted to call |<server1>|; but |<server2>| answered

EXPLANATION: When Remote MHS tried to connect to <server1>, a
messaging server named <server2> answered. The telephone number of
<server1> is probably incorrect.

ACTION: Check with the server administrator at <server1> to find
out the server telephone number.


3004 < Connection{<n>} broken [<nn>:<nn>]

EXPLANATION: The connection to the server was terminated before the
message transfer completed. Any messages that were successfully
transferred before the connection terminated will be deleted from
the sending queue.

The connection number indicates the progress of the message
transfer before the broken connection occurred. It can have the
following values:

	0 (or no brace at all)

	The connection was not yet fully established.

	1

	The connection was fully established, and the transfer
of the file that contains the messages had begun.

	2

	The transfer of the message file is complete, and
transfer of attachments has begun, but is not yet
complete.

The final number ([<nn>:<nn>]) in the error message, indicates the
layer of the file transfer protocol where the disconnection was
first detected.

ACTION: Check the line connections and the modem power supplies,
and try the call again. If the connection continues to fail, ensure
the modem hardware and telephone lines are working properly.


3006 < Disconnect [nn:nn]

EXPLANATION: Your messaging server is terminating a connection with
another server.

The number nn:nn indicates the layer of the file transfer protocol
where the disconnection was first detected.

ACTION: No action is required.


3019 NETMGR.QUE: File is empty

EXPLANATION: Remote MHS was not properly installed or this file was
damaged.

ACTION: Restore Remote MHS from backup or reinstall Remote MHS.


3037 Modem: modem_type [Comn: speed]

EXPLANATION: This message is generated when MHS starts. It tells
you which modem this transport server is configured to use.

ACTION: No action is required.


3045 > WARNING: your messaging server is not declared here

EXPLANATION: Your messaging server is not defined in the MHS
database of the server it is calling. However, the answering server
is configured to accept calls from unknown servers.

ACTION: No action is required.


3046 > Incorrect password; access denied

EXPLANATION: Remote MHS submitted an incorrect password to the
server so the server broke the connection; no messages were
transferred.

ACTION: Contact the server administrator to find out what password
you should use. Then enter that password in the Password field on
the Remote MHS Configuration screen.


3048 > WARNING: your mail is routed via messaging server |<server>|

EXPLANATION: Remote MHS connected to a server that routes your
messages to a third server. Although the warning is displayed,
messages are transferred.

ACTION: If you expect to get messages directly from the server,
contact its server administrator to investigate the situation.


3049 < Connection broken [<nn>:<nn>]

EXPLANATION: The connection to the server terminated before message
transfer was completed. Any messages that were transferred before
the connection terminated will be deleted from the sending queue.

The number ([<nn>:<nn>]) in the message indicates the layer of the
file transfer protocol where the disconnection was first detected.

ACTION: Check the connections and the modem power supplies, and try
the call again. If the connection continues to fail, check the
modem hardware, the modem configuration, and the line connections.


3050 Denied access

EXPLANATION: Remote MHS was denied access to the server. The
connection was broken, and no messages were transferred. This error
occurs if your password is incorrect, or if your name is the same
as the name of a server or user defined on your server.

ACTION: Call the server administrator to ensure that your password
is correct and that your server name is unique.


3052 Error code S. [Contact Novell for assistance.]

EXPLANATION: A programming error occurred. The connection
terminated and no messages were transferred.

ACTION: Contact Novell Technical Support.


3057 > No queued communications

EXPLANATION: The remote messaging server has no messages for
delivery to your server.

ACTION: No action is required.


3058 < Disconnect

EXPLANATION: The call has ended and communication has terminated.

ACTION: No action is required.


3091 INCOMING: nn COMs, aa ATTs (bb bytes, count=cc); approx. time
nn:nn:nn

EXPLANATION: The messaging server has nn messages and aa
attachments waiting for delivery to you. The total size of incoming
messages and attachments is bb bytes, and transfer time is
approximately nn:nn:nn.

ACTION: No action is required.


3104 Communicating with another messaging server...

EXPLANATION: This is a status update message.

ACTION: No action is required.


3106 Call to server n:nn:nn status

EXPLANATION: This message reports that your messaging server called
another server, the time at which the call occurred, and the call
status.

ACTION: No action is required.


3142 |<variable>| is an unsupported version |<nn>|

EXPLANATION: Remote MHS tried to connect to a server with an SMF
version that Remote MHS does not support.

ACTION: Have the administrator upgrade the server to an SMF version
that Remote MHS supports.


3400 COM port is OFF-LINE

EXPLANATION: RMHS attempted to initialize the communication
hardware, but the hardware did not respond properly.
Telecommunication transfer activities cannot be started.

ACTION: Check your modem connection.


3511 server: File is missing

EXPLANATION: A file that RMHS needs is missing. RMHS will not be
able to finish the operation.

ACTION: No action is required.


3513 Transfer cancelled: server (<nn> bytes)

EXPLANATION: The transfer of messages was terminated prematurely.
This error might occur if the receiving modem was disconnected
during message transfer, if there is a problem with the telephone
lines, or if the receiving workstation ran out of disk space.

ACTION: Contact the server administrator and report the problem.


3515 Sent: server (nnnnn bytes)

EXPLANATION: This message indicates the size of data that was sent
to the specified server.

ACTION: No action is required.


3516 Timeout (nn min:nn sec)

EXPLANATION: Remote MHS timed out while waiting for a response from
the messaging server.

ACTION: No action is required.


3520 > Postman at "server" (description) answered [ID:nn]

EXPLANATION: Remote MHS is calling the specified server. This
message identifies the answering server.

ACTION: No action is required.


3532 Could not create <file>

EXPLANATION: Remote MHS could not create the specified <file>
because there is not enough disk space or you do not have sufficient
NetWare rights.

ACTION: Ensure that there is sufficient disk space on the volume
on which you installed Remote MHS. To obtain additional disk space,
delete any unnecessary files.


3538 < Recvd: filename (nnnnn bytes)

EXPLANATION: This message indicates the filename of the file
received and the file size in bytes.

ACTION: No action is required.


3539 > Disconnect.

EXPLANATION: RMHS is terminating the connection to the messaging
server.

ACTION: No action is required.


3552 Could not initialize Async Transport layer (out of memory?)

EXPLANATION: RMHS could not start a connection. This problem might
result from insufficient memory.

ACTION: Check to see whether the workstation has sufficient main
memory (refer to Chapter 2, "Installing and Configuring NetWare
Remote MHS," to find out how much you need). If it does have
sufficient memory, review the contents of the AUTOEXEC.BAT and
CONFIG.SYS files to determine whether there are any resident
programs that can be removed to free additional space.


3927 Message #nn, Size nn bytes, nn Attachment(s)

EXPLANATION: This message indicates a message bearing a message
number, size and number of attachments is being processed.

ACTION: No action is required.


3928 Processing outgoing MHS mail

EXPLANATION: RMHS is delivering outgoing messages in the
MHS\MAIL\SND directory.

ACTION: No action is required.


4007 Initializing...

EXPLANATION: RMHS is initializing data. It is displayed during RMHS
start-up.

ACTION: No action is required.


4019 Log file does not exist or cannot be opened

EXPLANATION: This error might appear for the following reasons:

1.	If the RMHS log file does not exist or is damaged.

2.	The log file has read-only attribute set.

3.	If a disk error occurred.

ACTION: To resolve the problem:

1.	If the <mv>\MHS\MAIL\PUBLIC directory does not contain MHS.LOG,
the file does not exist. RMHS will create the file when it runs.

2.	Ensure that RMHS.LOG does not have read-only attribute set.

3.	Use the CHKDSK command (for a local drive) or the VREPAIR command
(for a network drive) to check for disk errors.


4033 Resetting modem...

EXPLANATION: RMHS is instructing the modem to hang up and return
to a known state.

ACTION: No action is required.


4034 Reinitializing modem. This may take a few seconds...

EXPLANATION: RMHS is reconfiguring the modem (this takes between
five and ten seconds). If you enter any keystrokes, they will be
processed when initialization is finished.

ACTION: No action is required.


5200 Sending complete

EXPLANATION: All messages have been transferred successfully to the
messaging server.

ACTION: No action is required.


5201 Sequence error nn

EXPLANATION: A transmission error occurred during a message
transfer using the BPLUS Protocol. RMHS automatically retries.

ACTION: No action is required.


5202 Receiving complete

EXPLANATION: All messages from the messaging server have been
delivered to your workstation.

ACTION: No action is required.


5203 Disconnect

EXPLANATION: MHS is terminating a connection with another messaging
server.

ACTION: No action is required.


5204 Partial

EXPLANATION: Only part of the incoming message was transferred. An
accompanying error message explains why a partial transfer
occurred.

ACTION: Check the accompanying message to find out what action to
take.


5222 Error setting bps rate to <nnnn>

EXPLANATION: RMHS could not change the bps rate. This error occurs
if the transport server setup is incorrect, or if a hardware error
occurred.

ACTION: Check the Modem Speed and Modem Type specified on the
Remote MHS Configuration screen, to ensure that they are valid for
your modem. If they are, find out whether the modem is faulty.
Replace the modem, if necessary.


5225/5226 Call to server (S/N: serial_no v:nn l:nn)

EXPLANATION: RMHS is making a call to the specified server.

ACTION: No action is required.


5227 Preparing remote mail for new MHS version, please call later

EXPLANATION: Your server's SMF version is different than the SMF
version defined for it in the remote server's MHS database. The
remote server must reformat messages to the correct version before
it can deliver them.

ACTION: No action is required. The server will deliver the messages
during the next communication session.


5233 Send nn messages, aa attachments (bb bytes)

EXPLANATION: RMHS has nn messages and aa attachments, totalling bb
bytes, to send to the messaging server.

ACTION: No action is required.


5234 Receive nn messages, aa attachments (bb bytes)

EXPLANATION: MHS has nn messages and aa attachments, totalling bb
bytes, to receive from the messaging server.

ACTION: No action is required.


5235 Time this call will take (estimate): nn:nn:nn

EXPLANATION: This message tells you approximately how long it will
take to transfer messages to the messaging server.

ACTION: No action is required.


5300 Hardware initialization failure, COM<n>:

EXPLANATION: The specified COM port is defective, is incorrectly
configured, does not exist, or the modem does not support the
selected speed.

ACTION: Ensure that the workstation contains the COM port specified
on the Remote MHS Configuration screen. If the correct COM port is
specified, the COM port might be defective.


5302 MHS has received a BPLUS packet whose length (<nn> bytes)
exceeds the limit (<bb> bytes)

EXPLANATION: Remote MHS is communicating with a server through an
asynchronous connection using the BPLUS protocol. The maximum
packet size has been negotiated to be <bb> bytes. The size of the
packet received is greater than this limit. This error can occur
if there is line noise, or if the server is not MHS-compatible.

ACTION: To find out what kind of server Remote MHS is communicating
with, contact the server administrator at the remote server. If the
problem persists, contact Novell Technical Support.


5304 <Esc> key hit - operation aborted

EXPLANATION: You pressed the <Esc> key while an RMHS operation was
in progress. Error messages immediately following this message are
a direct result of this action and should be ignored.

ACTION: Start the operation over again.


6125 This user does not use the application application

EXPLANATION: When an application sends a message to a user, it can
tell MHS what application to deliver the message to (for example,
it delivers mail to MHS). If a user does not use the specified
application, MHS will not deliver the message.

ACTION: No action is required.


6126 Not a user of this application

EXPLANATION: When an application sends mail to a user, it can tell
RMHS what application to deliver mail to (for example, it delivers
mail to MHS). If a user does not use the application, RMHS will not
deliver the message.

ACTION: No action is required.


6141 /6142 Unknown error

EXPLANATION: A program error occurred.

ACTION: Call Novell Technical Support.


7001 Insufficient Memory

EXPLANATION: Your workstation has insufficient available memory to
run the program.

ACTION: Review the contents of the AUTOEXEC.BAT and CONFIG.SYS
files to determine whether there are any resident programs that can
be removed to free additional space. If you run RMHS from a shell,
exit the shell and run RMHS without the shell. Or, if your computer
is not using extended or expanded memory, you can install
additional memory. RMHS will use extended or expanded memory.


9001 RMHS.EXE was not run from the MHS\EXE directory, has an
incorrect -M parameter, or the MV variable is incorrect. Go to the
MHS\EXE directory and try again

EXPLANATION: You tried to run Remote MHS from a directory other
than the one containing the Remote MHS program files, or you did
not set the MV environment variable.

ACTION: Check to make sure you are in the correct directory. If you
are, check to make sure the MV environment variable is pointing to
the correct directory. If it is not pointing to the correct
directory, use the DOS SET command.


9002 Another Remote MHS support utility is already running.
Terminate the other program and try again. If no other Remote MHS
utility is running, delete the file MHS\MAIL\PUBLIC\\SERVER.DAT
and try again.

EXPLANATION: You tried to run two copies of RMHS at once, or another
program is running but there is not sufficient disk space for both
programs to run.

ACTION: Quit the additional program you are running and start the
RMHS program again.


9003 RMHS data files (NAMES.INF, NETDIR.TAB, NETMGR.QUE) are
corrupt or missing, or the MV variable is set incorrectly.

EXPLANATION: The MV environment variable is set incorrectly or the
Remote MHS data files are missing or corrupt.

ACTION: Ensure the MV variable is pointing to the correct
directory. If it is, confirm that the NETDIR.TAB, NAMES.INF and
NETMGR.QUE files are in the MAIL\PUBLIC directory. If they are not,
re-run RSETUP or reinstall Remote MHS.


9005 Correcting error discovered in outbound message queue

EXPLANATION: RMHS is correcting an error it discovered while trying
to process a message that was placed in the outbound message queue.

ACTION: No action is required.


9007 Could not find entry for outbound message queue in NETMGR.QUE

EXPLANATION: RMHS could not find an entry in the NETMGR.QUE file
for the server. The data file is corrupt.

ACTION: Ensure the MV variable is set correctly on the Remote MHS
workstation. If it is, run RSETUP again. If the problem persists,
reinstall Remote MHS.


9008 Attempt to open message file <filename> failed. Trying next
message

EXPLANATION: Remote MHS could see, but could not access the message
file. This error might occur if the message file does not exist,
or a disk error occurred.

ACTION: Check the MAIL directory to ensure the message file exists.
If it does exist, use the DOS CHKDSK command to check for disk
errors. If no disk errors occurred, use the DOS ATTRIB command to
ensure the file is marked read/write.


9009 Could not rename file <filename> to <filename>

EXPLANATION: Remote MHS could not rename the file as you requested.
The filename already exists, you have insufficient rights, or you
have run out of disk space.

ACTION: Check to make sure the filename does not already exist and
to make sure you have sufficient rights. If you have sufficient
rights, check to make sure you have enough disk space. Remove
unnecessary files to free additional space.


9010 Could not delete file <filename>

EXPLANATION: Remote MHS could not delete the file. The file does
not exist, or you have insufficient rights to delete this file.

ACTION: Check to make sure the file exists. If it does, check to
make sure you have sufficient rights to the file.


9012 Bad attachment detected while adding minimal submission
message to outbound queue

EXPLANATION: Remote MHS detected a corrupt file while trying to add
an SMF message into the outbound queue, or the message contains a
bad filename.

ACTION: Check to make sure you have sufficient rights to access the
file. If you do, use the DOS ATTRIB command to ensure the file is
marked read/write.


9013 File open error while adding minimal submission message to
outbound queue

EXPLANATION: A file open error occurred because Remote MHS is not
properly installed, the NETMGR.QUE file does not exist, or a disk
error occurred.

ACTION: Verify that Remote MHS is properly installed. Reinstall
Remote MHS if necessary. Check the MHS\MAIL\PUBLIC directory to see
if the NETMGR.QUE file exists. Restore NETMGR.QUE from backup if
it is missing. Use the DOS CHKDSK command to check for disk errors.


9014 Unable to open outbound queue for minimal submission message
add

EXPLANATION: Remote MHS could not open the outbound queue to add
an SMF message.

ACTION: Ensure the file MHS\MAIL\QUEUES\OUTBOUND.<nnn> exists and
use the DOS ATTRIB command to ensure that it is marked read/write.


9015 Add queue entry error while adding minimal submission message
to outbound queue

EXPLANATION: Your workstation ran out of disk space or the outbound
queue file is corrupt.

ACTION: Remove unnecessary files to free up disk space. If the
outbound queue file is corrupt, reinstall Remote MHS.


9016 Queue write error while adding minimal submission message to
outbound queue

EXPLANATION: You have run out of disk space or the outbound queue
file is corrupt.

ACTION: Remove unnecessary files to free up disk space. If the
outbound queue file is corrupt, reinstall Remote MHS.


9017 Attachment add failed while adding minimal submission message
to outbound queue

EXPLANATION: Remote MHS failed to add an attachment to the outbound
queue. Your server ran out of disk space, or the outbound queue is
corrupt.

ACTION: Remove unnecessary files to free up disk space. If the
outbound queue file is corrupt, reinstall Remote MHS.


9018 Invalid sender detected. Sender or SMF level of message does
not match data from RSETUP

EXPLANATION: Remote MHS requires that all applications support the
same SMF version and that the sender of the message matches the
configured username.

ACTION: Ensure that the SMF level specified on the Remote MHS
Configuration screen is correct and that the correct username is
being used.


9032 Error encountered during fixup of outbound message queue

EXPLANATION: The outbound queue is corrupt.

ACTION: If processing continues normally, ignore this message. If
it does not, delete the message queue and resubmit any messages
that were not delivered.


9033 SMF level <nn> does not match that of the server <nn>

EXPLANATION: Remote MHS is trying to connect with the server, but
the SMF version of your application is invalid.

ACTION: Upgrade the SMF version to allow a connection to be made.


9036 Error encountered while bursting incoming message queue

EXPLANATION: Remote MHS detected an error while trying to
decompress messages in the message queue. The user directory is
deleted or you have run out of disk space.

ACTION: Ensure the user directory exists. If it does, ensure you
have enough disk space. Remove any unnecessary files to free up
disk space.


9037 Error moving attachment <filename> to directory <path>

EXPLANATION: Remote MHS could not move the attachment file to the
directory. The directory does not exist, you have insufficient
rights to this directory, or you have run out of disk space.

ACTION: Check to make sure the directory exists. If it does, make
sure you have rights to the directory. If you have sufficient
rights, check to make sure you have enough disk space. Free up disk
space by deleting unnecessary files.


9038 Error delivering message <filename> to user <username>

EXPLANATION: Remote MHS could not deliver the message file to the
user. The user does not exist, you do not have permissions to the
MHS\MAIL\USERS\<username> directory, or you are using a filename
that already exists.

ACTION: Ensure the user exists. If the user does exist, check to
make sure you have permissions to the username directory. Make sure
the filename does not already exist.


9039 Error moving message <filename> to directory <path>

EXPLANATION: Remote MHS could not move the file to the specified
directory. You do not have sufficient rights to this directory, or
the filename already exists.

ACTION: Check to make sure you have sufficient rights to the
directory. Make sure the filename does not already exist.


9040 Proper RMHS command line syntax is: RMHS [-C"calling-card"]
[-D"dialing-prefix"] [-I"init-string"] [-LT|P] [-M"mail path"]
[-N"phone-number"] [-P+|-][-Q[2]]
[-Rconnection-retries[,minutes-between-tries]] [-S]
[-Tthreshold-in-Kb] [-V0..9] [-X] [-Y]

EXPLANATION: Remote MHS can be invoked using the command line
syntax described.

ACTION: No action is required.


9044 Error creating notification file <filename>

EXPLANATION: Remote MHS detected an error while creating a
non-delivery notification. You have run out of disk space.

ACTION: Remove unnecessary files to free up disk space and resend
your message.


9045 Cannot connect to server while modem type is DISABLED

EXPLANATION: Remote MHS could not connect to the server because the
modem type is Disabled.

ACTION: Ensure that the modem type specified on the configuration
setup screen matches the modem being used.


9046 Creating a delivery notification

EXPLANATION: RMHS is now creating a delivery notification.

ACTION: No action required. Delivery notification will be
transmitted the next time RMHS connects to the server.


9047 A delivery error forced the creation of a non-delivery
notification

EXPLANATION: An error occurred during delivery of a message and a
non-delivery notification message was generated. Likely causes for
this are:

1.	The hard disk is full or has a data corruption.

2.	Allow alternate application delivery on the incoming message was
set to No and RMHS does not have the appropriate application
installed.

ACTION: To correct the problem:

1.	Check the hard disk for sufficient free space and to ensure no
disk corruption has occurred.

2.	Install the appropriate destination application, or have the
sender allow alternate application delivery.


9049 nn seconds before next outbound call attempt

EXPLANATION: This message appears on the status line and counts
down seconds to the next call attempt.

ACTION: No action is required.


9050 Called server requested autoregistration information. Either
the information entered in RSETUP is incorrect, or you are not
defined as a remote mail user at the server you are calling.

EXPLANATION: RMHS is configured for part-time remote mode, but the
server that was called does not have you defined as a user.

ACTION: Have your server administrator configure you as a user.


9051 No telephone number, manual dial being used.

EXPLANATION: RMHS is in manual dial mode.

ACTION: No action is required. The user will be prompted to dial
the telephone number when appropriate.


9052 When first ring is heard, hit <Enter> and hang up telephone.

EXPLANATION: This message appears on the status line when a
telephone number was omitted on the Configuration/Setup screen.

ACTION: Follow these instructions when they appear.


9053 Waiting for user to place telephone call.

EXPLANATION: RMHS is waiting for the user to place a telephone
call.

ACTION: When this message appears, place the telephone call.


9054 Collecting mail from SND directory

EXPLANATION: RMHS is collecting submitted messages.

ACTION: No action is required.


9055 Cleaning up incoming message queues.

EXPLANATION: RMHS is deleting incoming queues with no valid
messages. This is a result of aborted calls that were never
resumed.

ACTION: No action is required.


9056 Unclosed quote or parameter too long.

EXPLANATION: A parameter on the command line, or in a command file
contains an unclosed quote, or was longer than 128 characters.

ACTION: Correct the error on the command line or in the command
file and run RMHS again.


9057 MV, MAIL or SW environment parameter has invalid syntax.
Remote products do not support SERVER/VOLUME: drive name or
relative paths. Your MV variable may be set to a network MHS tree
instead of your local MHS tree.

EXPLANATION: The MV environment variable is set incorrectly, using
SERVER/VOLUME: syntax instead of the drive letter syntax required
by RMHS.

ACTION: Change the MV environment variable to use a drive letter
syntax (e.g. J:\)


9058 Incoming message serial number matches RMHS's serial number.
Possible license violation detected. User USER_NAME is sharing your
license.

EXPLANATION: An incoming message from user USER_NAME shows that
he/she is using a copy of RMHS that has the same serial number as
your copy. This is a violation of the RMHS license agreement.

ACTION: Ensure that each RMHS user has their own copy of the RMHS
software.


9059 Synchronizing RMHS's outgoing messages with MHS located at
PATH.

EXPLANATION: RMHS has been invoked with the -Y (sync) option and
RMHS is about to synchronize with the MHS tree located at path PATH.

ACTION: No action is required.


9060 RMHS message synchronizing complete

EXPLANATION: RMHS -Y synchronization operation is complete.

ACTION: No action required.


9061 Network path must be set in order to synchronize (-Y) RMHS
messages. Run RSETUP, fill in the "Net MHS tree" field, and try
again.

EXPLANATION: In order to use the -Y (synchronization) option of
RMHS, the field labeled "Net MHS tree" in the RSETUP program must
be filled in.

ACTION: Fill in the "Net MHS tree" in RSETUP and try again.


9062 Network path for RMHS synchronization has invalid syntax.
Remote products don't support SERVER/VOLUME: drive naming or
relative paths. Run RSETUP, edit the "Net MHS tree" field, and try
again.

EXPLANATION: The "Net MHS tree" field in RSETUP is set incorrectly,
using SERVER/VOLUME: syntax instead of the drive letter syntax
required by RMHS.

ACTION: Change the "Net MHS tree" field to use drive letter syntax
(e.g. J:\).


9063 Cannot access network path for RMHS synchronization.Check for
correct path, verify that drive letter is already mapped, and try
again.

EXPLANATION: In order to use the -Y (synchronization) option of
RMHS, the field labeled "Net MHS tree" in the RSETUP program must
be set to a path containing an MHS tree and the drive letter must
be mapped (you must be connected to the network).

ACTION: Correct the path and/or drive mapping and try again.


9064 If you would like to continue normal processing, press "Y" and
the MHS\MAIL\PUBLIC\SERVER00.DAT file will be deleted for you,
otherwise hit any other key to exit. Note: if you continue
processing and another RMHS or support utility is running, data may
be lost or corrupted.

EXPLANATION: RMHS has detected that another copy of RMHS or RSETUP
is running by detecting the MHS\MAIL\PUBLIC\SERVER00.DAT file.
Since this can occur following a system crash, RMHS will use this
prompt to ask the user if he/she wishes to continue.

ACTION: If no other RMHS/RSETUP is running, hit "Y" and processing
will continue normally. If another copy of RMHS/RSETUP is running,
hit any other key and this copy of the program will terminate.


9065 Message FILE_NAME successfully moved to directory DIR_NAME.

EXPLANATION: The file FILE_NAME was successfully moved to the
directory DIR_NAME.

ACTION: No action is required.


9066 Synchronizing with network extract file(s).

EXPLANATION: RMHS in -Y (synchronization) mode is getting a copy
of the server extract file for use by applications when user goes
remote.

ACTION: No action is required.


9067 Synchronizing with network extract file(s) failed. Database
extract file(s) is missing or cannot be accessed.

EXPLANATION: RMHS attempt to access the network extract file
failed.

ACTION: Ensure that "Net MHS tree" parameter is set correctly and
that the appropriate drive is mapped. There are brief periods when
network database is not available for download, so if path appears
to be correct, try again.


9068 Synchronizing local and network mail submission directories.

EXPLANATION: RMHS in -Y (synchronization) mode is preparing to move
local mail messages (from submission directory) into the network
MHS tree.

ACTION: No action is required.


9069 Bursting outbound mail queue into local submission
directories.

EXPLANATION: RMHS in -Y (synchronization) mode is preparing to move
local mail messages (already queued) into the network MHS tree.

ACTION: No action is required.


9070 Delivering incoming mail.

EXPLANATION: RMHS is preparing to deliver any incoming mail
messages.

ACTION: No action is required.


9071 RMHS -Y option may not be used when RMHS is configured for
full-time remote operation. If you need to do synchronization,
reconfigure RMHS to part-time remote mode, and try again.

EXPLANATION: RMHS has been configured for full-time remote
operation, but the user has attempted to use the -Y
(synchronization) feature of RMHS. This feature is available only
when RMHS is configured for part-time remote mode.

ACTION: If you need the functionality of RMHS -Y (synchronization)
then reconfigure your RMHS to part-time remote mode and try again.


9072 RMHS.EXE was not run from the MHS\EXE directory or has an
incorrect -M parameter. When -Y option is used, MV variable is
treated as ambiguous, so go to the MHS\EXE directory (or correct
the -M parameter) and try again.

EXPLANATION: When RMHS -Y option is used, the DOS environment
parameter MV cannot be used by RMHS to locate its mail tree. RMHS
will locate it's mail tree either by examining where it was run
from, or by the -M command-line parameter. This error indicates
that RMHS could not locate it's mail tree using either of these
methods.

ACTION: Either execute RMHS from the MHS\EXE directory, or use the
-M parameter.


9073 RMHS running from MHS tree located at pathname.

EXPLANATION: RMHS has found it's subdirectory structure at the path
indicated by using either the DOS MV environment parameter, the
RMHS -M parameter, or the subdirectory from which RMHS was
executed.

ACTION: No action is required.


9077 Password verification failed.

EXPLANATION: Either your NAMES.INF file has been corrupted, or you did
not use the correct utility (RSETUP) to set your password.

ACTION: Reset your password using RSETUP -I and retry again.


9301 The directory <path> could not be created

EXPLANATION: Remote MHS could not create the directory path
specified. You have insufficient rights or your workstation ran out
of disk space.

ACTION: Check to make sure you have enough disk space. If you do
have enough disk space, make sure you have sufficient rights.


9302 Failed creating file <filename>

EXPLANATION: Remote MHS could not create the file <filename>. You
have insufficient rights to this directory, or your workstation ran
out of disk space.

ACTION: Check to ensure there is sufficient rights to the
directory. If there are, check to make sure your workstation has
not run out of disk space. Delete any unnecessary files to free
memory.


9304 Failed to write <value> at line <nn> ... for keyword <keyword
name>

EXPLANATION: Remote MHS did not recognize the value given or you
have run out of disk space.

ACTION: Check to make sure you have not run out of disk space. If
the workstation has ran out of disk space, contact Novell
representative.


9305 Failed to open file <filename>

EXPLANATION: Remote MHS could not be open the file you specified
because the file does not exist, or you have insufficient rights
to this file.

ACTION: Check to make sure you have sufficient rights to open this
file. If you do have sufficient rights to this file, check to make
sure you are spelling the name correctly.


9307 In line <nn> of <filename> ... <keyword name> is an invalid
keyword

EXPLANATION: An invalid keyword was found in the NAMES.INF file.

ACTION: Check to make sure you have enough disk space. If you do
have enough disk space, contact your Novell representative.


9308 In line <nn> of <filename> ... invalid syntax for keyword
<keyword name>

EXPLANATION: An invalid syntax for the specified keyword was used.

ACTION: Check to make sure there is enough disk space. If you do
have enough disk space, contact your Novell representative.


9309 In line <nn> of <filename>... <value> is not a valid keyword
syntax for keyword <keyword name>

EXPLANATION: An invalid keyword syntax was used on the specified
line of the specified file.

ACTION: Check to make sure you have enough disk space. If you do
have enough disk space, contact your Novell representative.


9310 RSETUP cannot run because other MHS programs are running

EXPLANATION: RMHS is currently running.

ACTION: Stop running the RMHS program.


9314 Error unzipping Remote MHS files. Installation cannot continue

EXPLANATION: An error occurred while Remote MHS was trying to
decompress the files from the install disk. You have run out of
disk space or you have insufficient rights to access these files.

ACTION: Check to make sure you have enough disk space and rights
to these files. If you do have enough disk space and access rights
to these files, contact your Novell Representative.


9320 Upgrading or Re-installing existing Remote MHS

EXPLANATION: Any time RMHS is being installed where an RMHS
directory already exists, this message appears to indicate that you
will be upgrading or re-installing.

ACTION: No action is required.
