MTA log shows 8200 error Disk logging turned off

(Last modified: 15Sep2003)

This document (10086685) is provided subject to the disclaimer at the end of this document.

fact

Novell GroupWise 6.5

Support Pack 1

Novell Netware 6

Support Pack 3

symptom

MTA log shows 8200 error Disk logging turned off

B305 errors reported in MTA log

8E03 error on POA and GroupWise clients

B305 would occur after the 8200, the 8E03 would occur after the MTA showed the B305 error

MTP threads start spooling on the POA

Performance is poor while the errors are occurring

fact

MTA loaded in Protected Memory

fix

This issue has been fixed in NWMEM3.EXE.  This fix will only be applied if SP3 for Netware 6 has been applied.  Please check your support pack version from the server console by typing "version" and NWCONFIG > Product Options > View/Configure/Remove installed products.  In this we applied NWMEM3 and it looked like it worked, but checking the dates of the files it updates showed it didn't.  NWCONFIG showed the support pack version as SP2, but version at the server console showed SP3.  The server had to be patched to SP3 correctly before the NWMEM3.EXE could fix the 8200 Disk logging turned off error.

The B305 and 8E03 errors were resolved by adding the /IP switch to the MTA and POA startup files specifying the correct secondary IP address the agent should be communicating over.  Packet traces showed the POA and MTA using two different IP addresses in communicating to each other.  This should be OK if host names have been specified for the agents addresses and in Link Configuration, but isn't if specific IP addresses have been stated.

note

Troubleshooting:

1.  Using GW65 - updated to SP1 - didn't help
2.  Applied NWMEM3 to fix 8200 on MTA -- didn't help
3.  Ran NSSPOOLVERIFY to see if there might be a problem with NSS - no errors found
4.  Applied NSS optimization switches to see if that might help - didn't
5.  When the MTA was reporting the 8200 error the customer used a workstation to create, rename and delete a file in the same directory where the MTA was trying to write the log file -- that was succesful
6.  Took a trace from the MTA and POA during the problem - It showed the MTA and POA each using two IP addresses -  added the /ip switch to the MTA and POA to force a bind to one IP address -- didn't help
7.  We found that support pack 3 may not have been applied properly.  Applied it correctly, then reapplied NWMEM3.  The dates are now showing correctly for the files it applied.

document

Document Title:	MTA log shows 8200 error Disk logging turned off
Document ID:	10086685
Solution ID:	NOVL92178
Creation Date:	03Sep2003
Modified Date:	15Sep2003
Novell Product Class:	Groupware NetWare

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.