10.0 Post Office Agent Error Messages
NOTE:This guide does not include a comprehensive list of all possible GroupWise agent error messages. It lists error messages for which solutions are readily available from GroupWise engineers and testers. You can search the Novell Support Knowledgebase to locate additional solutions documented by Novell Support as specific customer issues have been resolved.
GWPOA: Admin database for post_office could not be recovered
Source:
GroupWise Post Office Agent; admin thread.
Explanation:
An attempt to recover the post office database (wphost.db) has failed.
Possible Cause:
The post office database requires repair beyond what can be done while in use.
GWPOA: Administrator record not found in database
Source:
GroupWise Post Office Agent; admin thread.
Explanation:
The POA admin thread can send a message to an administrator in case of database errors. However, no administrator has been designated.
Possible Cause:
No GroupWise administrator has been set up yet.
Action:
Use the --noerrormail switch when starting the POA to turn off administrator messages.
GWPOA: Application connection table full
Source:
GroupWise Post Office Agent; TCP agent.
Explanation:
The POA is configured for TCP/IP communication and it has run out of application connections.
Possible Cause:
The POA is very busy.
GWPOA: Authentication failed for the above object
Source:
GroupWise Post Office Agent; admin thread.
Explanation:
The POA admin thread attempted to process a record that has the wrong authentication key for the current GroupWise system.
Possible Cause:
The record did not originate in the current GroupWise system, which is a possible security violation.
Action:
Someone is trying to tamper with your GroupWise system. Check your system security measures.
GWPOA: Cannot access remote post office; retrying
Source:
GroupWise Post Office Agent.
Explanation:
The POA can no longer access its post office.
Possible Cause:
The server where the post office is located is currently down.
Action:
Wait for the server to come back up, or contact the administrator of that server.
GWPOA: Cannot access remote post office; user ID switch is missing
Source:
GroupWise Post Office Agent.
Explanation:
The Windows POA cannot access its post office because it cannot log in to the server where the post office is located.
Possible Cause:
The POA has not been started with the /user or /dn switch.
Action:
Include the /user and /password switches when the POA needs to access a post office on a remote server.
Action:
In ConsoleOne, specify the login information in the Remote File Server Settings box on the Post Office Settings page of the Post Office object.
GWPOA: Cannot find the help file
Source:
GroupWise Post Office Agent for Windows.
Explanation:
The Help file for the agent is not available.
GWPOA: Client/server login failed; no user ID supplied
Source:
GroupWise Post Office Agent.
Explanation:
The POA cannot communicate with a GroupWise client process that is requesting services because the client is not providing a user ID.
Possible Cause:
The GroupWise client was not started with the needed user ID information.
Action:
Use the /@u switch to make sure the client has the correct user ID information.
GWPOA: Configured address may not match actual address
Source:
GroupWise Post Office Agent; TCP agent.
Explanation:
The POA is configured for TCP/IP communication, but a mismatch of IP addresses has been detected.
Possible Cause:
DNS is not currently available, so the POA is unable to resolve a hostname into its IP address.
Action:
Make sure DNS is functioning correctly. Or specify the IP address instead of the hostname when configuring the POA.
Possible Cause:
The POA was started with the wrong --name switch setting, so that it is associated with the wrong configuration information.
Action:
Make sure the --name switch setting specifies the correct POA configuration.
Possible Cause:
TCP/IP is not set up correctly on the server where the POA is running.
Action:
Make sure TCP/IP is set up correctly.
GWPOA: Database language has been updated; please rebuild this database
Source:
GroupWise Post Office Agent; admin thread.
Explanation:
The post office database (wphost.db) needs to be rebuilt because the language has been changed, which changes the sort order of the users listed in the database.
GWPOA: Disk is full; turning disk logging off
Source:
GroupWise Post Office Agent.
Action:
Free up disk space. The agent should resume disk logging after disk space is available. To ensure that disk logging has resumed, check the Logging Level setting in the Log Settings page for the agent in ConsoleOne.
Action:
Specify a different location for log files where sufficient disk space is available.
Source:
GroupWise Post Office Agent; TCP agent.
Explanation:
The POA is configured for TCP/IP communication. The TCP agent might display a large number of error messages that begin with "Error creating...".
Possible Cause:
Insufficient memory.
GWPOA: Error creating file; turning disk logging off
Source:
GroupWise agents.
Explanation:
Logging information to disk has been turned off because the agent cannot create a new log file.
Possible Cause:
The agent cannot create a file in the location specified by the Log File Path setting on the Log Settings page for the agent in ConsoleOne or specified on the command line using the --log switch.
Action:
Make sure the location exists or specify a more appropriate location.
Action:
Make sure the agent has rights to create files in the specified location. Start the POA including the --rights switch to determine the specific problem the POA is encountering.
Action:
Make sure there is available disk space in the specified location.
GWPOA: Error initializing communications protocol
Source:
GroupWise Post Office Agent; TCP agent.
Explanation:
The POA is configured for TCP/IP communication but is unable to establish TCP/IP communication.
Possible Cause:
TCP/IP is not set up correctly on the server where the POA is running.
Action:
Make sure TCP/IP is set up correctly.
GWPOA: Error initializing HTTP
Source:
GroupWise Post Office Agent.
Explanation:
The HTTP port the POA is trying to use for its Web console is not responding correctly.
GWPOA: Error listening for connection
Source:
GroupWise Post Office Agent; TCP agent.
Explanation:
The POA is configured for TCP/IP communication but is unable to connect.
Possible Cause:
TCP/IP is not set up correctly on the server where the POA is running.
Action:
Make sure TCP/IP is set up correctly.
Possible Cause:
Insufficient memory.
GWPOA: Error opening listener port
Source:
GroupWise Post Office Agent; TCP agent.
Explanation:
The POA is configured for TCP/IP communication, but the port it is configured to listen on is already in use by another program.
GWPOA: Error putting item in queue
Source:
GroupWise Post Office Agent; TCP agent.
Explanation:
The TCP threads are not keeping up with the current workload.
GWPOA: Error writing to file; turning disk logging off
Source:
GroupWise Post Office Agent.
Possible Cause:
If the log file is located on a server other than the one where the agent is running, that server might be down.
Action:
Wait for the server to come back up, or contact the administrator of that server. When the server comes back up, the agent will resume disk logging.
Possible Cause:
The log file has been damaged so the agent can no longer write to it.
Action:
Remove the damaged log file and turn disk logging back on in the Log Settings page for the agent in ConsoleOne. The agent will create a new log file. You can also use from the POA server console or Web console to start a new log file.
GWPOA: Failed to redirect user; missing host configuration
Source:
GroupWise Post Office Agent.
Explanation:
The GroupWise client is attempting to contact the POA in client/server mode, but the POA is not set up for client/server communication.
Source:
GroupWise Post Office Agent.
Explanation:
The POA cannot access a required file.
Possible Cause:
The POA cannot read its startup file.
Possible Cause:
The POA cannot view its log file.
GWPOA: Host refused connection
Source:
GroupWise Post Office Agent; message transfer protocol.
Explanation:
The POA is configured to communicate with the MTA by way of TCP/IP. The server where the MTA is located has refused the POA’s request for a connection.
Action:
Check the TCP/IP configuration of the server to which the POA must connect.
GWPOA: HTTP port nn is already in use
Source:
GroupWise Post Office Agent.
Explanation:
The HTTP port the POA is trying to use for its Web console is already in use by another program.
GWPOA: Internal UDP port is unusable
Source:
GroupWise Post Office Agent; TCP agent.
Explanation:
The POA is configured for TCP/IP communication but it cannot access the UDP port of the server where it is trying to run.
Possible Cause:
TCP/IP is not set up correctly on the server where the POA is running.
Action:
Make sure TCP/IP is set up correctly.
GWPOA: Listen port already in use
Source:
GroupWise Post Office Agent; TCP agent.
Explanation:
The POA is configured for TCP/IP communication, but the port it is configured to listen on is already in use by another program.
GWPOA: Low disk space for QuickFinder indexing
Source:
GroupWise Post Office Agent.
Explanation:
The POA requires at least 20 MB of free disk space to perform QuickFinder indexing. This warning appears when disk space drops below 30 MB. The POA performs QuickFinder indexing as specified by the QuickFinder Update Interval setting on the POA Agent Settings page in ConsoleOne or as specified using the --qfinterval switch.
GWPOA: Machine appears to have TCP/IP incorrectly configured
Source:
GroupWise Post Office Agent; TCP agent.
Explanation:
The POA is configured for TCP/IP communication but it is unable to determine the IP address of the server where it is trying to run.
Possible Cause:
TCP/IP is not set up correctly on the server where the POA is running.
Action:
Make sure TCP/IP is set up correctly, including assignment of an IP address.
GWPOA: Not enough disk space for QuickFinder indexing
Source:
GroupWise Post Office Agent.
Explanation:
The POA requires at least 20 MB of free disk space to perform QuickFinder indexing. A warning appears when disk space drops below 30 MB. This error appears when free disk space drops below 20 MB. The POA performs QuickFinder indexing as specified by the QuickFinder Update Interval setting on the POA Agent Settings page in ConsoleOne or as specified using the ‑‑qfinterval switch.
Action:
Make sure sufficient free disk space is available on the server where the POA is running by the next time the POA needs to perform QuickFinder indexing.
GWPOA: Not enough memory to complete operation
Source:
GroupWise Post Office Agent.
Explanation:
Not enough memory is available for the POA to function properly.
Action:
Stop some other programs on the server to free up memory for use by the POA.
Action:
Add memory to the server to accommodate the POA along with other existing programs.
Action:
Select a different server to run the POA on, where adequate resources are available.
Possible Cause:
If the POA starts successfully, then encounters a memory error later during otherwise normal processing, some other program on the server, or another agent thread, might have temporarily used a large quantity of memory.
Action:
Wait to see if the memory problem resolves itself. The POA will retry its operations and should succeed at a later time, when the other program has released some memory.
Action:
If the POA starts successfully but frequently encounters memory errors during later processing, treat the situation as if the POA cannot start and see the recommended actions above.
GWPOA: One or more connections to a remote storage area have been lost and could not be reestablished
Source:
GroupWise Post Office Agent.
Explanation:
The POA has lost its connection to the server where a document storage area is located.
Possible Cause:
The server where the document storage area is located is down.
Action:
Wait for the server to come back up. The POA will reconnect automatically when the server is available again.
Action:
Contact the administrator of that server.
GWPOA: Physical connection table full
Source:
GroupWise Post Office Agent; TCP agent.
Explanation:
The POA is configured for TCP/IP communication and it has run out of physical connections.
Possible Cause:
The POA is very busy.
GWPOA: Possibly damaged blob in database
Source:
GroupWise Post Office Agent
Explanation:
During indexing, the POA has encountered a BLOB file that it could not process.
Possible Cause:
The BLOB file is damaged
Action:
Restore the BLOB file from backup.
Action:
If the damaged BLOB file cannot be restored, you can delete it to eliminate the error.
GWPOA: Possibly dangerous message; temporarily suspending dispatcher
Source:
GroupWise Post Office Agent
Explanation:
No additional message file processor threads will be started until processing of the current message file has completed. The current message file is flagged as having caused the POA to shut down in a previous processing attempt.
Possible Cause:
The current message file is damaged.
Action:
If all existing message file processor threads successfully process their message files, the POA will resume normal processing. No action is necessary.
Action:
If processing of a message file causes the POA to shutdown, do not put message files from the post_office/wpcsout/problem directory back into the POA input queue. Restart the POA.
GWPOA: Reached inbound connections limit
Source:
GroupWise Post Office Agent; message transfer protocol.
Explanation:
The POA is configured to communicate with the MTA by way of TCP/IP. The POA has reached the maximum number of inbound connections.
Action:
None. Connections are automatically released and reopened as processing continues.
GWPOA: Running the agent with conflicting effective users
Source:
GroupWise Post Office Agent for Linux.
Explanation:
You are starting the POA as a user that is different from the user the POA is configured to run as. The user specified in the uid.conf file does not match the user specified in the uid.run file.
Possible Cause:
The user specified in the uid.conf file has been manually edited.
Possible Cause:
The uid.conf file has been deleted.
GWPOA: StartServiceCtrlDispatcher failed when attempting to start Windows_agent service
Source:
GroupWise Post Office Agent for Windows.
Explanation:
The Windows POA cannot start its dispatcher thread.
Possible Cause:
The Windows server is not functioning properly.
Action:
Reboot the Windows server.
GWPOA: The Windows_agent service fails to set service status; service stopped
Source:
GroupWise Post Office Agent for Windows.
Explanation:
The Windows POA cannot start as a service.
Possible Cause:
The Windows POA cannot communicate with the service control manager (SCM).
Action:
Reboot the Windows server.
GWPOA: The Windows_agent service fails to initialize memory system; service stopped
Source:
GroupWise Post Office Agent for Windows.
Explanation:
The Windows POA cannot start as a service.
Possible Cause:
The Windows POA has insufficient memory resources.
Action:
Reboot the Windows server.
Action:
Run fewer programs on the server.
GWPOA: Timed out waiting for end-of-file confirmation
Source:
GroupWise Post Office Agent; message transfer protocol.
Explanation:
The POA is configured to communicate with the MTA by way of TCP/IP. The MTA has stopped responding in the middle of a communication.
Possible Cause:
The MTA is running on an overburdened server, so it cannot respond to the POA in a timely manner.
Action:
Add resources to the MTA server so that the MTA can function properly.
Possible Cause:
The server where the MTA is running has gone down.
Action:
Check the status of the MTA server. Reboot if necessary.
GWPOA: Transport header build failed
Source:
GroupWise Post Office Agent; message transfer protocol.
Explanation:
The POA is configured to communicate with the MTA by way of TCP/IP. The POA was unable to create a packet of information to send to the MTA.
Possible Cause:
Insufficient memory.
GWPOA: Unable to add additional message handler; maximum reached
Source:
GroupWise Post Office Agent.
Explanation:
The maximum number of message handler threads for the POA is 32. You cannot create any more message handler threads for this POA.
GWPOA: Unable to change all configuration options
Source:
GroupWise Post Office Agent.
Explanation:
POA configuration settings have been changed in ConsoleOne, but some cannot be put into effect until the POA is restarted.
Action:
Exit and restart the POA.
GWPOA: Unable to load viewer
Source:
GroupWise Post Office Agent for Windows.
Explanation:
The POA cannot run the program used to view agent log files or edit agent startup files.
Possible Cause:
The viewer program is not available on the current path or is incorrectly specified.
Action:
The default viewer used by the POA is Notepad, which is typically available. You can change the viewer specification by selecting in the Windows POA server console or Web console and changing the information in the Viewer field. Check the viewer and path specified under in the POA server console or Web console.
GWPOA: Unable to remove document storage area
Source:
GroupWise Post Office Agent.
Explanation:
The POA cannot delete the document storage area.
Possible Cause:
The library database (dmsh.db) is damaged, so that the POA cannot read the information necessary to delete the storage area.
GWPOA: Unable to start IMAP because SSL is not configured
Source:
GroupWise Post Office Agent.
Explanation:
The POA cannot start because it is configured to use SSL for its IMAP connection and SSL is not correctly configured.
Possible Cause:
The SSL certificate or key file is missing
GWPOA: Unable to start SOAP because SSL is not configured
Source:
GroupWise Post Office Agent.
Explanation:
The POA cannot start because it is configured to use SSL for its SOAP connection and SSL is not correctly configured.
Possible Cause:
The SSL certificate or key file is missing