11.0 Message Transfer Agent Error Messages

GWMTA: Access denied

Source: GroupWise® Message Transfer Agent; last closure reason.
Explanation: A domain or post office is closed because the MTA cannot access the database ( wpdomain.db or wphost.db ) at the location.
Possible Cause: An MTA is already running against the domain database.
Action: Do not try to run more than one MTA for a domain.

GWMTA: Admin database for domain cannot be recovered

Source: GroupWise Message Transfer Agent; admin thread.
Explanation: An attempt to recover the domain database ( wpdomain.db ) has failed.
Possible Cause: The domain database requires repair beyond what can be done while in use.
Action: Rebuild the domain database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide .

GWMTA: Administrator record not found in database

Source: GroupWise Message Transfer Agent; admin thread.
Explanation: The MTA admin thread can send a message to an administrator in case of database errors. However, no administrator has been designated.
Possible Cause: No GroupWise administrator has been set up yet.
Action: Set up a GroupWise administrator to receive messages about database errors. See Notifying the Domain Administrator in Message Transfer Agent in the GroupWise 7 Administration Guide .
Action: Use the /noerrormail switch when starting the MTA to turn off administrator messages.

GWMTA: Authentication failure for the above object

Source: GroupWise Message Transfer Agent; admin thread.
Explanation: The MTA admin thread attempted to process a record that has the wrong authentication key for the current GroupWise system.
Possible Cause: The record did not originate in the current GroupWise system, which is a possible security violation.
Action: Someone is trying to tamper with your GroupWise system. Check your system security measures.

GWMTA: Cannot attach to server or volume

Source: GroupWise Message Transfer Agent; last closure reason.
Explanation: A domain or post office is closed because the NetWare® MTA cannot access the server or volume where the domain or post office is located.
Possible Cause: The domain or post office is located on a different server from where the MTA is running and the MTA has not been configured with user information to enable it to log in.
Action: Make sure the MTA startup file includes the /user and /password, or /dn switches, so the MTA can log into the remote server. Make sure the user and password information is correct and current. Make sure the information is formatted correctly. In some configurations, you might need to specify a distinguished name (for example, user. org_unit. org) for the /user switch, rather than just a simply user ID. In some configurations, you might need to include the type (for example, .CN= user. org_unit. org).
Action: If the MTA still cannot log in to the remote server after appropriate user information has been supplied, start the MTA with /tracelogin-2 to display NetWare error codes. Look up the error codes at Novell Error Codes.
Possible Cause: The NetWare MTA cannot log into the server where a domain or post office is located because all available NetWare licenses are already in use.
Action: Increase the number of licenses on the server.

GWMTA: Cannot create a new receiver thread

Source: GroupWise Message Transfer Agent; message transfer protocol.
Explanation: The MTA cannot create a new receiver thread.
Possible Cause: Insufficient memory.
Action: See GWMTA: Insufficient memory.

GWMTA: Cannot create/read/write files/directories

Source: GroupWise Message Transfer Agent; last closure reason.
Explanation: A domain or post office is closed because the MTA cannot write files into its output queue in the closed domain or post office.
Possible Cause: The user specified with the /user switch in the MTA startup file does not have sufficient rights to create files in the domain or post office directory.
Action: Make sure the user the MTA is logging in as has sufficient rights in the domain or post office directory. See Creating a NetWare Account for Agent Access (Optional) in Installing GroupWise Agents in the GroupWise 7 Installation Guide .
Possible Cause: The MTA cannot write message files across a mapped or UNC link into the MTA input queue in a closed domain ( domain\wpcsin directory) or a closed post office ( post_office\wpcsout directory) because the 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 /home switch.
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 Using MTA Startup Switches in Message Transfer Agent in the GroupWise 7 Administration Guide .

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 MTA in Message Transfer Agent in the GroupWise 7 Administration Guide .
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.

GWMTA: Cannot move files

Source: GroupWise Message Transfer Agent; last closure reason.
Explanation: The MTA cannot move message files from its input queue ( domain\wpcsin or post_office\wpcsin ) to its in progress" queue ( gwinprog ).
Explanation: Insufficient disk space on the server where the mslocal directory structure is located.
Action: Free up disk space so the MTA has sufficient space to process message files.

