Source: GroupWise engine; Post Office Agent.

Explanation: Error reading post office configuration information.

Possible Cause: An error was detected while reading POA configuration information from the post office database (wphost.db). The post office database might be in an inconsistent state.

Action: Start the POA with /noconfig, and validate the post office database. See Maintaining Domain and Post Office Databases in Databases in the GroupWise 8 Administration Guide.

Source: GroupWise engine; Post Office Agent.

Explanation: Invalid application name.

Possible Cause: The eDirectory distinguished name (DN) specified on the command line when starting the POA was invalid. The DN might be misspelled.

Action: Specify a valid DN. A list of valid DNs for a given post office can be obtained by failing to specify one on the POA command line (with the /name switch) when the system is configured so that one is required. You can then choose one from the list. A DN must be specified in a system that has been configured to run more than one POA process for a single post office. In that case, the DN is used by the POA to find configuration information for a specific POA process (such as TCP/IP address, port, and other configuration information).

Source: GroupWise engine; Post Office Agent.

Explanation: Ambiguous application name.

Possible Cause: An eDirectory distinguished name (DN) was not specified where one is required. Your system is configured in a way that requires the /name switch to be specified when starting the POA.

Possible Cause: This post office has been configured to run more than one POA process for it. The DN is used by the POA to identify the configuration information and options that it should use when running.

Action: The /name switch should be used in conjunction with one of the DNs specified in the error message.

Source: GroupWise engine; Post Office Agent.

Explanation: The /user and /password switches are required when the POA must log into a remote server.

Possible Cause: The POA needs to log in to a remote server where a document storage area is located, but it does not have the necessary user and password information to log in with.

Action: See Using POA Startup Switches in Post Office Agent in the GroupWise 8 Administration Guide.

Action: In ConsoleOne, specify the login information in the Remote File Server Settings box on the Post Office Settings page of the Post Office object.

Possible Cause: You have renamed the server where a document storage area is located. The POA can no longer access the original document storage area location, so the POA cannot start.

Action: First, provide the new location of the document storage area. See Moving a Document Storage Area in Libraries and Documents in the GroupWise 8 Administration Guide.

Next, start the POA using the /noconfig, /user, and /password switches so the POA can start and process the administrative message containing the new storage location without accessing the old storage location. Finally, exit, then restart the POA with its typical configuration.