Novell GROUPWISE 7 - TROUBLESHOOTING 2 Troubleshooting Manual page 29

After communication between the POA and MTA is re-established, make the
configuration changes again. Wait for the configuration changes to be
replicated to the post office database (wphost.db), then start the POA in its
new location.
Action: Stop the POA, then start the POA using the
switches to specify the new IP address and port the POA should use for
Message Transfer Protocol (MTP) communication with the MTA. After the
link is established and all administrative messages have been processed, you
do not need to use these startup switches again.
Action: Stop the POA. Rebuild the post office database (wphost.db) to replicate the
configuration changes. See
"Databases" in the
POA Fails to Respond to Other Configuration Changes in ConsoleOne
Problem: You change a POA configuration setting in ConsoleOne, but the POA does not
respond to the change. For example, you change from direct access to client/
server mode, or you want to turn off error mail to the administrator.
Action: Synchronize the post office database (wphost.db) with the domain database
(wpdomain.db). See
in the
Action: Stop the POA. Rebuild the post office database (wphost.db) to replicate the
configuration changes. See
"Databases" in the
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
2 If the dates on the .dc files in the post office are older than the dates on the
"Rebuilding Domain or Post Office
GroupWise 7 Administration
"Synchronizing Database
GroupWise 7 Administration
"Rebuilding Domain or Post Office
GroupWise 7 Administration
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).
.dc files in the update source, copy the .dc files from the update source
into the post office directory.
/mtpinipaddr and
Guide.
Information" in "Databases"
Guide.
Guide.
(gwpo.dc and ngwguard.dc) in
/mtpinport
Databases" in
Databases" in
Post Office Agent Problems 29