When I run AD MA Export, I get stopped-server error. There are few errors in the event viewer: 1. Application Error Faulting application name: miiserver.exe, version: 4.0.2592.0, time stamp: 0x4b6790ea Faulting module name: KERNELBASE.dll, version: 6.1.7601.17514, time stamp: 0x4ce7c78c Exception code: 0xe0434f4d ... 2. FIMSynchronizationService The extensible extension returned an unsupported error. The stack trace is: "Microsoft.MetadirectoryServices.ExtensionException: Thread was being aborted. at Exch2010Extension.Exch2010ExtensionClass.BeginExportToCd(String connectTo, String domain, String server, String user, String password) Forefront Identity Manager 4.0.2592.0" 3. FIMSynchronizationService The description for Event ID 0 from source FIMSynchronizationService cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: There is an error in Exch2010Extension BeginExportToCd() function.Type: System.Threading.ThreadAbortException Message: Thread was being aborted. ... Have anyone experienced this error?

Seems like you've got problems with provisioning to Exchange 2010. Did you had this working before? Or did you just added this? There have been some bugs with prior FIM build. What build is your synchronization service currently?http://setspn.blogspot.com

There is something going wrong with the Exchange 2010 provisioning option which runs a powershell cmdlet as part of every export. If you set the MA to run in it's own process than it will at least stop crashing the whole miiserver process - however you can't do this if you're using password sync to this MA. Next you need to figure out why it is crashing. Are all you users on Exchange 2010? If you have any users not on Exchange 2010 you can have problems with the Exch 2010 provisioning option. Also it is worth testing that you can attach by remote powershell to the CAS server you have nominated in the MA, using the connection account from the MA.http://www.wapshere.com/missmiis

You're running the RTM build (4.0.2592.0). You should deploy the latest and greatest.CraigMartin Edgile, Inc. http://identitytrench.com

You're running the RTM build (4.0.2592.0). You should deploy the latest and greatest.CraigMartin Edgile, Inc. http://identitytrench.com

Hah indeed, the build number was in the error :) Here's an overview with all available builds: FIM 2010 Build Overviewhttp://setspn.blogspot.com

Hah indeed, the build number was in the error :) Here's an overview with all available builds: FIM 2010 Build Overviewhttp://setspn.blogspot.com

4.0.2592.0 is the version I had. I installed 4.0.3531.2 and everything works without errors. Thank you!