Go Premium for a chance to win a PS4. Enter to Win

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

Exchange services sometimes fail to start after server reboot

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
paul williams
Asked:
paul williams
  • 6
  • 4
1 Solution
 
VB ITSCommented:
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
 
paul williamsAuthor Commented:
Windows 2003 - thats 2008 only isnt it?
0
 
VB ITSCommented:
Oh, Server 2003. Try the steps in this article then: http://support.microsoft.com/KB/193888
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
paul williamsAuthor Commented:
Hmmm. Working out the dependencies is the issue then.
0
 
VB ITSCommented:
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
 
paul williamsAuthor Commented:
No answer here.
0
 
paul williamsAuthor Commented:
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
 
VB ITSCommented:
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
 
paul williamsAuthor Commented:
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
 
paul williamsAuthor Commented:
This is one way to get it working - worked for me
0

Featured Post

Independent Software Vendors: 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!

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