locked
ILM With FP1 and Exchange 2007 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    We are experiencing problems provisioning Mailboxes with ILM FP1.

     

    When running the export to AD after enabling the Provision Exchange 2007 checkbox, get the error below.

     

    Is there a way to do exchange provisioning by setting the appropriate attributes as we could do in Exchange 2003?

     

    Thanks.

     

     

     

    The extensible extension returned an unsupported error in MIIS.

     The stack trace is:

     

     "System.IO.FileNotFoundException: Could not load file or assembly 'System.Management.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

    File name: 'System.Management.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

       at Exch2007Extension.Exch2007ExtensionClass.BeginExportToCd(String connectTo, String domain, String user, String password)

     

    WRN: Assembly binding logging is turned OFF.

    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.

    Note: There is some performance penalty associated with assembly bind failure logging.

    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

    Microsoft Identity Integration Server 3.3.0118.0"

     

    For more information, see Help and Support Center at

     

    Tuesday, March 4, 2008 9:23 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    As Chris points out, the FileLoad error is related to either PowerShell or Exchange Management Console FP1 not being installed on the ILM server.

    Wednesday, March 5, 2008 7:53 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi GRB,

    Is Powershell installed on the ILM Server? The same attributes and methods are used to create mailboxes for Exchange 2007 mailbox provisioning. When the checkbox is activated, the Exch2007Extension.dll is used to run the proper cmdlets for provisioning to Exchange.

    If the problem persists, what are the attributes you are passing to the ExchangeUtils class?

    Chris

     

    Tuesday, March 4, 2008 10:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    As Chris points out, the FileLoad error is related to either PowerShell or Exchange Management Console FP1 not being installed on the ILM server.

    Wednesday, March 5, 2008 7:53 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    A new error since installing Exchange 2007 SP1 Console and Powershell...

     

    The extensible extension returned an unsupported error in MIIS.

    The stack trace is:

    "Microsoft.MetadirectoryServices.ExtensionException: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.

    at Exch2007Extension.Exch2007ExtensionClass.AfterExportEntryToCd(Byte[] origAnchor, String origDN, String origDeltaEntryXml, Byte[] newAnchor, String newDN, String failedDeltaEntryXml, String errorMessage)

    Microsoft Identity Integration Server 3.3.0118.0"

    For more information, see Help and Support Center at

    Wednesday, March 5, 2008 2:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    What parameters are you using with the ExchangeUtils.CreateMailbox method? Take a look at the formatting of the “homeMDB” value?

    Assuming provisioning of the object into the CS is successful; you can preview the CS object and verify everything looks good before it leaves ILM by looking at the pending exports before you execute the ADMA [export] run profile.

     

    Wednesday, March 5, 2008 3:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Same error to me,

    The extensible extension returned an unsupported error in MIIS.

    The stack trace is:

    "Microsoft.MetadirectoryServices.ExtensionException: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.

    at Exch2007Extension.Exch2007ExtensionClass.AfterExportEntryToCd(Byte[] origAnchor, String origDN, String origDeltaEntryXml, Byte[] newAnchor, String newDN, String failedDeltaEntryXml, String errorMessage)

    Microsoft Identity Integration Server 3.3.0118.0"

    For more information, see Help and Support Center at




    HomeMDB is correct but when ilm try to update recipient is raised that error..
    Any News?

    Thx
    Regards Luka.
    Wednesday, October 15, 2008 12:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    What happens when you run update-recipient manually in powershell on the ILM server?

     

    Carol

     

     

    Wednesday, October 15, 2008 1:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The user become mailbox linked correctly if launch update recipient manually....I can't understand why with ilm fp1 don't work while manually work...(homeMDB is set by Exchange.CreateMailbox()) and even when launching update from powershell i use the same attribute



    Wednesday, October 15, 2008 1:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Before the proviosu error there is this error in event viewer :

     

    Event Type: Error
    Event Source: MIIServer
    Event Category: None
    Event ID: 0
    Date:  15/10/2008
    Time:  15.45.32
    User:  N/A
    Computer: D1ILM
    Description:
    The description for Event ID ( 0 ) in Source ( MIIServer ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event:

    There is an error in Exch2007Extension AfterExportEntryToCd() function when exporting an object with DN CN=ProvaILM11,OU=ILM,...(hidden)...

    Type: Microsoft.Exchange.Configuration.Tasks.ThrowTerminatingErrorException

    Message: Could not find the default Administrative Group 'Exchange Administrative Group (FYDIBOHF23SPDLT)'.

    Stack Trace:    at Microsoft.Exchange.Configuration.Tasks.Task.ThrowTerminatingError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Configuration.Tasks.Task.ProcessUnhandledException(Exception e)
       at Microsoft.Exchange.Configuration.Tasks.Task.BeginProcessing()
       at System.Management.Automation.Cmdlet.DoBeginProcessing()
       at System.Management.Automation.CommandProcessorBase.DoBegin().

     

    Wednesday, October 15, 2008 1:50 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    I believe I have the answer to the cause and problem of the second error about not finding the default administrative group 

    When you follow Craig's solid advice be sure open the Exchange 2007 Shell using RunAs -- RunAs the account used by the AD MA. You can even run the commandlet in Whatif mode and it should reproduce the error.

    The cause of the error as was in my case was the following

    "To run the Update-Recipient cmdlet, the account you use must be delegated the following:

    Exchange Recipient Administrator role" --  http://technet.microsoft.com/en-us/library/bb738148.aspx

    So the Account used by the AD MA must be in the Exchange Recipient Administrator Role (usually this is a global group) being a domain administrator won't help -- Exchange 2007 has a split permissions model.

    David Lundell www.ilmBestPractices.com
    • Proposed as answer by LK10 Thursday, January 29, 2009 10:09 AM
    Thursday, January 1, 2009 12:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes, I discover same thing.

    Ilm user was not in Exchange Recipient Administrator role.

    Thanx.

    Regards.

    Luka.

    Thursday, January 29, 2009 10:08 AM