Source: GroupWise agents.
Explanation: Logging information to disk has been turned off because the agent can no longer write to the current log file.
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. See "Using MTA Log Files" in "Message Transfer Agent" in the GroupWise 6.5 Administration Guide. The agent will create a new log file.
You can also use Cycle Log from the MTA agent console to start a new log file. See "Cycling the MTA Log File" in "Message Transfer Agent" in the GroupWise 6.5 Administration Guide.