GWMTA: Cannot proceed; incompatible GWENN5.NLM

Source: NetWare GroupWise Message Transfer Agent.
Explanation: The MTA cannot start because the agent engine ( gwenn5.nlm ) is not compatible with the MTA itself ( gwmta.nlm ).
Possible Cause: Some agent files have been updated but the update is not complete.
Action: When updating the agents, make sure all agent files are installed. For a complete list of files, see Agent Installation Directories in GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure .
Possible Cause: The agent engine ( gwenn5.nlm) was not unloaded prior to updating the agent software. The agent software cannot be successfully updated if the agent engine is still loaded.
Action: After exiting all the agents, unload the gwenn5.nlm, then perform the update. See the Updating Secondary Domains in Updating Your GroupWise 6.x System to Version 7 in the GroupWise 7 Installation Guide .

GWMTA: Cannot proceed; insufficient memory available

Source: GroupWise Message Transfer Agent.
Action: See GWMTA: Insufficient memory.

GWMTA: Cannot read domain database; insufficient memory

Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot access its domain database ( wpdomain.db ).
Possible Cause: Insufficient memory.
Action: See GWMTA: Insufficient memory.
Possible Cause: The domain database has been damaged.
Action: Rebuild the domain database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide .

GWMTA: Cannot read post office database; insufficient memory

Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot access the post office database ( wphost.db ).
Possible Cause: Insufficient memory.
Action: See GWMTA: Insufficient memory.
Possible Cause: The post office database has been damaged.
Action: Rebuild the post office database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide .

GWMTA: Cannot route message(s); out of memory

Source: GroupWise Message Transfer Agent.
Action: See GWMTA: Insufficient memory.

GWMTA: Cannot start server; insufficient memory available

Source: GroupWise Message Transfer Agent.
Action: See GWMTA: Insufficient memory.

GWMTA: Closed for inbound traffic

Source: GroupWise Message Transfer Agent.
Explanation: The MTA is not accepting inbound connections on its TCP/IP link.
Possible Cause: The MTA has been manually suspended.
Action: Resume the MTA for the domain. See Suspending/Resuming MTA Processing for a Location in Message Transfer Agent in the GroupWise 7 Administration Guide .
Possible Cause: If you are running multiple MTAs on the same server, the same TCP port might be in use by more than one MTA.

NetWare Note: On a NetWare server, you would see the message "Waiting for busy listen socket to become available."

Action: Check the setup of the MTAs. Make sure each MTA is using a unique port. See Configuring the MTA for TCP/IP in Message Transfer Agent in the GroupWise 7 Administration Guide .

GWMTA: Command line parameter /home is required

Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot start without a /home switch specifying the domain directory.
Possible Cause: The /home switch has not been provided in the command to start the MTA.
Action: Add the /home switch to the command to start the MTA. See Using MTA Startup Switches in Message Transfer Agent in the GroupWise 7 Administration Guide .
Possible Cause: The agent was not able to access the startup file where the /home switch was specified.
Action: Make sure the startup file exists.

GWMTA: Could not launch the editor

Source: GroupWise Message Transfer Agent for Windows.
Explanation: The MTA cannot run the program used to view agent log files or edit agent startup files.
Possible Cause: The viewer program is not available on the current path or is incorrectly specified.
Action: The default viewer used by the agents is Notepad, which is typically available. You can change the viewer specification by selecting View Log Files in the agent window and changing the information in the Viewer field. Check the viewer and path specified in the View Log Files dialog box in the agent window.

GWMTA: Database language has been updated; please rebuild this database

Source: GroupWise Message Transfer Agent; admin thread.
Explanation: The database needs to be rebuilt because the language has been changed, which changes the sort order of the users listed in the database.
Action: Rebuild the database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide .

GWMTA: Disk full; disk logging turned off

Source: GroupWise Message Transfer Agent.
Explanation: Logging information to disk has been turned off because there is insufficient disk space to continue writing to the agent log file.
Action: Free up disk space. The agent should resume disk logging after disk space is available. To ensure that disk logging has resumed, check the Logging Level setting in the Log Settings page for the MTA in ConsoleOne. See Using MTA Log Files in Message Transfer Agent in the GroupWise 7 Administration Guide .
Action: Specify a different location for log files where sufficient disk space is available.

