Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1003
  • Last Modified:

Exchange 2K3 information store not automatically starting after system reboot.

We have just recently starting having problems with the Exchange info store not starting automatically after system reboot. Everything runs fine after manually starting the MTA stacks service. This is running on a 2003 Small Business Server. I am seeing the following events in the system log on reboot...

LSASRV 40960 The Security System detected an authentication error for the server HOST/MYDC.  The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request."
 (0xc000005e)".

3 minutes later I see the following:

SERVICE CONTROL MANAGER 7001 The Microsoft Exchange Information Store service depends on the Microsoft Exchange System Attendant service which failed to start because of the following error:
The operation completed successfully.

and also...

SERVICE CONTROL MANAGER 7001 The Microsoft Exchange MTA Stacks service depends on the Microsoft Exchange System Attendant service which failed to start because of the following error:
The operation completed successfully.

I have verified that DNS is configured properly (pointing to itself first, then our other Domain Controller). All dcdiag and netdiag tests pass. 2003 SBS SP1 and Exchange 2003 SP2.


0
FIFBA
Asked:
FIFBA
  • 2
  • 2
1 Solution
 
Alan Huseyin KayahanCommented:
  Hi FIFBA
       Do you encounter any time service errors? You encounter these on SBS if time service is not started yet while exchange services try to start.

Regards
0
 
FIFBAAuthor Commented:
I do see some w32time errors. This server has been configured to sync time via an external time source per MS article 816042. Do you think that this is what is causing the problem with the info store? Do I need to configure the server to use its internal hardware clock in order for services to start successfully?
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
"I have verified that DNS is configured properly (pointing to itself first, then our other Domain Controller). "

Actually in an SBS Environment, that is not a properly configured DNS.  You should ONLY be pointing to the SBS for DNS, as that's all that's needed.  If it can't reach itself it won't need to try anywhere else.

Also, the MTA Stacks Service is usually disabled on an SBS by default.  Why do you have it enabled?

Jeff
TechSoEasy
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
One other thing... how large is your Exchange Store?  If it's hitting the 16GB limit, it won't start automatically.  If you want to increase it beyond 16GB (since you've applied SP2) you need to edit the registry to allow that to happen.

See:  http://www.msexchange.org/tutorials/Explaining-Database-size-limit-changes-Exchange-2003-Service-Pack-2.html

Jeff
TechSoEasy
0
 
FIFBAAuthor Commented:
I set MTA stacks service to disabled and removed 2nd DNS entry on the SBS. Unable to bounce server now, will try later...
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now