MTA Fails to Update
the Domain Database Version
You are updating the MTA software in a secondary domain and
the MTA fails to update the database version for the domain. You
might see conflicting database version information depending on
whether you are connected to the secondary domain or the primary
You installed and started the MTA for the secondary domain
before the MTA for the primary domain had finished updating the
primary domain database.
Wait until the MTA for the primary domain has finished updating
the primary domain database. For a large domain database, you might
need to wait as much as 20 minutes or more. Verify that the primary
domain database version has been updated by checking the Domain
object’s Identification page in ConsoleOne. Then stop and
restart the MTA for the secondary domain to update the secondary
If restarting the MTA for the secondary domain does not update
the domain database version:
dates on the .dc files (gwdom.dc and gwpo.dc)
in the secondary domain 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).
If the dates on the .dc files
in the secondary domain are older than the dates on the .dc files
in the update source, copy the .dc files from
the update source into the domain directory.
At the MTA console, recover the domain
the Domain Database Automatically or Immediately in
Transfer Agent in the GroupWise
7 Administration Guide.
When the recovery process is finished, the database version
should be updated.
In ConsoleOne, connect to the secondary
domain, then check the Domain object’s Identification page
to verify that the database version has been updated.
Connect to the primary domain database,
then check the Identification page for the primary domain to verify
that the database version information matches in both domain databases.
There are one or more closed links between the secondary domain
and the primary domain that are preventing the administrative messages
from flowing between the domains to accomplish the database version