Link to home
Start Free TrialLog in
Avatar of Christian Hans
Christian HansFlag for United States of America

asked on

Exchange MBX Database drops

We have recently been seeing issues randomly where our users lose connectivity thru OWA and Outlook 2010/2013 when connecting to our Exchange 2013 environment.

I have been seeing numerous errors such as:

Event ID 2138 - MSExchange ADAccess
Process Microsoft.Exchange.EdgeSyncSvc.exe (PID=9616). Exchange Active Directory Provider received a request to connection to domain controller DC01.domain.local but that domain controller is not available. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers. Run the Dcdiag command line tool to test domain controller health.

Event ID 10006 - MSExchange Mid-Tier Storage
Active Manager Client experienced an AD timeout trying to lookup object '1f7f97fb-a752-496c-8d32-925ead0ae9ab' in 00:01:00.

Event ID 10006 - MSExchange Mid-Tier Storage      
Active Manager Client experienced an AD timeout trying to lookup object 'DAG01' in 00:01:00.

Event ID 1006 - MSExchangeDiagnostics
The performance counter '\\EXCH05\MSExchangeIS Store(db06)\% RPC Requests' sustained a value of '100.00', for the '10' minute(s) interval starting at '6/9/2015 3:22:00 PM'. Additional information: None. Trigger Name:StorePercentRpcRequestsTrigger. Instance:db06

Where would you recommend troubleshooting steps to begin?

This is an Exchange 2013 Server running on VMware Infrastructure. The MBX databases are presented from our NetApp filers.

Thanks in advance.
SOLUTION
Avatar of Will Szymkowski
Will Szymkowski
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Jeff Rodgers
Jeff Rodgers

Off the hop one question I need to askt... how many domain controllers do you have?   Exchange can absolutely hammer AD.... as the number of mailboxes increases so too does the pounding.   Most of the above errors can be caused by a slow connection to AD.  

The solution would be to add additional Domain Controllers (I tend to make most of my DC's Global Catalogs as well).
Avatar of Christian Hans

ASKER

4 out of the 5 DCs we have at this site are Global Catalog servers...

I will run those commands shortly and post an update. Thanks.
And How many mailboxes?
Just under 10,000 mailboxes
1 DAG
3 Mailbox Role  servers
6 Mailbox Databases
I think it needs to be taken to Microsoft...and it all started in the month of April. i saw this issue in Two different Prod setups and i was reported the same issue from different organization. Only solution was to reboot the server where event was generating.
That is a sizeable deployment.   Are 10,000 mailboxes being well enough served by the 4 Global Catalogs in the site?

Do you have any performance monitors installed that would tell you what is happening on these servers?   It smacks of performance bottlenecks in its communications with AD.
Ive opened a ticket with Microsoft support. So far we have been sending logs back and forth to try to determine the cause of this issue. 10,000 is a larger number for 4 global catalog servers but it should be adequate no?

Im not running performance monitors on there right now, but Id like to turn something on for the next 7 days if possible, monitoring the growth naturally. What specific performance monitors should I be looking at?
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial