Novell GROUPWISE 7 - TROUBLESHOOTING 1 Troubleshooting Manual page 201

Possible Cause: The MTA cannot write message files across a mapped or UNC link into the
MTA input queue in a closed domain
closed post office
directory is inaccessible or damaged.
Action: Make sure the input queue directory exists and that the MTA has sufficient
rights to create files there. If necessary, and if the input queue subdirectories
are empty, you can rename the original input queue directory and then
manually recreate it, along with its required subdirectories.
Possible Cause: The server where the closed domain or post office is located does not have
sufficient disk space for the MTA to create message files.
Action: Free up disk space.
NetWare Note: On a NetWare server, you might need to purge deleted files to
free up disk space.
Possible Cause: The name of the domain directory contains more than 8 characters.
Action: Rename the domain directory. The MTA currently does not support long
names. Also update the domain directory path in ConsoleOne
Possible Cause: The network type specified for the domain is incorrect.
Action: Check the network type selected for the domain. In ConsoleOne, right-click
the Domain object, then click Properties. Make sure the Network Type field is
correct for the MTA running for the domain.
GWMTA: Cannot find domain database
Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot access a domain database (wpdomain.db) in the directory
specified by the
Possible Cause: The MTA has been able to access the directory specified by the /home switch,
but it cannot locate a valid domain database in that directory.
Action: Make sure the location provided by the /home startup switch specifies a valid
domain directory. See
Agent" in the
GWMTA: Cannot find startup file
Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot start because it cannot locate or read its startup file.
Possible Cause: The name of the startup file as provided in the command to start the MTA is
incorrect.
Action: Make sure you are providing the name of the startup file correctly. See
"Installing and Starting the
GroupWise 7 Administration
Possible Cause: The startup file is not located on the current path.
Action: Specify the full path to the startup file in the command to start the MTA.
(domain\wpcsin
(post_office\wpcsout
/home switch.
"Using MTA Startup
GroupWise 7 Administration
MTA" in "Message Transfer
Guide.
directory) or a
directory) because the
®
.
Switches" in "Message Transfer
Guide.
Agent" in the
Message Transfer Agent Error Messages 201