GWMTA: Domain database error; circular transfer domain link

Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot route a message to the domain it is addressed to because available indirect links create a circular reference.
Possible Cause: Links between domains in your GroupWise system are not set up correctly.
Action: Check, and if necessary, adjust the indirect links between domains in your GroupWise system. See Editing a Domain Link in Domains in the GroupWise 7 Administration Guide .

GWMTA: Domain database error; transfer domain not found

Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot locate the domain to which a message is addressed, nor can it locate an indirect link to that domain.
Possible Cause: Links between domains in your GroupWise system are not set up correctly.
Action: Check, and if necessary adjust, the indirect links between domains in your GroupWise system. See Link Configuration between Domains and Post Offices in Domains in the GroupWise 7 Administration Guide .

GWMTA: Domain database open failed

Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot access the domain database ( wpdomain.db ).
Possible Cause: The domain database has been damaged.
Action: Rebuild the domain database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide .

GWMTA: Domain database read error

Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot access its domain database ( wpdomain.db ).
Possible Cause: The domain database has been damaged.
Action: Rebuild the domain database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide .

GWMTA: Domain now closed

Source: GroupWise Message Transfer Agent.
Explanation: The MTA has lost its connection to a domain with which it could previously communicate.
Possible Cause: The server where the domain is located is currently down.
Action: Wait for the server to come back up, or contact the administrator of that server.
Possible Cause: If using TCP/IP communication between domains, TCP/IP might be down.
Action: Make sure TCP/IP is running in both domains.

GWMTA: Domain open failed

Source: GroupWise Message Transfer Agent.
Explanation: The MTA in the local domain cannot contact the MTA in a different domain in your GroupWise system.
Possible Cause: Links between the domains are not set up correctly.
Action: Check the links between the domains. See Editing a Domain Link in Domains in the GroupWise 7 Administration Guide .
Possible Cause: The local MTA cannot access the MTA input queue in the other domain.
Action: Check the directory structure of the closed domain. See Domain Directory in Directory Structure Diagrams in GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure .

GWMTA: Error initializing HTTP

Source: GroupWise Message Transfer Agent.
Explanation: The HTTP port the MTA is trying to use for its Web console is not responding correctly.
Action: Configure the MTA to communicate on a different HTTP port. See Using the MTA Web Console in Message Transfer Agent in the GroupWise 7 Administration Guide .

GWMTA: Error validating post office members

Source: GroupWise Message Transfer Agent, Novell® eDirectory™ user synchronization.
Explanation: When attempting eDirectory user synchronization, the MTA could not access the user information stored in eDirectory.
Action: Look up the NetWare error code that accompanies this error at Novell Error Codes.
Possible Cause: The MTA does not have sufficient rights to access the user information in eDirectory.
Action: Make sure the MTA is properly set up to perform eDirectory user synchronization. See Using eDirectory User Synchronization in Message Transfer Agent in the GroupWise 7 Administration Guide .

GWMTA: Expired en route to destination

Source: GroupWise Message Transfer Agent.
Explanation: The MTA was unable to deliver a message because it passed through the maximum of 15 hops without reaching its destination.
Possible Cause: Links between domains are not set up correctly.
Action: Check the links between domains. Look for a more efficient route. See Link Configuration between Domains and Post Offices in Domains in the GroupWise 7 Administration Guide .

GWMTA: File create error; disk logging turned off

Source: GroupWise Message Transfer Agent.
Explanation: Logging information to disk has been turned off because the MTA cannot create a new log file.
Possible Cause: The agent cannot create a file in the location specified by the Log File Path setting on the Log Settings page for the agent in ConsoleOne or specified on the command line using the /log startup switch. See Using MTA Log Files in Message Transfer Agent in the GroupWise 7 Administration Guide .
Action: Make sure the location exists or specify another location.
Action: Make sure the agent has rights to create files in the specified location.
Action: Make sure there is available disk space in the specified location.

GWMTA: File write error; disk logging turned off

