The post office version does not get updated when the new agents are loaded when upgraging to GroupWise 6.0 or 6.5
Articles and Tips: qna
01 Jun 2003
GroupWise
Scenario
When upgrading a GroupWise post office or domain to GroupWise version 6.0 or 6.5 and they are both on the same server, the post office version does not get updated when the new agents are loaded.
Problem:
The *.DC files did not update correctly. The GWPO.DC file is not in the post office directory or is an older version of the file. The POA checked the wphost.db on for the owning domain's version, since the MTA is in the process of updating the domain, the post office still shows the domain as the older version. By the time the domain completes its upgrade and sends the admin messages to update the post office, the POA has skipped the upgrade process.
Solution:
Following are some steps to take to update the database. They should be done in the order listed.
Check the database version from ConsoleOne.
If the version is 6.5, then exit the POA and restart it
If the post office was created with GroupWise 4.x, it's possible that the old security settings have caused the POA to correct those settings. Restarting the POA will complete the update allowing users to access the post office with the GW 6.5 client.
Prior to the POA exit and restart, the GW 6.5 client will get an error telling the user that the client version is too new for the post office version.
If the database version is still 5.5 then check the dictionary files in the root directory of the post office. They should have the following dates:
Gwpo.dc (8/13/2002)
ngwguard.dc (1/9/2003)
If the dates are not correct, copy the files from the Admin CD from the following locations:
gwpo.dc: <cd root directory>\domain directory
ngwguard.dc: <cd root directory>\po directory
Check the POA console screen. F10 | Admin Status | Recovery Count
If the Recovery Count is 0 (zero) then the POA didn't pick up the needed trigger to update the database.
To correct this and complete the update, select the "Perform DB Recovery Now?" option on the same POA console screen from which you checked the Recovery Count.
Allow the recovery to complete and then check the post office version in ConsoleOne. It should now be 6.5.
Prevention:
To prevent this from happening, only load the MTA and let it complete the update to the domain. Once it is complete, load the POA for the post office on the same server as the domain
* Originally published in Novell Connection Magazine
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.