Exchange 2003 Fails every few days

Hi All,

Have a single 2003 SBS server in an office.  All patches have been installed.  Every few days Exchange fails.  Each time a reboot of the server fixes the issue.

When it happened this morning I checked the Event Viewer and the following Errors showed (in order of appearence)

Error ID 8026  MSEchangeAL  Process STORE.EXE (PID=4340). All the DS Servers in domain are not responding
Error ID 8026  MSEchangeAL LDAP Bind was unsuccessful on directory 2k3server.fa.local for distinguished name ".Directory returned error:[0x34] Unavailable.
Error ID 2104  MSExchangeDSAccess  Process STORE.EXE (PID=4340), All the DS Servers in domain are not responding.
Error ID 2102  Process MAD.EXE (PID=3468)  All Domain Controller Servers in use are not responding: 2k3server.fa.local
This error last occurred 7 days ago and the log then had hundreds of the same errors as above.

Would really appreciate any thoughts on what might be going on here.  I'm not generally a tinkerer when it comes to this server so other than installing regular updates I don't touch the thing enough to break it!



Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

It looks like it's losing communication with your AD servers.

This could be caused by network issues on your Exchange server or your AD server going AWOL briefly.

Check out all the IP settings on the Exchange server to make sure they are correctly setup.  Check the event log for other errors under the SYSTEM section for around the time Exchange throws a fit - there are likely to be other entries which may help identify this fault.

Just noticed that you've only got one server so my first two comments are irrelevant (left it in though so others can see).

Check the SYSTEM log for other errors at the same time.
Here are a couple of things you can do:

Go to the server properties and then go to "Directory Access Tab" and remove the Checkbox that says "Automatically Discover Servers". Do it for all Config, Domain Controller and Global Catalogue by choosing them via the drop down menu. Once done, Click on Add button and add your local AD server as your Domain Controller, GC and Config. Click OK and then restart the System Attendant Service.

This whole process is called Hard Coding Directory Servers. This will ensure that DSAccess Component always connects to the local SBS server and any cache or stale information will not affect the DS queries.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
amlydiateAuthor Commented:
Thanks a lot Hilal, have made the changes you have suggested and will monitor over the next few days and let you know if it has worked.  really appreciate your help.

All the best

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Vishal BreedProgram ManagerCommented:
If this doesn't help,
1 - run dcdiag and netdiag - paste the result here.
2 - run exbpa and fix all issues related to AD, DNS
Is this the only server on the network? I.e. is this server the only DC?
when you say the services fail in the morning, what has occured before they fail? A system reboot or full backup? The event logs should be able to tell you what has happened.

Otherwise make MsExchangeSA dependon the Netlogon service so that exchange will not try and mount until the domain is available.
amlydiateAuthor Commented:
Excellent that fixed the problem, really appreciate your help!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.