Source: GroupWise agents.
Explanation: Logging information to disk has been turned off because the agent can no longer write to the current log file.
Possible Cause: If the log file is located on a server other than the one where the agent is running, that server might be down.
Action: Wait for the server to come back up, or contact the administrator of that server. When the server comes back up, the agent will resume disk logging.
Possible Cause: The log file has been damaged so the agent can no longer write to it.
Action: Remove the damaged log file and turn disk logging back on in the Log Settings page for the agent in ConsoleOne. See Using MTA Log Files in Message Transfer Agent in the GroupWise 7 Administration Guide . The agent will create a new log file.

You can also use Cycle Log from the MTA agent console to start a new log file. See Cycling the MTA Log File in Message Transfer Agent in the GroupWise 7 Administration Guide .

GWMTA: File not found

Source: GroupWise Message Transfer Agent; agent console
Explanation: From the MTA agent console, you are trying to edit or view either the MTA log file or startup file and the MTA cannot access it.
Action: Verify the existence and rights to the file.

GWMTA: Gateway now closed

Source: GroupWise Message Transfer Agent.
Explanation: The MTA has lost its connection to a gateway with which it could previously communicate
Possible Cause: The server where the gateway is located is currently down.
Action: Wait for the server to come back up, or contact the administrator of that server.

GWMTA: Gateway open failed

Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot contact a gateway to which a message needs to be routed.
Possible Cause: The MTA cannot access the gateway input queue under the wpgate directory of the domain.
Action: Check the directory structure of the closed Internet gateway.

GWMTA: Host refused connection

Source: GroupWise Message Transfer Agent.
Explanation: The MTA is configured to communicate with another MTA or a POA by way of TCP/IP. The server where the other MTA or the POA is located has refused the MTA’s request for a connection.
Action: Check the TCP/IP configuration of the server to which the MTA must connect.

GWMTA: IDomain now closed

Source: GroupWise Message Transfer Agent.
Explanation: The MTA has lost its connection to a domain across the Internet with which it could previously communicate.
Possible Cause: The server where the domain is located is currently down.
Action: Wait for the server to come back up, or contact the administrator of that server.
Action: Make sure the Internet link between domains is set up correctly. See Internet Agent in the GroupWise 7 Administration Guide .

GWMTA: Incompatible GWENV1A.DLL; GWMTA cannot continue

Source: GroupWise Message Transfer Agent for Windows.
Explanation: The MTA cannot start because the agent engine ( gwenv1a.exe ) is not compatible with the MTA itself ( gwmta.exe ).
Possible Cause: Some agent files have been updated but the update is not complete.
Action: When updating the agents, make sure all agent files are installed. For a complete list, see Agent Installation Directories in GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure .

GWMTA: Insufficient disk space

Source: GroupWise Message Transfer Agent.
Explanation: The MTA does not have sufficient disk space to write files into its input queues or holding queues. The MTA requires at least 1 MB of free disk space to run.
Possible Cause: One or more locations are closed, resulting in a backlog of messages in the MTA holding queues in the directory.
Action: Resolve the problems with the closed facilities so that normal message flow resumes. See MTA Status Box Shows a Closed Location in GroupWise 7 Troubleshooting 2: Solutions to Common Problems .
Possible Cause: Other programs running the same server with the MTA have used up all available disk space.
Action: Free up disk space so the MTA can continue processing messages. Check the MTA log file to see which queue the MTA can no longer write to so you know where more disk space is required. See Using MTA Log Files in Message Transfer Agent in the GroupWise 7 Administration Guide .
Possible Cause: The MTA cannot write message files across a mapped or UNC link into the MTA input queue in a closed domain ( domain\wpcsin directory) or a closed post office ( post_office\wpcsin directory) because the directory is damaged.
Action: If the input queue subdirectories are empty, you can rename the original input queue directory and then manually re-create it, along with its required subdirectories.

GWMTA: Insufficient memory

