Messages are not flowing between the migrated POA and the MTA for the domain
Display the POA console.
http://source_server_address:port_number
Click MTP Status.
The status in the Receive column shows Closed.
Click the Closed link,
In the Address field, specify the new IP address of the POA, then select Start MTP Receive.
Click Submit to execute the actions.
The POA cannot start
Start the POA with the /noconfig switch so that the POA ignores the troublesome configuration settings and starts successfully.
Because of the /noconfig switch, manually configure the link between the POA and the MTA for the domain. See Messages are not flowing between the migrated POA and the MTA for the domain
Follow the instructions in Reconfiguring the Migrated POA to configure the log file path correctly.
Allow time for the configuration information to replicate from ConsoleOne to the post office database (wphost.db) so that the POA has the correct configuration settings.
Start the POA again.
It should start successfully this time.
The POA cannot start because of incorrect permissions
Error: Running the agent with conflicting effective users
On the Linux server, change to the post office folder.
Delete the uid.run file.
Start the POA again.
It should start successfully this time.
The POA cannot start because of a C06B error
Start the POA with the /noconfig switch so that the POA ignores the troublesome configuration settings and starts successfully.
Because of the /noconfig switch, manually configure the link between the POA and the MTA for the domain. See Messages are not flowing between the migrated POA and the MTA for the domain
Follow the instructions in Reconfiguring Remote Document Storage Areas to configure the remote document storage areas correctly.
Allow time for the configuration information to replicate from ConsoleOne to the post office database (wphost.db) so that the POA has the correct configuration settings.
Start the POA again.
It should start successfully this time.
The POA starts with SSL errors
In ConsoleOne, browse to and right-click the POA object, then click Properties.
Click GroupWise > SSL Settings.
Remove the path information from the Certificate File and Key File fields.
The information pertains to the source NetWare or Windows server, not the Linux server, and is therefore not needed.
The Server Migration Utility places certificate files and key files in their default location on Linux (/opt/novell/groupwise/agents/bin).
Click OK to save the settings.
Allow time for the configuration information to replicate from ConsoleOne to the post office database (wphost.db).
When the POA has the correct configuration settings, SSL is enabled as usual.
The POA starts with TCP/IP errors
TCP/IP services on your system may not be configured or installed
This would happen only if you manually copied the startup file to the Linux server, because the Server Migration Utility comments out the /ip switch in order to avoid this problem.