Re: The MAD Monitoring thread was unable to read its configuration from the DS

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thanks for your prompt reply. I got an education investigating your
suggestion:-))) Since this is an SBS 2003 server, a good share of the magic
of a normal Exchange install was done automagically.

I ran adprep /forestprep and /domainprep from the 2003 SBS server setup
disk. Was this what you meant?

Both of them went on strike and said the job was already done so they
weren't about to do it again. (or words to that effect.)

More suggestions would be appreciated.

Regards,
Al

"Nuevo" <imaneophyte@xxxxxxxxx> wrote in message
news:%23n0tt5%23KGHA.3944@xxxxxxxxxxxxxxxxxxxxxxx
Permissions are definitely screwed up and the five minute interval
indicates an AD replication issue. So the question is what has changed in
your environment? One relatively simple solution might be to rerun
forestprep and domainprep. This will reset permissions and might fix your
problem.

Nue
"Al Christoph" <ac2@xxxxxxx> wrote in message
news:%23pbRpt6KGHA.3728@xxxxxxxxxxxxxxxxxxxxxxx
I am running Exchange 2003 sp2 on SBS 2003 sp1.

Every 5 minutes I get a pair of error conditions which I strongly suspect
are related:

Event Type: Error
Event Source: MSExchangeSA
Event Category: Monitoring
Event ID: 9098
Date: 2/2/2006
Time: 10:21:33 PM
User: N/A
Computer: AC2M6
Description:
The MAD Monitoring thread was unable to read its configuration from the
DS,
error '0x80070005'.

The error points to permission denied or some such thing. At about the
same
time (though often off by a couple of minutes) but with the same
frequency,
I'm getting security violations:

Logon Failure:
Reason: Unknown user name or bad password
User Name: <computer name>$
Domain: 3BEARS
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM
Workstation Name: <computer name>
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: -
Source Port: -

I suspect that the two are tied together and that somehow the MAD service
is trying to use an inappropriate user or that the user doesn't have the
appropriate permissions.

QUESTIONS:
A. Does this interpretation make sense?
B. What do I need to configure to fix this issue?

The research I've done suggests that this was a problem in the past for
others but has long since been fixed by service packs.

The system boots cleanly and chugs along nicely otherwise.

Regards,
Al





.

Relevant Pages