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.
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.
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.