Source: GroupWise Message Transfer Agent.
Explanation: Not enough memory is available for the MTA to function properly.
Possible Cause: If the MTA cannot start, you might be trying to run the MTA in an environment where too few system resources are available.
Action: For requirements, see GroupWise System Requirements in Installing GroupWise Agents in the GroupWise 7 Installation Guide .
Action: Stop some other programs on the server to free up memory for use by the MTA.
Action: Add memory to the server to accommodate the MTA along with other existing programs.
Action: Select a different server to run the MTA on, where adequate resources are available. See Moving the MTA to a Different Server in Message Transfer Agent in the GroupWise 7 Administration Guide .
Possible Cause: If the MTA starts successfully, then encounters a memory error later during otherwise normal processing, some other program on the server, or another agent thread, might have temporarily used a large quantity of memory.
Action: Wait to see if the memory problem resolves itself. The MTA will retry its operation and should succeed at a later time, when the other program has released some memory.
Action: If the MTA starts successfully but frequently encounters memory errors during later processing, treat the situation as if the MTA cannot start and see the recommended actions above.

GWMTA: Insufficient memory to read/process startup file

Source: GroupWise Message Transfer Agent.
Possible Cause: Insufficient memory.
Action: See GWMTA: Insufficient memory.

GWMTA: Insufficient resources to accept inbound connection

Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot start a receiver thread.
Possible Cause: Insufficient memory.
Action: If the problem does not resolve itself in a short time, see GWMTA: Insufficient memory.

GWMTA: Insufficient system resources

Source: GroupWise Message Transfer Agent.
Explanation: The MTA was unable to start another thread.
Possible Cause: Insufficient memory.
Action: If the problem does not resolve itself in a short time, see GWMTA: Insufficient memory.

GWMTA: Internet mail to address is undeliverable because no default GWIA is configured

Source: GroupWise Message Transfer Agent.
Explanation: A message addressed to a user across the Internet cannot be delivered.
Possible Cause: A default GroupWise Internet Agent has not been configured.
Action: Designate a default Internet Agent. See Configuring Internet Addressing in System in the GroupWise 7 Administration Guide .

GWMTA: Invalid /log parameter

Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot use the location specified by the /log startup switch to store its log files.
Possible Cause: The location specified by the /log startup switch does not exist.
Action: Check, and if necessary change, the location specified by the /log startup switch when starting the MTA. If the /log switch is not specified, it defaults to the mslocal directory in the directory specified by the /work switch.
Possible Cause: The location specified by the /log startup switch is on a server that is currently not available.
Action: Check the status of the server where the specified directory is located. Wait for the server to come back up or contact the administrator of that server.
Action: It is recommended that the /log switch be set to a location local to where the MTA is running to avoid this problem.

GWMTA: Invalid /work parameter

Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot use the location specified by the /work startup switch for its mslocal directory.
Possible Cause: The location specified by the /work startup switch does not exist.
Action: Check, and if necessary change, the location specified by the /work startup switch when starting the MTA. If the /work switch is not specified, it defaults to the domain directory. See Using MTA Startup Switches in Message Transfer Agent in the GroupWise 7 Administration Guide .
Possible Cause: The location specified by the /work startup switch is on a server that is currently not available.
Action: Check the status of the server where the specified directory is located. Wait for the server to come back up or contact the administrator of that server.
Action: It is recommended that the /work switch be set to a location local to where the MTA is running to avoid this problem.

GWMTA: Link or transport down

Source: GroupWise Message Transfer Agent.
Explanation: The MTA is using TCP/IP to communicate with an MTA or POA and the other agent is not responding.
Possible Cause: The MTA in the other domain is not properly set up for TCP/IP communication.
Action: Check the setup of the MTA in the other domain. See Using TCP/IP Links between Domains in Message Transfer Agent in the GroupWise 7 Administration Guide .
Possible Cause: The POA in the post office is not properly set up for TCP/IP communication.
Action: Check the setup of the POA. See Using TCP/IP Links between a Domain and its Post Offices in Message Transfer Agent in the GroupWise 7 Administration Guide .

GWMTA: Logging permanently suspended; insufficient memory

Source: GroupWise Message Transfer Agent.
Explanation: The MTA could not start a new thread for disk logging. Therefore, disk logging has been turned off.
Possible Cause: Insufficient memory.
Action: See GWMTA: Insufficient memory.
Action: After sufficient memory is available, turn disk logging back on in the Log Settings page for the agent in ConsoleOne. See Using MTA Log Files in Message Transfer Agent in the GroupWise 7 Administration Guide .

