locked
Exchange 2003 DSACCESS errors in Exchange Best Practice Analyzer RRS feed

  • Question

  • I am running Exchange 2003 SP2 with Windows 2003 DC/GC's and when I run the Exchange Best Practive Analyzer I continually receive the following DSACCESS errors:

    An error occurred during round-trip calculation between Exchange server Exchange2.domain.local and Active Directory server DC2.domain.local. The ping command returned the error '11010'.

    An error occurred during round-trip calculation between Exchange server Exchange3.domain.local and Active Directory server DC1.domain.local. The ping command returned the error '11010'.

    --

    My Exchange Servers and 2 domain controllers are all in the same network subnet and my Exchange Servers can ping these DC/CG fine (equal or less than 1 ms).  These are the only 2 DC/GC's that my Exhange Servers are accessing as well and I don't see any other issues.

    Does anyone know how to resolve these DSACCESS errors?  Is this something I really need to be concerned about?  Will increasing the amount of RAM on the DC's help or adding another DC/GC help?

    Thanks

     


    Steve
    Monday, April 18, 2011 5:15 PM

All replies

  • Have you updated the BPA with latest updates?

    Ensure the DAAccess is functioning properly by following the article below

    http://www.msexchange.org/tutorials/Closer-Look-Directory-Service-Access-DSAccess-Part2.html

    Monday, April 18, 2011 5:37 PM
  • Yes. I have the BPA check for updates every time I run it.  I am not sure what I can check to resolve this issue.
    Steve
    Monday, April 18, 2011 5:44 PM
  • Following the article, you can make sure all the dcs are discovered in toplogy discovery. Ensure that the LDAP serach times are not above the recommended thresholds. Run DCdiag on the domain controllers to ensure there are no issues.
    Monday, April 18, 2011 5:46 PM
  • DCDIAG produces the following errors.  It doesn't seem to be a big problem. Any ideas?

     

    --------------------------------------------------
    systemlog Tests:
    --------------------------------------------------
             An Error Event occured.  EventID: 0x00000457
                Time Generated: 04/18/2011   14:20:42
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x00000457
                Time Generated: 04/18/2011   14:20:42
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x00000457
                Time Generated: 04/18/2011   14:20:43
                (Event String could not be retrieved)
             An Error Event occured.  EventID: 0x00000457
                Time Generated: 04/18/2011   14:20:43
                (Event String could not be retrieved)
             ......................... TGI-DC2 failed test systemlog


    --------------------------------------------------
    DNS Tests - DC2:
    --------------------------------------------------

    DNS Tests are running and not hung. Please wait a few minutes...
             Test results for domain controllers:
               
                DC: dc2.domain.local
                Domain: domain.local

                     
                   TEST: Forwarders/Root hints (Forw)
                      Error: Root hints list has invalid root hint server: a.root-servers.net. (198.41.0.4)
                      Error: Root hints list has invalid root hint server: b.root-servers.net. (192.228.79.201)
                      Error: Root hints list has invalid root hint server: c.root-servers.net. (192.33.4.12)
                      Error: Root hints list has invalid root hint server: d.root-servers.net. (128.8.10.90)
                      Error: Root hints list has invalid root hint server: e.root-servers.net. (192.203.230.10)
                      Error: Root hints list has invalid root hint server: f.root-servers.net. (192.5.5.241)
                      Error: Root hints list has invalid root hint server: g.root-servers.net. (192.112.36.4)
                      Error: Root hints list has invalid root hint server: h.root-servers.net. (128.63.2.53)
                      Error: Root hints list has invalid root hint server: i.root-servers.net. (192.36.148.17)
                      Error: Root hints list has invalid root hint server: j.root-servers.net. (192.58.128.30)
                      Error: Root hints list has invalid root hint server: k.root-servers.net. (193.0.14.129)
                      Error: Root hints list has invalid root hint server: m.root-servers.net. (202.12.27.33)


    Steve
    Monday, April 18, 2011 6:38 PM
  • Please increase diagnostic logging level of MSExchangeTransport to Maximum, reproduce the issue, and then check the issue again

    Please make sure that the NIC driver has been update to the latest patch

    Please apply the hotfix below on the server

    An update to turn off default SNP features is available for Windows Server 2003-based and Small Business Server 2003-based computers

    Resources:

    Advanced network adapter troubleshooting for Windows workstations

    Understanding and Troubleshooting Directory Access


    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.
    • Proposed as answer by Alan.Gim Monday, April 25, 2011 3:26 AM
    • Marked as answer by Alan.Gim Tuesday, April 26, 2011 1:59 AM
    • Unmarked as answer by Steve March Tuesday, April 26, 2011 1:28 PM
    • Unproposed as answer by Steve March Tuesday, April 26, 2011 1:28 PM
    Friday, April 22, 2011 8:22 AM
  • I checked the registry and the EnableTCPChimney, EnableRSS, and EnableTCPA settings are already set to 0.  I turned on diagnostic logging and I am seeing the following errors.  Do you think I need another GC in the site?  It seems to be going to other DC's outside of the AD site.

     

    Event Type:        Error
    Event Source:    MSExchangeDSAccess
    Event Category:                LDAP
    Event ID:              2061
    Date:                     4/26/2011
    Time:                     8:50:03 AM
    User:                     N/A
    Computer:          EXCH3
    Description:
    Process MAD.EXE (PID=1552). An LDAP search call failed - Server=dc1.domain.local Error code=80040957. Base DN=, Filter=(legacyExchangeDN=), Scope=2.

    For more information, click http://www.microsoft.com/contentredirect.asp.
    --
    Event Type:        Error
    Event Source:    MSExchangeDSAccess
    Event Category:                LDAP
    Event ID:              2061
    Date:                     4/26/2011
    Time:                     8:38:35 AM
    User:                     N/A
    Computer:          EXCH3
    Description:
    Process MAD.EXE (PID=1552). An LDAP search call failed - Server=dc2.domain.local Error code=80040957. Base DN=, Filter=(legacyExchangeDN=), Scope=2.

    For more information, click http://www.microsoft.com/contentredirect.asp.
    --
    Event Type:        Information
    Event Source:    MSExchangeDSAccess
    Event Category:                Topology
    Event ID:              2085
    Date:                     4/26/2011
    Time:                     8:01:45 AM
    User:                     N/A
    Computer:          EXCH3
    Description:
    Process MAD.EXE (PID=1552). No Global Catalog server is up in the local site 'Site1'. DSAccess will use the  following out of site Global Catalog servers:
    dc4.domain.local
    dc3.domain.local


    For more information, click http://www.microsoft.com/contentredirect.asp.


    Steve
    Tuesday, April 26, 2011 1:27 PM