1

Resolved

exception was thrown while processing data from client

description

I am running Windows 2003 r2 sp2 x64 and exchange 2007 sp1 - I get this error in the event log and mail stops.
 
Event Type: Error
Event Source: MSExchangeTransport
Event Category: SmtpReceive
Event ID: 1033
Date: 1/7/2008
Time: 2:27:54 PM
User: N/A
Computer: TP2
Description:
An exception was thrown while processing data from client IP address 88.230.76.199. The exception is System.NullReferenceException: Object reference not set to an instance of an object.
at CatchAll.CatchAllAgent.RcptToHandler(ReceiveEventSource source, RcptCommandEventArgs rcptArgs)
at Microsoft.Exchange.Data.Transport.Smtp.SmtpReceiveAgent.Invoke(String eventTopic, Object source, Object e)
at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.Dispatcher.Invoke(MExSession session)
at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExSession.AsyncInvoke(Object state)
at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExSession.BeginInvoke(String topic, Object source, Object e, AsyncCallback callback, Object callbackState)
at Microsoft.Exchange.Protocols.Smtp.MExEvents.RaiseEvent(MExSession mexSession, String eventTopic, Int32 timeout, AsyncCallback callback, Object state, Object[] contexts)
at Microsoft.Exchange.Protocols.Smtp.SmtpCommand.RaiseEvent(AsyncCallback callback, Object state)
at Microsoft.Exchange.Protocols.Smtp.SmtpInSession.StartProcessingCommand(Byte[] inputBuffer, Int32 offset, Int32 size, Boolean overflow)
at Microsoft.Exchange.Protocols.Smtp.SmtpInSession.ReadLineComplete(IAsyncResult asyncResult).
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

comments

wilbertdg wrote Jan 18, 2008 at 4:43 AM

Do you happen to have a crash dump on your system, that you can share? It would typically be located at:

C:\Windows\PCHEALTH\ERRORREP\QHEADLES
-or-
C:\Windows\PCHEALTH\ERRORREP\QSIGNOFF

Anyway, I checked the sources and I think I know what the issue is. But this would happen if it failed to load the configuration file. If you enable tracing, it should tell you what the problem was. I will provide a fix for this issue, but please note that it failed to load the XML file, so the filter itself will still not work if you'd hit this error.

wilbertdg wrote Jan 23, 2008 at 4:45 AM

The issue was that 'Network Service' did not have read permission to the configuration file. The user has fixed that and it now works. The bug itself which reported the crash has also been fixed though. If something similar now happens, the configuration will be ignored, and the reason will be written to the trace file. Eventually this should become an event log.

wrote Jan 23, 2008 at 4:45 AM

wrote Feb 14, 2013 at 6:39 PM

wrote May 16, 2013 at 8:35 AM

wrote May 16, 2013 at 8:35 AM

wrote Jun 14, 2013 at 7:01 AM