none
Unable to expand Exchange Management console 2010

    問題

  • Get "Initialization Failed"

    The following error accourres when retreiving user information  for 'XXX/User':

    Provisioning layer initalization failed: 'The existing cmdlet extension agents configuration is invalid because cmdlet extension agents "Admin Audit Log Agent" and "Admin Audit Log Agent CNF:e4c2f6f9-e5b1-452a-9de0-9056a0af7247" share the same priority "255". Change the priority of one of these agents, and try the operation again. 'It was running the command 'Get-LogonUser'.

    Any ideas how to fix this???

    Thanks.

    2010年12月23日 下午 07:51

解答

  • My guess would be to delete Admin Audit Log Agent CNF:e4c2f6f9-e5b1-452a-9de0-9056a0af7247 since that looks like an orphan object in Active Directory.  I don't know where you would find it, though.  I'd use LDP to search for it.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    • 已標示為解答 Serena Li 2010年12月27日 上午 08:03
    2010年12月23日 下午 08:12

所有回覆

  • My guess would be to delete Admin Audit Log Agent CNF:e4c2f6f9-e5b1-452a-9de0-9056a0af7247 since that looks like an orphan object in Active Directory.  I don't know where you would find it, though.  I'd use LDP to search for it.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    • 已標示為解答 Serena Li 2010年12月27日 上午 08:03
    2010年12月23日 下午 08:12
  • Yeah, I figured it is some sort of orpahned object trying to start at the same time. Just can't figure out how to find it??
    2010年12月23日 下午 08:23
  • Try using ADSI Edit and looking in this container:

    CN=CmdletExtensionAgent Settings,CN=Global Settings,CN=<Your Organization>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=cacheflow,DC=com

    Be advised that you're at your own risk deleting the apparently orphaned object--I can't guarantee that deleting that object is the right thing to do.  To be sure, you should open a support ticket with Microsoft Support, or wait for someone else who knows more than I do to post here.

     


    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    2010年12月23日 下午 08:41
  • deleting that worked....thanks. Now just have to figure how it got there???
    2010年12月23日 下午 09:27
  • I followed your suggestion and verified through ADSI Edit that the object was not listed and rebooted the server and everything seemed to work.  After several days, the same error returned but ADSI Edit does not list the Cmdletextensionagent "Admin Audit Log Aget:CN:..." but does list the real one.  Is there somewhere else that this information might be comming from?  We are in a single server environment with 2 domain controllers.  I have verified that the entry is not listed in either DC.
    2012年2月23日 下午 05:27