MSExchangeDSAccess

[Grant007]

Hi
I have Exchange 2000 with SP3 on it and everyday with out fail exchnage freezes for around 5 or 10 minutes. I have 3 DCs nothe network. When looking at my exchange event logs i get event IDs: 2102, 2103, 2084, 2095 in the APP log. These are the event logs:

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 10/23/2003
Time: 5:26:30 PM
User: N/A
Computer: BREXCH3
Description:
Process MAD.EXE (PID=2316). All Domain Controller Servers in use are not responding:
brdc1.CHHNET.COM
brdc2.CHHNET.COM
brdc3.CHHNET.COM
londc1.CHHNET.COM



For more information, click

http://www.microsoft.com/contentredirect.asp.

I get a similar one saying:

Process MAD.EXE (PID=2316). All Global Catalog Servers in use are not responding:
brdc1.CHHNET.COM
brdc2.CHHNET.COM
brdc3.CHHNET.COM
londc1.CHHNET.COM

these are the two events that i get.

shortly after exchange comes back online i get this event log:

Event ID:9154 Source: MSExchangeSA
DSACCESS returned an error '0x80004005' on DS notification. Microsoft Exchange System Attendant will re-set DS notification later.


Please Please HELP!!!! thanks (in advance)

 

[compgirlfhredi]

This event is displayed in the Application Log when the Exchange server is unable to access a Domain Controller (DC). For example, this event may occur when a DC is restarted, if that is the ONLY DC in the site that the Exchange server belongs to.
The most likely cause for this Event is that the Kerberos ticket timed out. This typically happens in a topology that has a single DC. When the Kerberos tickets that are associated with the Lightweight Directory Access Protocol (LDAP) connections time out, all LDAP connection attempts show errors because the security contexts have failed. These connections must be re-established. Because there is only one domain controller in this topology, there are no other servers to obtain a ticket from while this re-establishment takes place. Therefore, the error occurs.

Incorrect DNS configuration.

User Action
The client LDAP connections should get re-established automatically and the errors should go away once this re-establishment has taken place. It is recommended that additional DCs be installed in the site in order to avoid such errors.
Ensure that both the Primary and Alternate DNS Servers listed in the Exchange Server IP Properties are up and running and have been configured properly.
Check the DC to ensure that it is running properly. For example, ensure that is not restarting unnecessarily.

=====================================================
You can find additional information on this topic in the following Microsoft Knowledge Base articles:
• XADM: Event ID 2102 and Event ID 9154 Error Messages Are Logged
The following event ID error messages may be logged in the Application event log of an Exchange 2000 server: Event ID 2102 Source MSExchangeDSAccess Category Topology Process MAD.EXE. All Domain Controller Servers in use are not responding: myserver ....
• PRB: Error Message: All Domain Controller Servers in Use Are Not Responding
When you run Exchange 2000 Server in a single domain controller topology, you receive the following error message: Event ID 2102 Process MAD.EXE (PID=1448). All Domain Controller Servers in use are not responding. Often followed by Event ID: 9154...

 

[Grant007]

I do have more than 1 DC in my network. I have 4 DCs on my network at present. In the event log it comes up saying that all DCs are unavaliable and one of these DCs is plugged into the same switch as my exchange server. If you have any more helpful tips please send them to me. Thanks in advance.

 

[compgirlfhredi]

re-run /DOMAINPREP from the Exchange 2000 Service Pack 3 CDROM,and see if that helps. Microsoft claims the 2102 is a benign error code and shows iup mainly if you are running in a single GC/DC environment. If you have converted Exchamge to native mode, disabling "automatic network topology discovery" in DSAccess tab may help. One user found that this problem may occur if Exchange 2000 is installed on a global catalog server and no domain controller is available. They re-installed Exchange Service Pack 3 and the problem was solved. Another user found the a 'Compaq" server was their problem. Changing out NICS was an option.Apparently in the mean time, they hardcoded the DSAccess Tab with the information returned in the 2050 Information messages collected by increased DSAccess/Topology logging. This provides the full table of discovered servers so you can hardcode that info into DSAccess.