• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 482
  • Last Modified:

Microsoft Exchange Information Store and Microsoft Exchange MTA Stacks services won't start on reboot.

Microsoft Exchange Information Store and Microsoft Exchange MTA Stacks services won't start on reboot.

Troubleshooting completed:

-  I can start the services manually once logged into the server, Exchange runs normally after that.
-  The services are set to start 'automatic'
-  All the dependency services for both services start fine.
-  The services log in as a local system account.  
-  The services won't start with a net start batch file either.  I can only start them through the 'services' mmc.  
-  The DCOM permissions are set at their default level.  
-  I have used and not used these switches in boot.ini (either way makes no difference) /3GB /USERVA=3030
-  I do get this 'error' listed below:

Event Type:      Error
Event Source:      Service Control Manager
Event Category:      None
Event ID:      7001
Date:            7/6/2006
Time:            8:15:30 PM
User:            N/A
Computer:      ORLDC1
Description:
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.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Thanks  for the help!!
 
0
Biziteks
Asked:
Biziteks
  • 3
  • 3
1 Solution
 
kristinawCommented:
does anything else run on this server? is it a dc, etc?
what type of antivirus do you run? make sure it's fully updated and all exchange exclusions are properly set. a good test would be to completely disable it, set it to disabled in services and try a reboot.

for good measure, run an exbpa and see what it flags, it should tell you if your exclusions are not set properly.
http://www.microsoft.com/technet/prodtechnol/exchange/downloads/2003/analyzers/default.mspx

kris.
0
 
BiziteksAuthor Commented:
It is a DC.
It runs Symantec Corp Anti-virus.  
It runs Backup Exec.
ALL Windows and Exchange updates are installed.  

I haven't tried to disable anti-virus services and reboot it.  I will give that a shot.  Thank you!!
0
 
kristinawCommented:
is this ex2000 or 2003?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
BiziteksAuthor Commented:
EX2003 and Windows Server 2003.  
I will have to try the disabling of the Symantec this weekend and respond back by Monday.
0
 
NetoMeter ScreencastsCommented:
I would suggest to set Diagnostic Logging for these services to the maximum level and check what error messages you get first.

Dean
0
 
BiziteksAuthor Commented:
I disabled the Symantec services this weekend, rebooted, and Exchange came up fine.  So it looks like we found the problem, however, the solution still eludes me.

I updated the Symantec anti-virus.
I configured the exclusions.
I ran Exchange best practices analyzer and fixed the critical errors (there were a couple of other informational notices, but nothing related to this issue).  
I rebooted and am still having the same problem.  

If you have any other ideas, please let me know.  I am going to call Symantec today and see if they can help.  


Thank you Kris and Dean for your help!!!!

Lee
0
 
kristinawCommented:
Lee,

Yes, I think a call to symantec would definitely be in order at this point. you may need to set some other exlusions based on the fact that it's a dc.

kris.
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

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