SharePoint 2010 User Profile Sync: stopped-extension-dll-exception

Well, it’s good to see that User Profile Sync can be better in 2010 than it was in 2007.  However, there are definitely some issues still.

The first one, which is something we just noticed was that the User Profile Sync jobs were constantly failing.  Unfortunately, there isn’t really a good way to know without going into the MIISClient program to look at the errors.  Basically, if you think, for whatever reason, profile sync is not working, open up the MIISClient.exe (Program FilesMicrosoft Office Servers14.014.0Synchronization ServiceUIShell) as the farm account and take a look to see if everything is a success.

For us, we were seeing all the MOSS-{guid} jobs failing with the error stopped-extension-dll-exception as you can see below.

Based on the lovely error message, I’m still amazed that I was able to isolate this issue (event logs reported that CA was being accessed via a non-registered name).  However, it turns out it is because of alternate access mappings (AAMs) for the central admin (CA) website.  Normally, SharePoint sets up the AAM for CA as the machine name you first install SharePoint on to.  However, we changed the AAM to be a more friendly name.

When you update the “Public URL for Zone” for the CA website, it does not propagate the change into the MIISClient.  This causes the MIISClient to not correctly access the CA APIs for the user profile sync (or at least I am imagining this is the case).

Fix it with the following steps:

  1. MIISClient.exe as the farm account.
  2. Tools > Management Agents (or click the Management Agents in the bar)
  3. Right-click on the MOSS-{guid} management agent and select Properties
  4. Go to the Configure Connection Information section in the left-hand pane
  5. In the connection information box, change the Connect To URL to be the same URL as listed as the “Public URL for Zone” for your CA in the AAM configuration.
  6. Re-enter the farm account username and password for good measure
  7. Save the configuration
  8. Run a full profile sync from CA


  1. This was a big help. Thanks for posting. I recently went live with a new intranet and at the go live date, changed the AAM and didn’t realize FIM would fail on our ECT profile syncs.

  2. Info for SharePoint 2013: The problem gets fixed by SharePoint itself if you stop and restart the “User Profile Synchronization Service” in “Services on Server”.

  3. Thank you, great info! I recently came across this exact problem and had found another article describing how to check the Configure Connection Information. I had a look and everything appeared to be good. Your extra bit on the AAMs turned out to be our issue.

  4. Solved my problem on Sharepoint 2013 after a day of search and try.

    Thank you.

  5. Thank you! Saved me a ton of time, though I am using SP2013. I also changed the AAM for CentralAdmin and experienced this issue.

    Restarting the User Profile Service after changing the AAM does indeed change the Connect To setting and fixed the issue.

    I wonder if anything else is broken by that AAM change…

Comments are closed.