none
Event id 2389 RRS feed

  • Question

  • We are running in 4Passive / 1Active Cluster of Exchange 2003

    with 2 DC Windows Server 2008 R2 Enterprise, (01 & 02) where 02 running in VMWARE (but disk is in local not in SAN)

    Occasionally we are getting lot of event id 2389 in all the exchange 2003 maximum 10 minutes continuously during that time exchange stops working.

     

    Wednesday, June 22, 2011 11:17 AM

Answers

  • Hello Shaik

    Is the domain controller that is noted in the event constant or does it show both domain controllers? If it is one primarily I would monitor this server with the articles below.

    http://www.activedir.org/Articles/tabid/54/articleType/ArticleView/articleId/49/Default.aspx

    If it is both I would reiterate the network communications issues.

    1. check that the nics and switches are hard coded to a speed- not auto.

    2. if networks are teamed - you might want to try standard nic config

    3. check nic drivers for updates

    4. remove SNP features from exchange and dcs (scalable networking. RSS and tcp offload)

    Here is an explanation of what should be triggering this 2389: http://technet.microsoft.com/en-us/library/aa995664(EXCHG.80).aspx

    High LDAP search latencies can be caused by high remote procedure call (RPC) latencies and by increasing queues. High LDAP search latencies generally indicate one of the following problems:

    • A performance problem with the network connection to the domain controller.
    • Performance problems with the domain controller itself.


    Essentially we sent a request to the dc and we do not get a response - so you need to look on the dc/network side to resolve. Exchange is only waiting for a response.  

    • Proposed as answer by Rowen-Xu Tuesday, June 28, 2011 7:21 AM
    • Marked as answer by Rowen-Xu Friday, July 1, 2011 7:12 AM
    Monday, June 27, 2011 2:34 PM

All replies

  • i,

    Sounds as if the exchange servers have problhttp://www.microsoft.com/technet/support/ee/transform.aspx?

    http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=6.5.6940.0&EvtID=2389&EvtSrc=MSExchangeDSAccess&LCID=1033

    Leif

     

    Wednesday, June 22, 2011 11:27 AM
  • Hi Leif

    I already referred the link but unable to come any conclusion.

    Regards

    Shaik

    Wednesday, June 22, 2011 11:32 AM
  • Hi Shaik,

    It might due to some network issue the connectivity was lost or delayed.

    So just make sure your network will be ok all the time and at the same time verify that whether this event recur.

    Best Regards!


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Thursday, June 23, 2011 2:02 AM
  • Jidan

    I confirmed there is no network issue also it re occurs randomly

    Thursday, June 23, 2011 9:08 AM
  • Hello Shaik

    Is the domain controller that is noted in the event constant or does it show both domain controllers? If it is one primarily I would monitor this server with the articles below.

    http://www.activedir.org/Articles/tabid/54/articleType/ArticleView/articleId/49/Default.aspx

    If it is both I would reiterate the network communications issues.

    1. check that the nics and switches are hard coded to a speed- not auto.

    2. if networks are teamed - you might want to try standard nic config

    3. check nic drivers for updates

    4. remove SNP features from exchange and dcs (scalable networking. RSS and tcp offload)

    Here is an explanation of what should be triggering this 2389: http://technet.microsoft.com/en-us/library/aa995664(EXCHG.80).aspx

    High LDAP search latencies can be caused by high remote procedure call (RPC) latencies and by increasing queues. High LDAP search latencies generally indicate one of the following problems:

    • A performance problem with the network connection to the domain controller.
    • Performance problems with the domain controller itself.


    Essentially we sent a request to the dc and we do not get a response - so you need to look on the dc/network side to resolve. Exchange is only waiting for a response.  

    • Proposed as answer by Rowen-Xu Tuesday, June 28, 2011 7:21 AM
    • Marked as answer by Rowen-Xu Friday, July 1, 2011 7:12 AM
    Monday, June 27, 2011 2:34 PM
  • Hi Shaik,

    Any update? Have you tried Dan's suggestion?

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Thursday, June 30, 2011 2:20 AM