can anyone tell me what's causing this error and how to fix it. this is a fresh install of exchange 2013 on a clean server 2012 server.

I'm getting a bunch of these:

Active Manager Client experienced an AD timeout trying to lookup object '00:01:00' in %2.

dcdiag on the exchange box returns full pass. there's no appreciable CPU or memory load on either box and the network connection is good.

however, i'm also getting these crashes:

The description for Event ID 65535 from source Application cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

<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.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)
   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)
   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__4.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__DisplayClass17.&amp;lt;FindAndCacheRecipients&amp;gt;b__14()
   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.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.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 ---</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></Exception></TraceRecord>

the message resource is present but the message is not found in the string/message table

i have to say i'm really unhappy with my exchange 2013 experience so far. definitely a downgrade in my opinion.

oh, here's a bunch more errors i keep getting:

Ping of mdb '21745b3e-f5f3-4ba8-81bb-e4aeeb2657c8' timed out after '00:00:00' minutes.  Last successful ping was at '1/22/2013 7:55:56 PM' UTC.

Failed to read killbit list file because of exception System.IO.IOException: The process cannot access the file 'C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\15.0.516.30\owa2\ext\killbit\killbit.xml' because it is being used by another process.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
   at Microsoft.Exchange.Data.ApplicationLogic.Extension.KillBitHelper.TryReadKillBitFile(Int32& refreshRate, DateTime& lastModifiedTime)

Failed to create or start performance logs with error: System.Runtime.InteropServices.COMException (0x80041326): The task is disabled. (Exception from HRESULT: 0x80041326)
   at PlaLibrary.DataCollectorSetClass.start(Boolean Synchronous)
   at Microsoft.Exchange.Diagnostics.PerformanceLogger.PerformanceLogSet.StartLog(Boolean synchronous)
   at Microsoft.Exchange.Diagnostics.PerformanceLogger.PerformanceLogMonitor.CheckPerflogStatus(). Performance log: ExchangeDiagnosticsPerformanceLog.

Current User: '[redacted]'
Unique Key: 'S-1-5-21-278578292-3934257875-407118246-1166'
Cookie Name: 'msExchEcpCanary'
Exchange Control Panel detected an invalid canary in cookie from request for URL 'https://[redacted]:444/ecp/default.aspx?exsvurl=1&p=ReceiveConnectors(https://[redacted]/ecp/?exsvurl=1&p=ReceiveConnectors)'.
Canary in cookie: 'NuuDk2vpoU6dua0OnbKdHa4FBaG1x88IEAl1H4aEfHPXq0C357micNuXF5Hg3IjEGXeO1UKF9rQ.'.
Reset canary cookie for user

another one:

There was an error setting up WacConfiguration. Wac will be disabled and we will fall back to stellent. The WacUrlHostName was invalid. Expected a valid Uri. Actual value was ''. Value read from 'OrganizationConfig'

how did this ever ship?

I should also not that NONE, I repeat: NONE of these events have any documentation in the online event log help.

I'm getting the feeling that this product has a single purpose: to push us to migrate to office 365.

Hello Spongman,

Sorry to hear there are a lot of issues on your new Exchange 2013 Server.

Did you install the Exchange Server separately from the DC?

From the error message, it indicates Either the component that raises this event is not installed on your local computer or the installation is corrupted. Therefore, I think there might be a bad installation.

Is it convenient for you to rebuild a new Exchange environment and see if the issue persists?

Thanks,

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

yeah, exchange is installed on a separate box.

the error you quote is a from windows that it shows when there's no error message installed for that event ID. it's a generic error - the important part is the stack trace below - can you tell me what's causing that?

it's not convenient for me to go through all this setup again. i'm not convinced i won't spend a day and end up exactly where i am now. i'm looking for someone to tell me what's causing the timeout, and how to fix it. again, there's no appreciable load on either server.

