paul williams
asked on
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.
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.
ASKER
Windows 2003 - thats 2008 only isnt it?
Oh, Server 2003. Try the steps in this article then: http://support.microsoft.com/KB/193888
ASKER
Hmmm. Working out the dependencies is the issue then.
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.
You could theoretically create the BootPause key in the registry to delay the startup of all the Exchange services if you wanted.
ASKER
No answer here.
ASKER
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
Accepted answer: 0 points for paul williams's comment #a40590597
for the following reason:
No easy way to do this
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This is one way to get it working - worked for me
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