Exchange 2013 errors : Event ID 65535 from source Application cannot be found

Noticed other folks here as well getting similar errors but no resolution, has MS team identified the source/bug related to these errors ? (These happen at random intervals of 25 mins,  45 mins etc etc. no fixed time intervals to be frank just randomly and are happening more often at night compared to during the day)

What is causing this error ? Is it a network connection issue or something else ? I believe it started for us only few weeks back. Is exchange trying to update itself to CU2 ? We are on Exch 2013 CU1 inside a VM. There are no other exch servers. All our services are virtualized like AD's and DNS servers.

Could it be related to some issue with DPM 2012 SP1 doing exchange backups of mailboxes and timing out issues ?

XML details :

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System>   <Provider Name="Application" />   <EventID Qualifiers="0">65535</EventID>   <Level>2</Level>   <Task>0</Task>   <Keywords>0x80000000000000</Keywords>   <TimeCreated SystemTime="2013-08-22T13:15:59.000000000Z" />   <EventRecordID>430152</EventRecordID>   <Channel>Application</Channel>   <Computer>exchange.domain.com</Computer>   <Security />   </System> - <EventData>   <Data><TraceRecord xmlns="http://schemas.microsoft.com/2004/10/E2ETraceEvent/TraceRecord" Severity="Error"><TraceIdentifier>http://msdn.microsoft.com/en-US/library/System.ServiceModel.Diagnostics.ThrowingException.aspx</TraceIdentifier><Description>Throwing an exception.</Description><AppDomain>MSExchangeFrontendTransport.exe</AppDomain><Exception><ExceptionType>System.ServiceModel.CommunicationException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'.</Message><StackTrace> at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) at System.ServiceModel.Channels.FramingDuplexSessionChannel.CloseOutputSessionCore(TimeSpan timeout) at System.ServiceModel.Channels.TransportDuplexSessionChannel.CloseOutputSession(TimeSpan timeout) at System.ServiceModel.Channels.TransportDuplexSessionChannel.OnClose(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Close(TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.OnClose(TimeSpan timeout) at System.ServiceModel.Channels.CommunicationObject.Close(TimeSpan timeout) at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.ServiceModel.Channels.ServiceChannelProxy.ExecuteMessage(Object target, IMethodCallMessage methodCall) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeChannel(IMethodCallMessage methodCall) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&amp;amp; msgData, Int32 type) at System.ServiceModel.ICommunicationObject.Close() at Microsoft.Exchange.Net.WcfUtils.DisposeWcfClientGracefully(ICommunicationObject client, Boolean skipDispose) at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient() at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception&amp;amp; exception) at Microsoft.Exchange.Data.Directory.ServiceTopologyProvider.GetTopologyVersions(IList`1 partitionFqdns) at Microsoft.Exchange.Data.Directory.TopologyProvider.GetTopologyVersion(String partitionFqdn) at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.CheckTopologyVersionForRebuild() at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, String partitionFqdn, ADObjectId domain, String serverName, Int32 port, NetworkCredential credential) at Microsoft.Exchange.Data.Directory.ConnectionPoolManager.GetConnection(ConnectionType connectionType, String partitionFqdn) at Microsoft.Exchange.Data.Directory.ADDataSession.GetConnection(String preferredServer, Boolean isWriteOperation, String optionalBaseDN, ADObjectId&amp;amp; rootId, ADScope scope) at Microsoft.Exchange.Data.Directory.ADDataSession.GetReadConnection(String preferredServer, String optionalBaseDN, ADObjectId&amp;amp; rootId, ADRawEntry scopeDeteriminingObject, DualSearchMode dualSearchMode) at Microsoft.Exchange.Data.Directory.ADGenericReader.GetNextResultCollection(Type controlType, DirectoryControl&amp;amp; responseControl) at Microsoft.Exchange.Data.Directory.ADPagedReader`1.GetNextResultCollection() at Microsoft.Exchange.Data.Directory.ADGenericPagedReader`1.GetNextPage() at Microsoft.Exchange.Data.Directory.ADGenericPagedReader`1.&amp;lt;GetEnumerator&amp;gt;d__0.MoveNext() at Microsoft.Exchange.Data.Directory.ADDataSession.ReadBatch[TKey,TData](TKey[] keys, ADObjectId rootId, Converter`2 filterBuilder, QueryFilter commonFilter, HashInserter`1 hashInserter, HashLookup`2 hashLookup, IEnumerable`1 properties, Boolean includeDeletedObjects, List`1 results) at Microsoft.Exchange.Data.Directory.ADDataSession.ReadMultiple[TKey,TData](TKey[] keys, ADObjectId rootId, Converter`2 filterBuilder, QueryFilter commonFilter, HashInserter`1 hashInserter, HashLookup`2 hashLookup, IEnumerable`1 properties, Boolean includeDeletedObjects) at Microsoft.Exchange.Data.Directory.ADDataSession.ReadMultiple[TKey,TData](TKey[] keys, Converter`2 filterBuilder, HashInserter`1 hashInserter, HashLookup`2 hashLookup, IEnumerable`1 properties, Boolean includeDeletedObjects) at Microsoft.Exchange.Data.Directory.ADDataSession.ReadMultiple[TKey,TData](TKey[] keys, Converter`2 filterBuilder, HashInserter`1 hashInserter, HashLookup`2 hashLookup, IEnumerable`1 properties) at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.FindByProxyAddresses[TData](ProxyAddress[] keys, IEnumerable`1 properties) at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientCache`1.&amp;lt;&amp;gt;c__DisplayClass15.&amp;lt;FindAndCacheRecipients&amp;gt;b__12() at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount) at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientCache`1.FindAndCacheRecipients(IList`1 proxyAddressList) at Microsoft.Exchange.Transport.Categorizer.ProxyHubSelector.&amp;lt;&amp;gt;c__DisplayClass1.&amp;lt;GetRecipientDatabases&amp;gt;b__0() at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.RunADOperation(ADOperation adOperation, Int32 retryCount) at Microsoft.Exchange.Data.Directory.ADNotificationAdapter.TryRunADOperation(ADOperation adOperation, Int32 retryCount) at Microsoft.Exchange.Transport.Categorizer.ProxyHubSelector.GetRecipientDatabases(IReadOnlyMailItem mailItem) at Microsoft.Exchange.Transport.Categorizer.ProxyHubSelector.TrySelectHubServers(IReadOnlyMailItem mailItem, IEnumerable`1&amp;amp; hubServers) at Microsoft.Exchange.Transport.FrontendProxyRoutingAgent.FrontendProxyAgent.OnProxyInboundMessageEventHandler(ProxyInboundMessageEventSource source, ProxyInboundMessageEventArgs e) 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.Invoke() 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.DataInboundProxySmtpCommand.RaiseProxyInboundMessageEvent(SmtpInSession session, AsyncCallback callback) at Microsoft.Exchange.Protocols.Smtp.DataInboundProxySmtpCommand.ContinueEndOfHeaders(IAsyncResult ar) at Microsoft.Exchange.Data.Transport.Internal.MExRuntime.MExAsyncResult.InvokeCompleted() 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.BaseDataSmtpCommand.RaiseEOHEvent(Object state, SmtpInSession session, AsyncCallback callback, EndOfHeadersEventArgs eventArgs) at Microsoft.Exchange.Protocols.Smtp.DataInboundProxySmtpCommand.RawDataReceived(Byte[] data, Int32 offset, Int32 numBytes) at Microsoft.Exchange.Protocols.Smtp.SmtpInSession.ReadComplete(IAsyncResult asyncResult) at Microsoft.Exchange.Net.LazyAsyncResult.WorkerThreadComplete(Object state) at Microsoft.Exchange.Net.LazyAsyncResult.Complete(IntPtr userToken) at Microsoft.Exchange.Net.LazyAsyncResult.ProtectedInvokeCallback(Object value, IntPtr userToken) at Microsoft.Exchange.Net.NetworkConnection.InvokeRecvCallback(LazyAsyncResultWithTimeout asyncResult, Object result) at Microsoft.Exchange.Net.NetworkConnection.ReadDataAvailable(IAsyncResult asyncResult) at System.Net.LazyAsyncResult.Complete(IntPtr userToken) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Net.ContextAwareResult.Complete(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) </StackTrace><ExceptionString>System.ServiceModel.CommunicationException: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'. ---&amp;gt; System.IO.IOException: The write operation failed, see inner exception. ---&amp;gt; System.ServiceModel.CommunicationException: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'. ---&amp;gt; System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) --- End of inner exception stack trace --- at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) at System.ServiceModel.Channels.BufferedConnection.WriteNow(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, BufferManager bufferManager) at System.ServiceModel.Channels.BufferedConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) at System.ServiceModel.Channels.ConnectionStream.Write(Byte[] buffer, Int32 offset, Int32 count) at System.Net.Security.NegotiateStream.StartWriting(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.NegotiateStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) --- End of inner exception stack trace --- at System.Net.Security.NegotiateStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.NegotiateStream.Write(Byte[] buffer, Int32 offset, Int32 count) at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) --- End of inner exception stack trace ---</ExceptionString><InnerException><ExceptionType>System.IO.IOException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>The write operation failed, see inner exception.</Message><StackTrace> at System.Net.Security.NegotiateStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.NegotiateStream.Write(Byte[] buffer, Int32 offset, Int32 count) at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)</StackTrace><ExceptionString>System.IO.IOException: The write operation failed, see inner exception. ---&amp;gt; System.ServiceModel.CommunicationException: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'. ---&amp;gt; System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) --- End of inner exception stack trace --- at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) at System.ServiceModel.Channels.BufferedConnection.WriteNow(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, BufferManager bufferManager) at System.ServiceModel.Channels.BufferedConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) at System.ServiceModel.Channels.ConnectionStream.Write(Byte[] buffer, Int32 offset, Int32 count) at System.Net.Security.NegotiateStream.StartWriting(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.NegotiateStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) --- End of inner exception stack trace --- at System.Net.Security.NegotiateStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.NegotiateStream.Write(Byte[] buffer, Int32 offset, Int32 count) at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)</ExceptionString><InnerException><ExceptionType>System.ServiceModel.CommunicationException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'.</Message><StackTrace> at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) at System.ServiceModel.Channels.BufferedConnection.WriteNow(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, BufferManager bufferManager) at System.ServiceModel.Channels.BufferedConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) at System.ServiceModel.Channels.ConnectionStream.Write(Byte[] buffer, Int32 offset, Int32 count) at System.Net.Security.NegotiateStream.StartWriting(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.NegotiateStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)</StackTrace><ExceptionString>System.ServiceModel.CommunicationException: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'. ---&amp;gt; System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) --- End of inner exception stack trace --- at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) at System.ServiceModel.Channels.BufferedConnection.WriteNow(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, BufferManager bufferManager) at System.ServiceModel.Channels.BufferedConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) at System.ServiceModel.Channels.ConnectionStream.Write(Byte[] buffer, Int32 offset, Int32 count) at System.Net.Security.NegotiateStream.StartWriting(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.NegotiateStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)</ExceptionString><InnerException><ExceptionType>System.Net.Sockets.SocketException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType><Message>An existing connection was forcibly closed by the remote host</Message><StackTrace> at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)</StackTrace><ExceptionString>System.Net.Sockets.SocketException (0x80004005): An existing connection was forcibly closed by the remote host at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout)</ExceptionString><NativeErrorCode>2746</NativeErrorCode></InnerException></InnerException></InnerException></Exception></TraceRecord></Data>   </EventData>   </Event>
August 22nd, 2013 11:38am

