Source: GroupWise engine; general communication.
Explanation: Port in use.
Possible Cause: The POA defaults to TCP/IP communication, but the necessary TCP/IP information is not configured in ConsoleOne. The default TCP port used by the POA (1667) is in use by another program.
Action: To enable TCP/IP communication, configure the POA for ConsoleOne. See "Using Client/Server Access to the Post Office" in "Configuring the POA" in the GroupWise 6.5 Administration Guide.
Action: To disable TCP/IP communication, use the /notcpip switch when starting the POA. See "Using POA Startup Switches" in "Post Office Agent" in the GroupWise 6.5 Administration Guide.
Possible Cause: You are trying to run two POAs on the same server in client/server mode and you have not given them unique TCP port numbers.
Action: Check the TCP port for each POA object. See "Using Client/Server Access to the Post Office" in "Configuring the POA" in the GroupWise 6.5 Administration Guide. Change the TCP port for one of the POAs.
Possible Cause: You are trying to run two POAs on the same server in client/server mode and you haven't created a second POA object in ConsoleOne.
Action: In ConsoleOne, create a second POA object in the post office. Make sure you give it a unique TCP port number, different from what the first POA is using. Use the /name switch when starting each POA. You might want to create a separate startup file for each POA. See "Creating a POA Object in eDirectory" in "Post Office Agent" in the GroupWise 6.5 Administration Guide.