GWMTA: Login not completed; timeout

Source: GroupWise Message Transfer Agent; message transfer protocol.
Explanation: An MTA or POA started to request TCP/IP communication from the MTA, but stopped responding in the middle of the login process.
Possible Cause: The server where the other agent was running went down.
Action: Check the status of the other server. Reboot if necessary.

GWMTA: Login to directory failed

Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot communicate with another domain or post office because it cannot access the server where the domain or post office is located.
Possible Cause: The /user and /password switches do not provide the correct information for the MTA to log in to the server.
Action: Check the settings for the /user and /password switches in the command that starts the MTA. Make sure you can log in to the server using the user name and password the MTA is trying to use.
Possible Cause: The server where the domain or post office is located is currently down.
Action: Wait for the server to come back up or contact the administrator of that server.
Action: See also GWMTA: Cannot attach to server or volume.

GWMTA: Maximum number of inbound connections reached

Source: GroupWise Message Transfer Agent.
Explanation: The MTA could not start another thread for an inbound connection.
Possible Cause: The maximum number of inbound connections as specified by the /tcpinbound startup switch has been reached. The default is 40 inbound connections.
Action: Increase the setting of the /tcpinbound switch to allow for more inbound connections. There is no maximum number of inbound connections. They are limited only by available system resources. See Adjusting the Number of MTA TCP/IP Connections in Message Transfer Agent in the GroupWise 7 Administration Guide .

GWMTA: No agent record found

Source: GroupWise Message Transfer Agent.
Explanation: The MTA object in the eDirectory tree is missing.
Possible Cause: When a domain is created, an MTA object is automatically created for it. It might have been deleted.
Action: Check for the MTA object in the domain. Make sure it is configured correctly. See Configuring the MTA in ConsoleOne in Message Transfer Agent in the GroupWise 7 Administration Guide .
Possible Cause: The domain database ( wpdomain.db ) is damaged.
Action: Check and, if necessary, repair the domain database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide .

GWMTA: No domain record found

Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot find the domain record in the domain database ( wpdomain.db ).
Possible Cause: The domain database is damaged.
Action: Rebuild the domain database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide .

GWMTA: No path configured

Source: GroupWise Message Transfer Agent.
Explanation: Path information for links between domains is missing.
Possible Cause: Links between domains are not set up correctly.
Action: Check the links between domain. See Editing a Domain Link in Domains in the GroupWise 7 Administration Guide .

GWMTA: No post offices found

Source: GroupWise Message Transfer Agent; eDirectory user synchronization.
Explanation: The MTA has been configured to perform eDirectory user synchronization for a domain which has no post offices and, hence, no users; for example, a routing domain.
Action: Remove the domain from the list of domains for which eDirectory user synchronization should be performed. See Using eDirectory User Synchronization in Message Transfer Agent in the GroupWise 7 Administration Guide .

GWMTA: No response from peer

Source: GroupWise Message Transfer Agent; message transfer protocol.
Explanation: The MTA is attempting to communicate with another MTA or a POA by way of TCP/IP, but the other agent does not answer.
Possible Cause: The server where the other MTA or the POA is located is down.
Action: Check the status of the other server. Reboot if necessary.

GWMTA: No sender IDomain; Internet address lookup not attempted

Source: GroupWise Message Transfer Agent.
Explanation: The address the MTA is trying to resolve does not contain IDomain information.
Possible Cause: The MTA is configured for GWMTP between GroupWise systems, but the link is not set up properly.
Action: Correct any problems in the setup of links between the two systems. See Using Dynamic Internet Links in Connecting to GroupWise 5.x, 6.x, and 7.x Systems in the GroupWise 7 Multi-System Administration Guide .
Action: If the message is destined for a non-GroupWise system across the Internet, it will be routed through the GroupWise Internet Agent. No action is required, provided a preferred Internet Agent has been designated. See Configuring Internet Addressing in System in the GroupWise 7 Administration Guide .