Hello,

From the error, the issue may be caused by a receive timeout being exceeded by the remote host, or an underlying network resource issue. And there is no other event to show whether the issue is realted to DPM 2012 SP1.

If we need to get more detailed information, I recommend you change disgnostic logging levels to check the result.

Manage Diagnostic Logging Levels

http://technet.microsoft.com/en-us/library/dd335139.aspx

Besides, I recommend you make sure whether there is any third-party AV program installed. If so, please temporary uninstall it to check the result.

If not, I recommend you upgrade to CU2 to check the result.

If you have any feedback on our support, please click here

Free Windows Admin Tool Kit Click here and download it now
August 22nd, 2013 11:02pm

Gui option does not exists in Exchange 2013, but can setup via shell, but exactly which one do i need to set to high there are like billions of options, plus that error message does not really help, i am going to go with exchfrontendtransport or to be specific MSExchange TransportService\TransportService

and maybe MSExchangeTransport\SmtpSend

PS: i have Endpoint from MS and no 3rd party antivirus solution on exchange.

August 23rd, 2013 11:57am

Hello,

There is only 65535 error.I need more detailed information to troubleshooting the issue.

From the error, I recommend you set logging level for MSExchangeFrontendTransport service to expert to check if there is any error.

If you have any feedback on our support, please click here

