Share via

FIM Troubleshooting: stopped-dll-exception troubleshooter document

  • Article

Overview / Purpose / Goal

The purpose of this article is to provide guidance around troubleshooting the stopped-dll-exception status that you may receive when exporting to an Active Directory with Exchange 2007 or Exchange 2010. 

The stopped-dll-exception status that you see on the Operations Tab in the Synchronization Server console does not provide very much help as to what is actually happening.  Our goal here is to help guide you on how to troubleshoot this issue so that you can better understand why you are receiving the stopped-dll-exception status.

Troubleshooting information

In most cases, when you receive a stopped-dll-exception status, you can go to the Application Event Log on the Synchronization Service machine.  The stopped-dll-exception status will throw events with IDs such as 6801, 6803, 0.  If you review the text inside of these event IDs you will have a better understanding of what is actually happening.

You will discover that the following links will provide the information in most cases to resolve the stopped-dll-exception status that you are receiving. 

*NOTE: You will notice that the articles below were written with a GalSync Solution in mind.  However, the requirements stand true for a normal Active Directory Management Agent solution that contains one of those Exchange servers.

Provisioning to Exchange 2007 Requirements
Provisioning to Exchange 2010 Requirements

Specific Issues with stopped-dll-exception

See also