Problem: The POA does not start.
Possible Cause: The /home switch is missing.
Action: Make sure the /home startup switch provides the correct path to the post office directory where the post office database (wphost.db) resides. This switch is required to start the POA and must be provided either in the POA startup file or on the command line when you start the POA. See "Installing and Starting the POA" in "Post Office Agent" in the GroupWise 6.5 Administration Guide.
Possible Cause: The /home switch points to an unavailable location.
Action: Make sure the location specified by the /home startup switch is currently available to the POA. If the post office is located on a different server from where the POA will run, preparations for the connection between the POA and the post office are required:
See "Installing and Starting the POA" in "Post Office Agent" in the GroupWise 6.5 Administration Guide.
Possible Cause: The server where the post office resides is down.
Action: Check the status of the server where the post office resides.
Possible Cause: The POA does not have sufficient rights to the post office directory.
Action: Make sure the network rights in the post office are correct. Start the POA using the /rights switch to determine the specific problem the POA is encountering and make corrections as needed.
Possible Cause: The post office database (wphost.db) is damaged.
Action: If the post office database is available to the POA but cannot be read, it might be damaged. In ConsoleOne®, perform database maintenance to correct any problems with the post office database. See "Maintaining Domain and Post Office Databases" in "Databases" in the GroupWise 6.5 Administration Guide.
Possible Cause: The POA server has inadequate resources.
Action: Make sure the server where you are trying to run the POA has adequate resources to run the POA, especially adequate available memory and the current versions of any required network system files. See "Agent System Requirements" in "Installing GroupWise Agents" in the GroupWise 6.5 Installation Guide.
Use your operating system tools to check current server resources.
Possible Cause: The POA is not installed correctly.
Action: Make sure all files required to run the POA are installed. For a list of agent files, see "Agent Installation Directories" in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure.
Possible Cause: A remote document storage area is unavailable.
Action: Make sure the remote server where the document storage area is located is running.
Action: Make sure the POA has sufficient rights to log in.
Action: Make sure the /user and /password or /dn switches have been provided in the POA startup file.
Action: As a temporary workaround, you can start the POA with the /noconfig switch, so it can start without trying to access the remote document storage area.
Possible Cause: Language files are missing.
Action: If you are using the /language startup switch to run the POA in a particular language, the corresponding language files must be installed for the POA to run in that language. To determine what language-specific files are required, see "Agent Installation Directories" in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure.
Possible Cause: A POA is already running on the server.
Action: If you have defined multiple POAs for the same post office in ConsoleOne, the /name switch is required in each startup file to specify which POA configuration to use when you start each instance of the POA.
Possible Cause: The POA encounters an error condition.
Action: If you receive an error message when trying to start the POA, look it up in "Post Office Agent Error Messages" in GroupWise 6.5 Troubleshooting 1: Error Messages.