Another day – another bug #bugmaster (although a very small one)
If you use Azure AD Connect and manually upgrading to v1.1.649.0 and have a Generic LDAP MA in your configuration, after the upgrade you will get a “no-start-ma” error on Delta / Full Import or an “extension-dll-exception” on an export or when syncs start automatically after the upgrade.
Fix: Easy one – open the MA and click through each config page to refresh the MA manually.
Microsoft has acknowledged the bug and will fix it in the next release.
I am surprised as there aren’t that many MA extensions in AADConnect so how this was missed in their internal testing..