Hello there,
I'm the administrator for a small (30-40) user company. We're running SBS 2003, utilizing Exchange, AD, and SQL on the box. the box is a Dell poweredge, dual 2.4 ghz xeon, 2gb RAM. RAID1 on OS, RAID5 for storage, plenty of space available on both drives. Drives were replaced 1 year ago.
I've begun having to reboot the server every weekend because of a weird error that I can't pin down. What happens is that the server doesnt actually crash, but it becomes hung due to some sort of process thread that just eats up all the resource, which seems to cause lots of other things to fail (LDAP binds, Exchange processes, DNS processes, etc), so its hard to weed out what the actual issue is.
The end result though, is that I can't get into the server via remote desktop, so I end up having to physically reboot it. Everything works as normal when I do, but I find that I have to go into the licensing wizard and restore all my licenses after the reboot.
It always seems to happen on the weekend, too - which is really odd and makes me think that some scheduled process is whats doing it, but I've checked and I have no scheduled tasks running on the weekend, there shouldnt be any SQL jobs running then either. I'm at a loss.
So you might wonder why I think mad.exe is involved. Basically Im going back to the first entry in the event viewer application log before everything goes south. That entry is:
The MAD Monitoring thread was unable to read the state of the services, error '0x80010100'.
For more information, click
http://www.microsoft.com/contentredirect.asp.
After that, lots of other things fail - like this:
Process MAD.EXE (PID=1760). All Domain Controller Servers in use are not responding:
And..
LDAP Bind was unsuccessful on directory xxxxxxxx for distinguished name ''. Directory returned error:[0x51] Server Down. DC=corp,DC=xxxxxxxx,DC=xxx
(domain info xx'ed out deliberately)
The big one though, is the system log - each time this happens, I get literally THOUSANDS of these entries:
An I/O operation initiated by the Registry failed unrecoverably. The Registry could not read in, or write out, or flush, one of the files that contain the system's image of the Registry.
So - I dont know whats happening here. This installation has been stable for a long time, and I really dont want to have to rebuild it, but I haven't done any significant changes to it that would cause the OS to suddenly go unstable like this (no new software, etc). I try to change as little as possible here. I did defrag the information store for Exchange a little while back to reclaim some space and to keep it from getting over the Exchange quota (11-12gb, whichever it is), but that was it. I've done that before and it never resulted in anything like this.
So - any help would be greatly appreciated. Thanks!
Start Free Trial
