Action:In Configuration Status Details, check the directory paths
for mapped and UNC connections or the IP addresses and port numbers
for TCP/IP links. Make sure the correct locations are displayed.
Make sure the locations exist, and verify that the database (wpdomain.db for
a domain or wphost.db for a
post office) is there in the specified location. Do not use eDirectory™ paths.
Possible Cause:A domain or post office has been moved incorrectly.
Action:When you move a domain or post office to a new location or
change its link type, you must make various configuration changes
in ConsoleOne. If the domain or post office becomes closed as a
result, the reconfiguration changes might not have replicated down
to the agent in the reconfigured location before other changes prevented
the replication from happening at all. Rebuild the location database
(wpdomain.db or wphost.db).
Domain or Post Office Databases in Databases in
7 Administration Guide. This ensures that the
reconfiguration changes are replicated to the location. Then restart
the agent for the location.
Possible Cause:The MTA server has insufficient memory.