Stopped-extension-dll-exception Mim

[Billi Mayhue]

Sobased on what was recorded, I'm thinking that the cause was the Export "stopped-extension-dll-exception"

I've read this article -us/troubleshoot/azure/active-directory/directory-sync-stop-register#cause for the likely cause..

I verified all of the causes mentioned by myself aside from the network connection issues since there's a different team managing that.

So on the Oct 18 (monday) I issued a Full Sync, to see if that fixes things, but until now it hasn't completed. I checked it's progress by issuing a Delta Sync to see if it would succeed and confirm the Full Sync is completed.

I just wanted to check in and see if you had any other questions or if you were able to resolve this issue? If you have any other questions, please let us know. Thank you for your time and patience throughout this issue.

Could you please confirm version of Azure AD connect ? also do you see Event ID: 6801 with stack trace error similar to below from server application event? if so then create an antivirus exception for __PSScriptPolicyTest*.* files or best approach and recommended way is to upgrade to latest version (1.6.16.0 or 2.0.28.0) of the AAD Connect which must fix the issue.

If non of these match your scenario and don't see Event ID: 6801 with stack trace error then would recommend you to reach out to MS support as this would require active troubleshooting and if you don't have support plan then I can help you with one-time free support.

Some errors (typically involving connection to the data source) happen even before the code gets a chance to run. You should see a stopped-extension-dll-exception, and there will be more information in the Windows Application Event log.

Make use of the Preview function in ILM/MIIS to simulate a synchronization of a selected connector space object. In ILM you can now commit this preview, but for code debugging it is usually more useful to replay the sync as many times as you need to get the code right.

Most blog posts I found regarding a UPA picture error with stopped-extension-dll-exception in FIM had to do with some incorrect PictureURL, mine was fine, and I could browse to it (from a client machine)

3a8082e126