Solved

Exchange services sometimes fail to start after server reboot

Posted on 2015-01-29
10
115 Views
Last Modified: 2015-02-10
Seems to happen at random. We do a reboot every night and most nights its all ok - some nights certain services just fail to start.

For instance, looking at event log for last night, we had:-

- MS Exchange Information Store service terminated with error 0
- Timeout waiting for MS Exchange Host service to connect
- MS Exchange Host service failed to start due to the following error: Did not respond to the start request in a timely manner.
- MS Exchange Transport Log Search service hung on starting.

Any ideas? How to prevent and/or recover these services?
At the moment, they remain stopped until someone manually starts them.
0
Comment
Question by:paul williams
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 4
10 Comments
 
LVL 24

Expert Comment

by:VB ITS
ID: 40577578
Try changing the Startup type of the problematic services to Automatic (Delayed Start), more specifically the Information Store and Transport services.

Microsoft even recommend this if your server has issues starting these services at startup: http://blogs.technet.com/b/nking/archive/2008/11/17/quick-tip-setting-exchange-store-and-transport-to-delayed-start.aspx
0
 

Author Comment

by:paul williams
ID: 40577667
Windows 2003 - thats 2008 only isnt it?
0
 
LVL 24

Expert Comment

by:VB ITS
ID: 40578980
Oh, Server 2003. Try the steps in this article then: http://support.microsoft.com/KB/193888
0
Edgartown IT Case Study

Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!

 

Author Comment

by:paul williams
ID: 40579605
Hmmm. Working out the dependencies is the issue then.
0
 
LVL 24

Expert Comment

by:VB ITS
ID: 40580060
If that's a bit too much for you then you can look at using the BootPause registry key instead. See Method 3 in this article: http://support.microsoft.com/kb/940845

You could theoretically create the BootPause key in the registry to delay the startup of all the Exchange services if you wanted.
0
 

Author Comment

by:paul williams
ID: 40590597
No answer here.
0
 

Author Comment

by:paul williams
ID: 40590633
I've requested that this question be closed as follows:

Accepted answer: 0 points for paul williams's comment #a40590597

for the following reason:

No easy way to do this
0
 
LVL 24

Expert Comment

by:VB ITS
ID: 40590634
Paul, did you even try the BootPause registry key or any of the steps outlined in the Microsoft KB article I posted previously?

You asked for a solution to your problem, when a potential solution is presented to you you decide it's too hard and close the question instead. If you aren't willing to put the effort into trying to resolve this issue then please indicate that you want a 'simple' way to achieve this when you ask your original question or at the very least give us a chance to provide you with alternative options.
0
 

Accepted Solution

by:
paul williams earned 0 total points
ID: 40590676
Sorry yes I did try BootPause and it made no difference. It seemed to work but a day later we had the same - it seems to happen at random.

Our servers get rebooted every night so what I've done to fix this is:-

1) Add scheduled job to start the effected services 60 mins after scheduled reboot. If they're down, they start now, if they're up it doesnt matter.
2) Changed service recovery to restart so if they do stop it will recover.

This seems to work ok. Not a great solution admitedly but Im not in a position to spend too long changing things on the live exchange server.
0
 

Author Closing Comment

by:paul williams
ID: 40600341
This is one way to get it working - worked for me
0

Featured Post

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.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
This video discusses moving either the default database or any database to a new volume.

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question