GWMTA: Path to domain database (/home) is invalid or blocked

Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot access the domain database ( wpdomain.db ) in the directory specified by the /home switch.
Possible Cause: The location specified by the /home startup switch does not exist.
Action: Check, and if necessary change, the location specified by the /home startup switch when starting the MTA. It must specify the domain directory. See Using MTA Startup Switches in Message Transfer Agent in the GroupWise 7 Administration Guide .
Possible Cause: The location specified by the /home startup switch is on a server that is currently not available.
Action: Check the status of the server where the specified directory is located. Wait for the server to come back up or contact the administrator of that server.
Possible Cause: If running the MTA on a Windows server, the location might be on a server that is not currently mapped.
Action: Make sure the server where the MTA is running has a drive mapped to the domain directory on the server where the domain is located if it is using a mapped link.
Action: See GWMTA: Cannot attach to server or volume.

GWMTA: Post office database open failed; insufficient memory

Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot access one of its post office databases ( wphost.db ).
Possible Cause: Insufficient memory.
Action: See GWMTA: Insufficient memory.
Possible Cause: The post office database has been damaged.
Action: Rebuild the post office database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide .

GWMTA: Post office database read error

Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot access the post office database ( wphost.db ).
Possible Cause: The post office database has been damaged.
Action: Rebuild the post office database. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 7 Administration Guide .

GWMTA: Post office now closed

Source: GroupWise Message Transfer Agent.
Explanation: The MTA has lost its connection to a post office with which is could previously communicate.
Possible Cause: The server where the post office is located is currently down.
Action: Wait for the server to come back up, or contact the administrator of that server.
Possible Cause: If using TCP/IP communication between post offices, TCP/IP might be down.
Action: Make sure TCP/IP is running on the servers where the post offices are located.

GWMTA: Post office open failed

Source: GroupWise Message Transfer Agent.
Explanation: The MTA cannot contact the POA in one of the local post offices.
Possible Cause: The MTA cannot access the POA input queue in the post office.
Action: Check the directory structure of the closed post office. See Post Office Directory in GroupWise 7 Troubleshooting 3: Message Flow and Directory Structure .

GWMTA: Received unsupported request; request ignored

Source: GroupWise Message Transfer Agent.
Explanation: The MTA received an administrative message from GroupWise Administrator that it could not respond to.
Possible Cause: GroupWise Administrator has been updated, but the GroupWise agent software has not yet been updated.
Action: Install the latest version of the GroupWise agent software. See the Installing the GroupWise 7 Software in Update in the GroupWise 7 Installation Guide .

GWMTA: Running the agent with conflicting effective users

Source: GroupWise Message Transfer Agent for Linux.
Explanation: You are starting the MTA as a user that is different from the user the MTA is configured to run as. The user specified in the uid.conf file does not match the user specified in the uid.run file.
Possible Cause: The user specified in the uid.conf file has been manually edited.
Possible Cause: The uid.conf file has been deleted.
Action: Verify that the uid.conf file specifies the desired user, then delete the uid.run file. For more information, see Running the Linux GroupWise Agents as a Non-root User in Installing GroupWise Agents in the GroupWise 7 Installation Guide .

GWMTA: StartServiceCtrlDispatcher failed when attempting to start Windows_agent service

Source: GroupWise Message Transfer Agent for Windows.
Explanation: The Windows MTA cannot start its dispatcher thread.
Possible Cause: The Windows server is not functioning properly.
Action: Reboot the Windows server.

GWMTA: Target queue temporarily locked

Source: GroupWise Message Transfer Agent.
Explanation: The MTA is in the process of clearing out a backlog of messages and is not accepting any additional messages into its queues. The MTA processes existing messages first, before processing new messages, so that messages arrive in the order in which they were sent.
Possible Cause: The backlog of messages might have been caused by one or more closed facilities in the domain.
Action: Wait until the backlog clears, then the MTA will resume its regular processing of new messages. Backlogged messages are stored in subdirectories of the mslocal directory.

GWMTA: The Windows_agent service fails to set service status; service stopped

Source: GroupWise Message Transfer Agent for Windows.
Explanation: The Windows MTA cannot start as a Windows service.
Possible Cause: The Windows MTA cannot communicate with the Windows service control manager (SCM).
Action: Reboot the Windows server.

GWMTA: The Windows_agent service fails to initialize memory system; service stopped