is there anyone on here that can offset some support beyond reading the KB for me (I'm fully capable of using Google myself) and offering 'did you plug it in?' advice?

• Edited by spongman Wednesday, January 23, 2013 6:13 PM

yeah, exchange is installed on a separate box.

the error you quote is a from windows that it shows when there's no error message installed for that event ID. it's a generic error - the important part is the stack trace below - can you tell me what's causing that?

it's not convenient for me to go through all this setup again. i'm not convinced i won't spend a day and end up exactly where i am now. i'm looking for someone to tell me what's causing the timeout, and how to fix it. again, there's no appreciable load on either server.

is there anyone on here that can offset some support beyond reading the KB for me (I'm fully capable of using Google myself) and offering 'did you plug it in?' advice?

• Edited by spongman Wednesday, January 23, 2013 6:13 PM

yeah, exchange is installed on a separate box.

the error you quote is a from windows that it shows when there's no error message installed for that event ID. it's a generic error - the important part is the stack trace below - can you tell me what's causing that?

it's not convenient for me to go through all this setup again. i'm not convinced i won't spend a day and end up exactly where i am now. i'm looking for someone to tell me what's causing the timeout, and how to fix it. again, there's no appreciable load on either server.

is there anyone on here that can offset some support beyond reading the KB for me (I'm fully capable of using Google myself) and offering 'did you plug it in?' advice?

Hi Spongman,

Sorry for no response to your questions on this thread. I will be glad to check those errors if you still have not found any resolution to the issues that you have reported.

I think there are some networking level issues that are preventing exchange from communcating with DC and causing the problems. Even if both roles are on the same box, the networking layer components are still used.

Thank you

Santhosh

• Edited by mc5694569494 Tuesday, April 16, 2013 7:15 AM

• Edited by mc5694569494 Tuesday, April 16, 2013 7:15 AM

I'll ask the question even though I imagine most of you guys have installed the latest updates but...

Have you installed the latest MS updates for Exchange 2013?

I'll ask the question even though I imagine most of you guys have installed the latest updates but...

Have you installed the latest MS updates for Exchange

Can confirm. This event is happening an all Exchange Servers (3). They are installed seperated from DC and all having CU2 applied.

We are getting those like every 20 minutes and all are related to MSExchangeFrontendTransport. Any help on identifying this errror ?

• Edited by znt GmbH Friday, August 09, 2013 8:12 AM

Can confirm. This event is happening an all Exchange Servers (3). They are installed seperated from DC and all having CU2 applied.

We are getting those like every 20 minutes and all are related to MSExchangeFrontendTransport. Any help on identifying this errror ?

• Edited by znt GmbH Friday, August 09, 2013 8:12 AM

I have made clean installation of Exchange 2013 CU2 and I can also confirm Event ID 65535..

Also a lot of Exchange 2013 CU2 has problem with DatabaseDriveSpaceTrigger. More here.

I have CU1 , 2013 exch. and only recently have started seeing this error, i am guessing some windows update package that is causing this grief. It does not tell you what application is causing the error shows source as "application", whats interesting to note is the IP / port description in the event log.

><Description>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'. The local IP address and port is [::1]:62869. The remote IP address and port is [::1]:890.</Description><AppDomain>MSExchangeFrontendTransport.exe</AppDomain><ExtendedData xmlns

Now what are those ports for ? It's always a socket related message for transport. Is it some Microsoft update feature for exchange that it checks for updates or something but fails ?

PS: anyone here using DPM 2012 to backup exchange ? Could it be related to DPM backups of exchange server ?

• Edited by IamPK Tuesday, August 20, 2013 3:30 PM

I have CU1 , 2013 exch. and only recently have started seeing this error, i am guessing some windows update package that is causing this grief. It does not tell you what application is causing the error shows source as "application", whats interesting to note is the IP / port description in the event log.

><Description>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'. The local IP address and port is [::1]:62869. The remote IP address and port is [::1]:890.</Description><AppDomain>MSExchangeFrontendTransport.exe</AppDomain><ExtendedData xmlns

Now what are those ports for ? It's always a socket related message for transport. Is it some Microsoft update feature for exchange that it checks for updates or something but fails ?

PS: anyone here using DPM 2012 to backup exchange ? Could it be related to DPM backups of exchange server ?

• Edited by IamPK Tuesday, August 20, 2013 3:30 PM

Event ID 65535 seems to occur like once every hour on all new Exchange 2013 installations. I have done 10 installations without failures during the process and on all installations this event occurs regularly. Any updates on this issue?

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

As the hours go forward, I think that Exch2k13 is not stable to put in production enrivonment... Too many issues!
Does anyone idea about when MS will provide a spk to fix a lot of issues that we see every day here???

>>> My opinion.

same here! every excact hour this error occours 3 times.

The Exchange 2013 is a catastrophe!!! I'd never had have so much problems before with microsoft-products as i have now with exchange/office2013/server2012...

same here! every excact hour this error occours 3 times.

The Exchange 2013 is a catastrophe!!! I'd never had have so much problems before with microsoft-products as i have now with exchange/office2013/server2012...

Well maybe after CU 3 comes out it might be better, or might have to wait for CU 4 to fix all the issues exchange 2013 is giving users.

I cannot see major co-operations adopting Exchange 2013, I would like to see what sort of exchange major players use.

I am also facing same Issue. I've installed Exchange Server 2013 CU2. Have you found any fix for that 

Thanks

got the same feeling mate, I also have similar problem with Exc2013, but there is one difference, server hang and become unresponsive. CPU got 100% usage and same with RAM (28 GB)

got the same feeling mate, I also have similar problem with Exc2013, but there is one difference, server hang and become unresponsive. CPU got 100% usage and same with RAM (28 GB)

Same problem here. CPU got 100% usage and server hang and no response for about 15 minutes, then ba

Has anyone found solutions?  I'm having this same issue on Exchange 2013 CU7 which has been in production for several months.  At this point in time the Exchange RPC Client Access Service keeps continuously restarting.  OWA, Outlook, EAC, EMS all down.

What's interesting is that the first error below is referencing a remote site DC.  We have Sites and Services configured properly so it's on Exch is going against a remote site DC.  Only thing I can think of is that DCMAIN holds the FSMO roles and that's why.  We are running Enterprise grade P2P wireless between sites, the pings have somewhat high latency at the moment, however I can browse UNC, Ping, etc without any failures but perhaps what Exchange is doing is much more sensitive, but its hard to imagine 180 seconds is passing without response since all my ping packets etc go through to the primary site DC.  

Source:        MSExchange ADAccess

Event ID:      2389

Process w3wp.exe (FE_Oab) (PID=8128). A request to Directory Server DCMAIN.CORP.COM did not return a result within 180 seconds and is being abandoned.  The search will be retried if possible.

Source:        MSExchange Mid-Tier Storage

Event ID:      10006

Active Manager Client experienced an AD timeout trying to lookup object EXCHSRVR1 in 00:01:00.

Source:        MSExchange Mid-Tier Storage

Event ID:      10006

Active Manager Client experienced an AD timeout trying to lookup object /o=Organization /ou=Exchange Administrative Group (FYDIBOHF44SPDLT)/cn=Configuration/cn=Servers/cn=EXCHSRVRa in 00:01:00.

Chris

EnterpriseIT.co

• Edited by Chris Harris EnterpriseIT 12 hours 34 minutes ago sanitized

Has anyone found solutions?  I'm having this same issue on Exchange 2013 CU7 which has been in production for several months.  At this point in time the Exchange RPC Client Access Service keeps continuously restarting.  OWA, Outlook, EAC, EMS all down.

What's interesting is that the first error below is referencing a remote site DC.  We have Sites and Services configured properly so it's on Exch is going against a remote site DC.  Only thing I can think of is that DCMAIN holds the FSMO roles and that's why.  We are running Enterprise grade P2P wireless between sites, the pings have somewhat high latency at the moment, however I can browse UNC, Ping, etc without any failures but perhaps what Exchange is doing is much more sensitive, but its hard to imagine 180 seconds is passing without response since all my ping packets etc go through to the primary site DC.  

Source:        MSExchange ADAccess

Event ID:      2389

Process w3wp.exe (FE_Oab) (PID=8128). A request to Directory Server DCMAIN.CORP.COM did not return a result within 180 seconds and is being abandoned.  The search will be retried if possible.

Source:        MSExchange Mid-Tier Storage

Event ID:      10006

Active Manager Client experienced an AD timeout trying to lookup object EXCHSRVR1 in 00:01:00.

Source:        MSExchange Mid-Tier Storage

Event ID:      10006

Active Manager Client experienced an AD timeout trying to lookup object /o=Organization /ou=Exchange Administrative Group (FYDIBOHF44SPDLT)/cn=Configuration/cn=Servers/cn=EXCHSRVRa in 00:01:00.

Chris

EnterpriseIT.co

• Edited by Chris Harris EnterpriseIT Thursday, July 30, 2015 6:54 PM sanitized

Shocking to see that there are no solutions or troubleshooting steps whatsoever available yet. I am having the exact same issues on 8 out of 23 Exchange 2013 servers, running CU8.

The difference between those 8 and the other 15 is that the 8 exchange servers showing this problem are connected via vSat (low bandwidth connection) and that those 8 server are only allowed to directly communicate with the Exchange servers at HQ. So it is not a full mesh netwerk; it is partly star and partly full mesh.

The vSat connected sites are the partly star in this case, to minimize the traffic on these low bandwidth connections. something tells me Exchange 2013 doesn't cope well with this.