none
Exporting to AD with Exchange 2010 gives timeout errors RRS feed

  • Question

  • Hi,

    We have a FIM 2010 R2 environment that has been up and running and happy for over a year now.

    A few days ago we started receiving errors when exporting to AD with Exchange 2010. We get an extension-dll-timeout error, sometimes followed by an unexpected-error on the next object. The export run takes three minutes and then stops, leading me to believe this may be related to WsManConnectionInfo timing out perhaps. The event log shows the following error message:

    "There is an error in Exch2010Extension AfterExportEntryToCD() when exporting an object with DN [valid DN here]"

    Type: Microsoft.MetadirectoryServices.TerminateRunException

    Message: PowerShell runspace is not initialized. This can happen when the host process was restarted in the midle of the export run."

    [Note that the misspelling of "midle" is in the error message.]

    There were recently changes to the Exchange servers, so I'm assuming the problem is a setting there, but the Exchange team is convinced their stuff is fine.

    Does WsManConnectionInfo seem like a reasonable culprit? Is there a way to increase the default timeout from three minutes (maybe a registry setting)? Or maybe something else? If anyone has a solution I would appreciate it. Been working on this off and on for a few days and am a bit stumped.

    Thank you!



    • Edited by SamiVV Friday, June 10, 2016 12:24 PM Typos
    Friday, June 10, 2016 12:16 PM

Answers

  • If exchange settings are wrong, this is typical. Check the uri for exchange. Also make sure the three required attributes for exchange provisioning are set corr ctly, homemdb, mailnickname, and exchhomeservername

    Nosh Mernacaj, Identity Management Specialist

    • Marked as answer by SamiVV Tuesday, June 14, 2016 12:50 PM
    Friday, June 10, 2016 1:29 PM

All replies

  • If exchange settings are wrong, this is typical. Check the uri for exchange. Also make sure the three required attributes for exchange provisioning are set corr ctly, homemdb, mailnickname, and exchhomeservername

    Nosh Mernacaj, Identity Management Specialist

    • Marked as answer by SamiVV Tuesday, June 14, 2016 12:50 PM
    Friday, June 10, 2016 1:29 PM
  • Thank you. Turns out the accounts somehow have decommissioned servers set for the homeMDB and msExchServerName attributes. Odd. But you gave me a place to start looking. Thanks!
    • Edited by SamiVV Tuesday, June 14, 2016 12:52 PM
    Tuesday, June 14, 2016 12:52 PM