Problem: The POA has been running smoothly, but stops unexpectedly.
Action: If the POA agent console is still displayed, exit it. If the normal exit procedure does not work, use the system procedure for terminating a program.
Action: After the POA agent console is no longer displayed, restart the POA as you normally would. See "Installing and Starting the POA" in "Post Office Agent" in the GroupWise 6.5 Administration Guide. If the POA shuts down again, exit it again, reboot the server, then start it again.
Action: Set the POA log level to Verbose for troubleshooting. See "Using POA Log Files" in "Post Office Agent" in the GroupWise 6.5 Administration Guide.
Possible Cause: Occasionally, a badly damaged message file can cause the POA to shut down.
Action: Check the contents of the POA input queue in the post office. For the location of the POA input queue in the post office, see "Post Office Directory" in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure.
Move the message files out of the input queue subdirectories, start the POA, then copy the message files back in groups, watching the POA carefully to see if it shuts down on a particular message file. If it does, delete the problem message file so normal processing can resume.
Action: Rename the post_office\wpcsout\ofs directory, then start the POA. This creates a new, empty input queue and the POA should run smoothly. Then copy the message files from the 0-7 priority subdirectories of wpcsout\ofs back into the correct priority subdirectory so the POA can process them. Copy them in small groups so the damaged message file can be identified and removed.
Possible Cause: Occasionally, a damaged database in the post office can cause the POA to shut down.
Action: In ConsoleOne, perform maintenance to correct any problems with the databases in the post office. See "Maintaining Domain and Post Office Databases" and "Maintaining User/Resource and Message Databases" in "Databases" in the GroupWise 6.5 Administration Guide.
Possible Cause: Although increasing the number of POA threads from their default settings can, in many cases, improve POA performance, creating too many POA threads can have undesirable results.
Action: For guidance is setting an appropriate number of POA threads, see "Optimizing the POA" in "Post Office Agent" in the GroupWise 6.5 Administration Guide.
Possible Cause: On a NetWare server, Upgrade Low Priority Threads is set to On.
Action: The POA might run more smoothly if you set Upgrade Low Priority Threads to Off. At the server console where the POA is running, type set upgrade low priority threads=off.
Possible Cause: Another program on the server is interfering with the operation of the POA.
Action: If the POA continues to be unstable, eliminate other programs running on the server. If the POA is stable when another specific program is not running on the same server with it, a conflict might exist between the two programs.