Re: Exchange MAD.EXE Errors
- From: "Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 30 Nov 2005 16:12:22 -0500
I think these are just a result of running Exchange on a domain controller -
services start and stop at different rates. Exchange System Attendant
(mad.exe) was looking for another service that had not started yet (or had
already stopped), so it logged that error. As long as these are happening
at system startup or shutdown, and there are no symptoms other than the
error itself, you can safely ignore them.
"AZ Steve" <AZSteve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6000FD9C-64CA-4656-B264-6FEF7FEC9B12@xxxxxxxxxxxxxxxx
>I have a SBS2003 SP1 network. I have started seeing random Exchange
> "Topology" event id 2102 errors:
>
> Process MAD.EXE (PID=3988). All Domain Controller Servers in use are not
> responding: (servername).(domainname).local
>
> When I access the supplied link for more info, I get:
>
> Explanation
> This event indicates that the DSAccess component on the Exchange server
> was
> unable to find any domain controllers suitable for Lightweight Directory
> Access Protocol (LDAP) queries. This can result in the halting of mail
> flow,
> so it should be investigated immediately.
>
> The most likely cause is that the Kerberos ticket timed out. When the
> Kerberos tickets that are associated with the LDAP connections time-out,
> all
> LDAP connections get errors because the security contexts have failed and
> these connections must be re-established. If there are no other servers to
> obtain a ticket from while this re-establishment takes place, then the
> error
> occurs.
> The Manage Auditing and Security Log right (SeSecurityPrivilege) was
> removed
> for the Exchange Enterprise Servers domain local group on some or all of
> the
> domain controllers.
> All intra-site and extra-site domain controllers are down or network
> problems have rendered them unreachable.
>
>
> User Action
> Try to have at least two domain controllers (configured as global
> catalogs)
> in a SITE. This is for failover purposes.
> Run the Exchange setup with the /DOMAINPREP switch. This will reassign the
> SeSecurityPrivilege right to the Exchange Enterprise Servers Group.
> Check the event log for DSAccess Event ID 2080 (may need to increase the
> DSAccess logging level to record this event). The detail in that event
> will
> help determine if domain controllers have been contacted that are
> unsuitable
> for some reason. They can then be corrected.
> Look for DSAccess Event ID 2070 in the event logs. These events will
> detail
> why each domain controller has become unsuitable. Correct as necessary.
>
> Since this is a single server SBS domain, there are not other servers for
> LDAP queries. The last one happened at 3:44 am but other occurances are
> completley random times of day or night. The server is a Dell PE800 2.8G
> with
> 1G memory and Trend 2.0. There dosent seem to be issues with mail flow.
>
> Thie dosent seem to have any impact on system operations.Does anyone have
> a
> cure (besides second server) for this or should it be ignored?
>
> All help appreciated.
.
- Follow-Ups:
- Re: Exchange MAD.EXE Errors
- From: AZ Steve
- Re: Exchange MAD.EXE Errors
- Prev by Date: Re: EventID 1030 & 1058 after Desaster Recovery Restore
- Next by Date: CAL'S question concerning 2 different versions of 2003 server.
- Previous by thread: Re: EventID 1030 & 1058 after Desaster Recovery Restore
- Next by thread: Re: Exchange MAD.EXE Errors
- Index(es):
Relevant Pages
|
