5.0 Bxxx Engine Error Codes

NOTE:This guide does not include a comprehensive list of all possible GroupWise error codes. It lists error codes for which solutions are readily available from GroupWise engineers and testers. You can search the Novell Support Knowledgebase to locate additional solutions documented by Novell Support as specific customer issues have been resolved.

B300 File transmission failed

Source: GroupWise engine; Message Transfer Protocol.
Explanation: The POA was not able to transfer a message file to the MTA.
Possible Cause: The MTA restarted during transmission of the file.
Possible Cause: The network experienced a slow-down, causing the MTA to time out while waiting for the rest of the file.
Action: None. The POA automatically resends the message until the message is sent successfully.

B309 Port already in use

Source: GroupWise engine; Message Transfer Protocol.
Explanation: The specified port is already in use.
Possible Cause: You have set up the POA to communicate with the MTA by way of TCP/IP but the TCP port you have chosen for the Message Transfer Protocol (MTP) link between them is already in use by another program.
Action: The message transfer port configured for the POA should be the same port number as the MTA is using to listen on. Make sure the MTA is set up correctly for TCP/IP links. Make sure the POA is configured with the message transfer port number matching the port number of the MTA. See Changing the Link Protocol between the Post Office and the Domain in Post Office Agent in the GroupWise 2012 Administration Guide.

B30A No peer listening for connection

Source: GroupWise engine; Message Transfer Protocol.
Explanation: The POA is attempting to communicate with the MTA by way of TCP/IP but the MTA is not responding.
Possible Cause: The MTA is not running.
Action: Start the MTA.
Possible Cause: The server where the MTA is running is overloaded so the MTA cannot respond to the POA in a timely manner.
Action: Check the load on the server where the MTA is running. If necessary, stop some other programs or upgrade the server so adequate resources are available for the MTA to function properly.
Possible Cause: The MTA is not configured for TCP/IP links.
Action: Reconfigure the MTA for TCP/IP links. See Changing the Link Protocol between Domains in Message Transfer Agent in the GroupWise 2012 Administration Guide.