DF17 on the Library of a Post Office Agent After Migrating the Post Office to Linux

  • Document ID:7002119
  • Creation Date:08-Dec-2008
  • Modified Date:30-Apr-2012
    • Micro Focus Products:
      GroupWise
    • SUSE Products:
      SUSE Linux Enterprise Server

Environment

Novell GroupWise 8
Novell GroupWise 7
Novell SUSE Linux Enterprise Server 10

Situation

POA migrated to Linux
DF17 error on POA startup
Domain shows correct Linux path to Library Storage Area
Post Office Agent will not load

Resolution


STEP 1

See TID - 3790690 Error DF17 displayed when loading POA
Use the steps therein to test the system.
If the POA loads with the --noconfig switch properly, but the gwcheck does not fix the problem, move on to the next step before contacting Novell Technical Support.

STEP 2

Verify the MTP information for the Post Office and Domain.
The Message Transfer Port information will be found in ConsoleOne in the MTA's and POA's Network Address Properties.

Load the POA with the following command line at the terminal:
Note: The load command should execute from within the same directory where the agent is located.  The default is /opt/novell/groupwise/agents/bin .

Syntax:

./gwpoa --show --home post_office_directory --noconfig --mtpinip poa_ip --mtpinport poa_mtp_port

Example:

./gwpoa --show --home /mnt/grpwise/testpo --noconfig --mtpinip 151.155.129.136 --mtpinport 7101

Once this loads properly, allow the POA to run for the time being.
Look at the domain and ensure that it shows the POA as 'open' to it.
If not, then restart the MTA.
The domain's --show screen or the web interface should allow for this.
Allow time for the admin messages to flow from the MTA to the POA.
This should change the path for the Library Storage Area at the Post Office level and beyond.

Additional Information

The problem occurs when the migration takes place and the Guardian Database is not updated properly.
The Guardian (ngwguard.db) should allow for the changes during the migration via the gwcheck /storelowercase procedure.
It may not automatically change, however, and the Linux path may not be updated within the Guardian database.
This procedure allows the Post Office to connect with the Domain long enough for the MTA to send the admin message to the Post Office for it to change the Guardian database's path to to match the one specified in ConsoleOne.

If this procedure fails to accomplish the task, it may be necessary to continue with the procedure specified in the first referenced TID and contact Novell Technical Support to have the Guardian database manually changed.  This is a last resort, however.