POA Fails to Update the Post Office Database Version

Problem: You are updating the agent software on a server where both the POA and the MTA are running. The MTA successfully updates the database version for the domain but the POA fails to update the database version for the post office.
Possible Cause: You let the Installation program start both agents automatically. As a result, the POA checked the domain version in the post office database before it had a chance to process the administrative message from the MTA that would update the domain version in the post office database.
Action: Wait until the MTA has updated the domain database. For a large domain database, you might need to wait as much as 20 minutes or more. Verify that the database version has been updated by checking the Domain object’s Identification page in ConsoleOne, then stop and restart the POA to update the post office database. Check the Post Office object’s Identification page in ConsoleOne to verify that the database version has been updated.
Action: If restarting the POA does not update the post office database version:

  1. Compare the dates on the .dc files (gwpo.dc and ngwguard.dc) in the post office directory with the dates on the .dc files in the update source (the GroupWise 7 Administrator CD or the software distribution directory if it has been updated from the GroupWise 7 Administrator CD).

  2. If the dates on the .dc files in the post office are older than the dates on the .dc files in the update source, copy the .dc files from the update source into the post office directory.

  3. At the POA console, recover the post office database. See Recovering the Post Office Database Automatically or Immediately in Post Office Agent in the GroupWise 7 Administration Guide.

    When the recovery process is finished, the database version should be updated.

  4. View the Post Office object’s Identification page in ConsoleOne to verify that the database version has been updated.