Free Windows Admin Tool Kit Click here and download it now
August 25th, 2013 9:56pm

These are all set to expert, i see no FrontendTransport errors other than the 65535 errors , no warnings either, i do have however some weird LDAP error where it complains about not sufficient access to one of our ad. Not sure if that is related ? The errors are quite apart though time wise ! Only once i saw LDAP error followed by application error, but that must be just coincidence. The only other error i see isfor SMTPSEND

Send connector ebf5799b-9033-4c37-a9eb-6124ed87e163: A DNS failure occurred with the following diagnostic information The DNS query for  'DnsConnectorDelivery':'canada.com':'ebf5799b-9033-4c37-a9eb-6124ed87e163' failed with error : InfoNoRecords.

Process MSExchangeHMWorker.exe (ExHMWorker) (PID=3352). An LDAP Modify operation failed - Server=ad1.server.ca Error code=50 (Additional information: Access is denied.
Active directory response: 00000005: SecErr: DSID-031A1190, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
). Object DN=CN=HealthMailboxaffa3155ca8f4343be6de979c56f7304,CN=Users,DC=server,DC=ca. 

MSExchangeFrontEndTransport\SmtpReceive                                                                                                                                                      Expert
MSExchangeFrontEndTransport\SmtpSend                                                                                                                                                         Expert
MSExchangeFrontEndTransport\DSN                                                                                                                                                              Expert
MSExchangeFrontEndTransport\Routing                                                                                                                                                          Expert
MSExchangeFrontEndTransport\Logging                                                                                                                                                          Expert
MSExchangeFrontEndTransport\Components                                                                                                                                                       Expert
MSExchangeFrontEndTransport\RemoteDelivery                                                                                                                                                   Expert
MSExchangeFrontEndTransport\Pickup                                                                                                                                                           Expert
MSExchangeFrontEndTransport\Categorizer                                                                                                                                                      Expert
MSExchangeFrontEndTransport\PoisonMessage                                                                                                                                                    Expert
MSExchangeFrontEndTransport\MessageSecurity                                                                                                                                                  Expert
MSExchangeFrontEndTransport\TransportService                                                                                                                                                 Expert
MSExchangeFrontEndTransport\Exch50                                                                                                                                                           Expert
MSExchangeFrontEndTransport\Process                                                                                                                                                          Expert
MSExchangeFrontEndTransport\ResourceManager                                                                                                                                                  Expert
MSExchangeFrontEndTransport\Configuration                                                                                                                                                    Expert
MSExchangeFrontEndTransport\Storage                                                                                                                                                          Expert
MSExchangeFrontEndTransport\Agents                                                                                                                                                           Expert
MSExchangeFrontEndTransport\Transport Address Book                                                                                                                                           Expert
MSExchangeFrontEndTransport\Orar                                                                                                                                                             Expert
MSExchangeFrontEndTransport\Unused                                                                                                                                                           Expert
MSExchangeFrontEndTransport\ShadowRedundancy                                                                                                                                                 Expert
MSExchangeFrontEndTransport\Approval                                                                                                                                                         Expert
MSExchangeFrontEndTransport\TransportSafetyNet                                                                                                                                               Expert
MSExchangeFrontEndTransport\TransportTenantAttribution                                                                                                                                       Lowest

