locked
Exchange Services Not Starting Automatically After Reboot RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Running MSExchange 2K7 on Windows 2008 Server x64
    exchange running on PDC
    added additional DC
    after reboot Exhange Information Store and System Attendant do not start automatically
    they will manually start just fine
    reboot taking too long to start up
    have added to restart on failure on 1,2,3 tries
    have taken automatic updates to download but not install so I do not have reboots overnight
    these seem to be workaround steps but not a solution to the cause....
    any help is greatly appreciated
    Wednesday, August 19, 2009 1:45 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Have you seen : http://support.microsoft.com/kb/940845?
    "Exchange 2007 services cannot start automatically after you install Exchange 2007 on a global catalog server"
    Wednesday, August 19, 2009 2:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you Mr. David
    I have read this article and thus changed the services to restart on failure as listed in one of the workarounds.
    I was actually hoping more for a solution than for a workaround the problem result.
    These symptoms did not occur prior to adding the second DC to the domain.
    Do you know if there is a true solution, or one that someone has tried successfully.
    I have not taken down the server for a reboot since the last incident occured.

    Wednesday, August 19, 2009 8:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Per my knowledge, there’re only workarounds as listed in that KB

    Thursday, August 20, 2009 5:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The best solution I found for this problem was to delay the startup of the Information Store and the System attendant.
    With this setting in services, the exchange program is functional without user intervention in the event of a restart.
    My new question is this:
    as all of these problems occured after adding a second domain controller, and I am specifically bothered by the amount of time it takes the server to start up and shut down, will these issues be resolved by removing the second domain controller and leave the pdc which is on the exchange server as the only DC.

    I am hesitant to change this if there will be no difference, but if the problem arises from turning a single DC domain into a Global Catalog Server will the problem reverse itself if the second dc is demoted to a stand-alone server?

    Thanks for your attention to this matter
    Tom Harrison
    Thursday, September 24, 2009 6:43 PM