exchange 2010, Active directory

pramod1
pramod1 used Ask the Experts™
on
I am getting error on my exchange server -HIGH LDAP search time .sustained for 2 minutes .yellow (>100 milliseconds)

what should I do, should I ignore
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Will SzymkowskiSenior Solution Architect
Most Valuable Expert 2015
Top Expert 2015

Commented:
Did this event just start happening? How many DC do you have in the site where Exchange is hosted? Basically it is stating that it cannot keep up to the queries that users are requesting. I would check to see what your DC are doing and make sure that they have available resources as well (CPU and memory). You should also check and make sure the you network latency is also good.

Checking DC replication also wouldn't hurt. Probably not a good idea to just let this go. Are your clients complaining?

Will.

Author

Commented:
this error was generated 3 hrs back and is from exchange relay server

Author

Commented:
how do I check network latency
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Will SzymkowskiSenior Solution Architect
Most Valuable Expert 2015
Top Expert 2015

Commented:
A simple ping can show the network latency. You can also use pathping as well.

I personally think it is to do with the resources on the DC's

Will.

Author

Commented:
what should be ldap normal search time

Author

Commented:
as I did tracert to google.com , all hops show less than 30 ms

Author

Commented:
what should be ldap normal search time , all dc are in site

Author

Commented:
if tracert  is less than 25ms , what should be the ldap search time?
Will SzymkowskiSenior Solution Architect
Most Valuable Expert 2015
Top Expert 2015

Commented:
you get 25ms on the same LAN? That seems high.

Or is this over a MPLS or IPSec VPN?

What about the resources on the DC's?

Will.
Senior Engineer
Commented:
On your DC change the following registry key.

HKLM\SYSTEM\CurrentControlSet\services\NTDS\Diagnostics

Change 15 Field Engineering to a Value of "5"

Once this is set look in the Directory Services log for event ID 1644.


If this Event ID shows up install HOTFIX http://support.microsoft.com/kb/2862304 on all DCs that Exchange uses.

LDAP Read and Search times should be under 15 with spikes not higher than 50.

To check for high LDAP times, run ExPerfWiz for about an hour or two and then open up the data and look at MSExchange ADAccess Domain Controllers and then LDAP Read Time and LDAP Search Time.

https://experfwiz.codeplex.com/

You didn't say what version of Windows you are running for your Domain Controllers.  The above applies to 2008 R2 SP1 and above.  If you are using 2003 you need to upgrade your DCs and apply the above hotfix.

Author

Commented:
tracert to google  took less than 10ms
Scott CSenior Engineer

Commented:
Just saw you accepted my solution.

Glad to have been able to help you so quickly.

When I was an Exchange Escalation engineer for MS this was the first thing we did when seeing high LDAP times.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial