On a Microsoft Exchange Server 2007 Service Pack 1 (SP1) Edge server, when you use a Send connector that uses the BasicAuthRequireTLS value, the Edgetransport.exe process may crash intermittently. Additionally, the following errors may be logged in the Application log:

Event Type: Error
Event Source: MSExchangeTransport
Event Category: PoisonMessage
Event ID: 10003
Description:
The transport process failed during message processing with the following call stack: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at
Microsoft.Exchange.Security.Cryptography.CapiNativeMethods.CertGetCertificateChain(S afeChainEngineHandle engine, IntPtr pCertContext, IntPtr time, SafeCertStoreHandle hAdditionalStore, CertChainParameter& parameters, ChainBuildOptions flags, IntPtr reserved, SafeChainContextHandle& chainContext)
at
Microsoft.Exchange.Security.Cryptography.X509Certificates.ChainEngine.BuildAsAnonymo us(X509Certificate2 certificate, ChainBuildOptions options, ChainBuildParameter parameter)
at
Microsoft.Exchange.Protocols.Smtp.CertificateValidator.ChainValidateInternal(String domain, X509Certificate2 cert, Boolean validateAsAnonymous)
at
Microsoft.Exchange.Protocols.Smtp.CertificateValidator.ChainValidateAsAnonymous(X509 Certificate2 cert)
at
Microsoft.Exchange.Protocols.Smtp.SmtpOutSession.TlsNegotiationComplete()
at
Microsoft.Exchange.Protocols.Smtp.SmtpOutSession.TlsNegotiationComplete(IAsyncResult asyncResult)
at
Microsoft.Exchange.Net.LazyAsyncResult.Complete(IntPtr userToken)
at
Microsoft.Exchange.Net.NetworkConnection.InvokeSendCallback(LazyAsyncResultWithTimeo ut asyncResult, Object result)
at
Microsoft.Exchange.Net.NetworkConnection.SendTlsNegotiationCompleted(IAsyncResult asyncResult)
at System.Net.LazyAsyncResult.Complete(IntPtr userToken)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.ContextAwareResult.Complete(IntPtr userToken)
at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)
at System.Net.Sockets.BaseOverlappedAsyncResult.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)

Event Type: Error
Event Source: MSExchange Common
Event Category: General
Event ID: 4999
Description:
Watson report about to be sent to dw20.exe for process id: <xxxx>, with parameters: E12, c-RTL-AMD64, 08.01.0240.006, edgetransport, M.E.Net, M.E.S.C.CapiNativeMethods.CertGetCertificateChain, System.AccessViolationException, 4d3a, 08.01.0240.005. ErrorReportingEnabled: True

Event Type: Error
Event Source: Microsoft Exchange Server
Event Category: None
Event ID: 5000
Description:
EventType e12, P1 c-rtl-amd64, P2 08.01.0240.006, P3 edgetransport, P4 m.e.net, P5 m.e.s.c.capinativemethods.certgetcertificatechain, P6 system.accessviolationexception, P7 4d3a, P8 08.01.0240.005, P9 NIL, P10 NIL.

Back to the top

To resolve this problem, install Update Rollup 2 for Exchange Server 2007 Service Pack 1.

For more information about Update Rollup 2 for Exchange Server 2007 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Back to the top

For more information about BasicAuthRequireTLS, visit the following Microsoft Web site:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the naming schema for Exchange Server software updates, click the following article number to view the article in the Microsoft Knowledge Base:

Back to the top