August 27th, 2013 11:29am

Hello,

I recommend you restart the MSExchangeFrontendTransport service .

If your send connector uses "DNS MX record" to route messages, please check if DNS MX record is correct.

Please make sure IPV6 is disabled.

Here is the similar thread for your reference.

http://social.technet.microsoft.com/Forums/exchange/en-US/72746e76-3dda-45c9-ad81-5c4ce4e3e0c6/can-only-recieve-mail-cannot-send

For the LDAP error, please refer to the following thread.

http://social.technet.microsoft.com/Forums/exchange/fr-FR/e57e5dcb-3276-413d-a423-b068b89aeb7e/exchange-management-console-new-user-creation-fails

If the issue persists, please try to upgrade to CU2 to check the result.

If you have any feedback on our support, please click here

Free Windows Admin Tool Kit Click here and download it now
August 27th, 2013 10:34pm

Follows my post from another thread which I now repeat here. Additional info:  I'm on CU2 and IPv6 is disabled, both in registry and on all (enabled and disabled) network adapters.

I have the same problem and they're the last red dots on my exchange 2013 server after a long battle! (not least after the latest security cruise missile...)

These red dots don't cause any other adverse symptoms *that I can see* 

Anyway:

The error (in my case) comes from MSExchangeFrontendTransport being timed out when it's trying to talk to Exchange Directory Topology Service on port 890.