Source: GroupWise Message Transfer Agent for Windows.
Explanation: The Windows MTA cannot start as a Windows service.
Possible Cause: The Windows server has insufficient memory resources available.
Action: Reboot the Windows server. Run fewer programs on the Windows server.

GWMTA: Timed out waiting for end-of-file confirmation

Source: GroupWise Message Transfer Agent.
Explanation: The MTA is in the process of clearing out a backlog of messages and is not accepting any additional messages into its queues. The MTA processes existing messages first, before processing new messages, so that messages arrive in the order in which they were sent.
Possible Cause: The backlog of messages might have been caused by one or more closed facilities in the domain.
Action: Wait until the backlog clears, then the MTA will resume its regular processing of new messages. Backlogged messages are stored in subdirectories of the mslocal directory.

GWMTA: Unable to initialize message log database

Source: GroupWise Message Transfer Agent; message transfer protocol.
Explanation: The MTA was unable to create the database where it stores information about messages waiting for processing in its in progress ( gwinprog ) queue. the msglog subdirectory of mslocal cannot be created.
Possible Cause: Insufficient disk space.
Action: Free up disk space on the server where the MTA runs.

GWMTA: Unable to open connection; no response

Source: GroupWise Message Transfer Agent; message transfer protocol.
Explanation: The MTA is attempting to communicate with another MTA or a POA by way of TCP/IP, but the other agent does not answer.
Possible Cause: The server where the other MTA or the POA is located is down.
Action: Check the status of the other server. Reboot if necessary.

GWMTA: Unable to register with SNMP agent

Source: GroupWise agents.
Explanation: The MTA is unable to contact the SNMP agent on the server where the agent is running.
Possible Cause: SNMP has not been installed and set up properly on the server.
Action: Install SNMP as required by the server operating system.

GWMTA: Unable to retrieve TCP/IP address

Source: GroupWise Message Transfer Agent.
Explanation: The MTA is configured for GWMTP between GroupWise systems, but the MTA cannot find the IDomain name of the destination system
Possible Cause: GWMTP is not properly set up between the two GroupWise systems.
Action: Correct any problems in the setup of links between the two systems. See Using Dynamic Internet Links in Connecting to GroupWise 5.x, 6.x, and 7.x Systems in the GroupWise 7 Multi-System Administration Guide .

GWMTA: Undefined link

Source: GroupWise Message Transfer Agent; last closure reason.
Explanation: MTAs cannot communicate because no link has been established between them.
Action: Configure a link between the MTAs. See Changing the Link Protocol between Domains in Configuring the MTA in the GroupWise 7 Administration Guide .

GWMTA: Unknown connection header received

Source: GroupWise Message Transfer Agent; message transfer protocol.
Explanation: The MTA received a request for a TCP/IP connection from a process other than a GroupWise agent.
Possible Cause: Some non-GroupWise program on the server where the MTA is running is configured to send packets to the port the MTA is configured to listen on.
Action: Check the network address information of the MTA. See Configuring the MTA for TCP/IP in Configuring the MTA in the GroupWise 7 Administration Guide . Make sure no other programs on the server besides GroupWise agents are configured to use this port.

GWMTA: Unknown destination

Source: GroupWise Message Transfer Agent.
Explanation: The MTA is unable to route a message because it does not recognize the domain to which it is addressed.
Possible Cause: The sender manually typed in an invalid address.
Action: Have the user select the recipient from the Address Book, then resend the message.
Possible Cause: During a reconfiguration of your system, a user has addressed a message to a location that either no longer exists or does not exist yet, because the reconfiguration information has not yet replicated throughout the GroupWise system.
Action: Wait until replication is complete. The MTA will retry the operation.
Possible Cause: The message has been damaged so that the destination information is no longer readable.
Action: Remove the damaged message from the MTA input queue so it can process subsequent messages. Have the user resend the message.

GWMTA: Waiting for busy listen socket to become available

Source: GroupWise Message Transfer Agent; message transfer protocol.
Explanation: The TCP port the MTA is configured to listen on is already in use by another program.
Possible Cause: Another MTA is already running on the server where you are trying to start this MTA.
Action: Configure this MTA to use a different TCP port. See Using TCP/IP Links between Domains in Configuring the MTA in the GroupWise 7 Administration Guide .