locked
Circular dependency error in Exchange System Attendant service... RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello:

    I have a win2k3 server with SP2 running Exchange 2007 with Sp1. This is a new installation with mailboxes having been migrated from Ex 2000. I tried to create a new user through EMC but the system threw an error "Exchange server on which an address list service is active cannot be found". On further investigation I found that Microsoft Exchange System Attendant service had not started. I have been unable to start it as it throws "Error 1059: Circular service dependency was specified". In other words when I look at the dependencies I see System attendant as one of them. So, obviously it goes into a circular loop. Now, is there a way to remove this System Attendant as one of the dependencies somewhere in the registry? Any help would be appreciated.

    Thanks much!

    Friday, November 14, 2008 3:57 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Never mind...I was able to fix this by changing the dependencies in registry. Here it is:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA DependOnService

    I deleted the entry for System attendant.

    Thanks.

    Friday, November 14, 2008 4:43 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Never mind...I was able to fix this by changing the dependencies in registry. Here it is:

    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA DependOnService

    I deleted the entry for System attendant.

    Thanks.

    Friday, November 14, 2008 4:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    As in my case, we have Exchange 2007 SP3 and SA service always seen to be in running condition on the Mailbox Server in question. This error is experienced in one or two Mailbox servers very often. We used to restart the SA service or reboot the server which instantly used to resolve the issue. But again after couple of months, the error re-surfaces. This is very much annoying. Have already logged a PSS case, but unfortunately MS also couldn't have provided a PERMANENT solution to this issue yet, being over 2 months. God knows the future well... 
    Thursday, March 1, 2012 5:09 PM