When I look at this latter, it has loads of open incoming sessions on its 890 port (and one outgoing session using LDAP to AD, logically enough)

So there are three possibilities how I see it

(a) the Exchange Directory Topology Service is often timing sessions out, and it doesn't matter, and we only notice it for the ExchangeFrontendTransport because of the missing message string, or

(b) there is some underlying resource or timing issue with the Exchange Directory Topology Service which needs to be addressed, or

(c) MSExchangeFrontendTransport is intermittently doing something that the Exchange Directory Topology Service is rejecting

If someone could tell us what the next diagnostics steps might be, it would be great!!!

Cheers, Steve

August 28th, 2013 6:20am

Cara,

These are my send connector settings :

LDAP error is related to healthmailbox that i get, no other issues with creating a user via the shell or ecp, no permission errors when adding user or removing user/mailboxes from ecp. Only the healthboxmonitoring throws ldap error out of the 3 only 1 healthmailbox is doing it no other errors for the other 2 healhboxes.

Next time (probably at lunch today when i replicate problem) will compare the get-serverhealth and get-healthreport  outputs. When problem exists all functions work within exchange even adding mailboxes, can ping dc as well. Our mx records are set by the government because they provide us with firewall and the internet connectivity as well, so no control over that we just point to their routers gateway/firewall on our end.

Will CU2 help ? I do not think so reading what Steve posted !

Free Windows Admin Tool Kit Click here and download it now
August 28th, 2013 11:40am

Hello,

The output for send connector is unavailable. Please post it again.

Besides, if there is any update when the issue again, please free let me know.

If you have any feedback on our support, please click here

August 28th, 2013 9:50pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics