Support-Info: (SYNC SERVICE): Export Run Profile: Information, Testing, Troubleshooting

NOTE	This is a newer version of an older blog post.  Mainly formatting changes and the move to our current central blog site for support.

APPLIES TO:.

• Microsoft Identity Manager 2016 SP1
• Microsoft Identity Manager 2016
• Forefront Identity Manager 2010 R2 SP1
• Forefront Identity Manager 2010 R2
• Forefront Identity Manager 2010
• Azure AD Connect

PURPOSE

• Provide information on what the export run profile does
• Provide information on how to test the export run profile

EXPORT RUN PROFILE

Here are a few key points that you should know/understand about the Export Run Profile: Export Run Profile is the process of the Synchronization Service Engine writing objects in the Pending Export state to the External Data Source (EDS) Export Run Profile is always a Delta.  We only export changes to an object to help the export be as efficient as possible. If you do not run an Export Run Profile then you should not write to the EDS. NOTE If you witness the Synchronization Service Engine writing to the EDS during a Synchronization, then it is most likely a custom piece of code such as a Metaverse Extension and/or a Management Agent Extension.  This type of custom coding is not recommended as it can cause performance related issues with the Synchronization process. OBJECT STATUS' THAT DEAL WITH THE EXPORT RUN PROFILE Pending Export A synchronized object that is ready to be exported to the target data source Awaiting Export Confirmation An exported object that the synchronization service engine wants/needs to confirm the data it wrote to the external data source. Export Error An error has occurred while exporting the object You can find more information on the Export Run Profile on the Run Profiles in Forefront Identity Manager 2010: https://technet.microsoft.com/en-us/library/jj863247(v=ws.10).aspx . NOTE If you are using Azure AD Connect, Azure AD Sync and/or DirSync these items are more for testing purposes and not meant to be used as on-going production usage.

 

HOW CAN I TEST OR VALIDATE EXPORT DATA PRIOR TO EXECUTING FULL EXPORT?

Exporting to an External Data Source (EDS) using Identity Manager Synchronization Service Engine is where the Synchronization Service Engine can be a stressful run profile if you are not aware of the information that you are exporting.  The following How To articles can provide guidance on how to test the export process and be more aware of the data that you are actually exporting.HOW TO - The how to articles below can provide assistance in testing the export prior to actually exporting. HOW TO: Export using a Threshold: http://social.technet.microsoft.com/wiki/contents/articles/9537.how-to-export-using-a-threshold.aspx HOW TO: Export to a drop file: http://social.technet.microsoft.com/wiki/contents/articles/9534.how-to-export-to-a-drop-file.aspx HOW TO: How to test the exporting of data before it is exported: http://social.technet.microsoft.com/wiki/contents/articles/9538.how-to-how-to-test-the-exporting-of-data-before-it-is-exported.aspx HOW TO: Check for Pending Exports: http://social.technet.microsoft.com/wiki/contents/articles/13357.fim-reference-how-to-check-for-pending-exports.aspx

 

COMMON EXPORT RELATED STATUS'

From time to time, you may encounter a failed Export Run Profile.  Here, are a few of the common failed Export Run Profile Status'. Stopped-Server The first thing to know about stopped-server is that it is not an error.  Stopped-Server is a status that is returned to the Synchronization Service Engine console indicating that there is a possible problem with the run profile that was executed.  Stopped-Server is one of the most re-occurring items that we see in support around mainly export and sometimes imports.  A stopped-server can occur on any management agent (connector).  Stopped-Server can be an indication that there is some sort of communication problem with the backend SQL Server.  In troubleshooting a stopped server, you may test the following and/or review the following: Active Directory Management Agent (Connector): Try refreshing the schema of the connector Application Event Log: In most stopped-server status related issues, the Synchronization Service Engine will dump additional information to the Application Event Log FIM/MIM Service Management Agent: Review the Forefront Identity Manager Event Log Review the Forefront Identity Manager Management Agent Event Log Enable the Forefront Identity Manager Operational Log There is some troubleshooting links documented below in the troubleshooting section. FIM 2010 R2 Troubleshooting: Stopped-Server Error on the FIM Service Management Agent: https://social.technet.microsoft.com/wiki/contents/articles/11331.fim-2010-r2-troubleshooting-stopped-server-error-on-the-fim-service-management-agent.aspx Support-Info: (SYNC SERVICE): stopped-server:  msidmCompositeType or Asynchronous Processing Scenario: https://blogs.msdn.microsoft.com/ms-identity-support/2013/09/30/troubleshooting-stopped-server-msidmcompositetype-or-asynchronous-processing-scenario/ Support-Tip:(SYNC SERVICE): stopped-server: Troubleshooting Event ID: 6311 and 6401: https://blogs.msdn.microsoft.com/ms-identity-support/2012/05/15/fim-troubleshooting-stopped-server-event-id-6311-and-6401/ Troubleshooting FIM: GalSync stopped-server on MA export: https://social.technet.microsoft.com/wiki/contents/articles/15526.troubleshooting-fim-galsync-stopped-server-on-ma-export.aspx   FIM/MIM SERVICE MANAGEMENT AGENT EXPORT ERRORS FIM TROUBLESHOOTING: Failed-Creation-Via-Web-Services: InvalidRepresentationException: ValueViolatesUniquness: http://social.technet.microsoft.com/wiki/contents/articles/17242.fim-troubleshooting-failed-creation-via-web-services-invalidrepresentationexception-valueviolatesuniqueness.aspx Failed-Creation-Via-Web-Services Troubleshooter: http://blogs.msdn.com/b/ms-identity-support/archive/2013/05/11/troubleshooting-failed-creation-via-webservices-troubleshooter.aspx Failed-creation-via-web-services: PermissionDeniedException: http://social.technet.microsoft.com/wiki/contents/articles/7350.fimma-export-permissiondeniedexception.aspx   ADDITIONAL EXPORT ERROR TROUBLESHOOTING BLOGS / WIKI TROUBLESHOOTING: Export of an AD Object Fails after a complete domain rebuild: http://social.technet.microsoft.com/wiki/contents/articles/10449.troubleshooting-export-of-an-ad-object-fails-after-a-complete-domain-rebuild.aspx TROUBLESHOOTING: Troubleshooting Export issues: http://social.technet.microsoft.com/wiki/contents/articles/10394.troubleshooting-troubleshooting-export-issues.aspx GalSync Resource Wiki: Export Errors: http://social.technet.microsoft.com/wiki/contents/articles/1726.global-address-list-synchronization-galsync-resources.aspx#EXPORT_ERRORS (OLDER BLOG): Support-Info: (SYNC SERVICE): How to troubleshoot and test the export process: https://blogs.msdn.microsoft.com/ms-identity-support/wp-admin/post.php?post=1703&action=edit     PERMISSION ISSUE Failed export runs that return a permission-issue export error, in most cases this results to be an issue with permissions on the external data source (EDS).  The account in question will be the management agent account for the management agent that has the failed export.

 

 

ADDITIONAL INFORMATION / RESOURCES

FIM/MIM Support Team Blog: http://blogs.technet.microsoft.com/iamsupport Run Profile Resources Wiki: https://social.technet.microsoft.com/wiki/contents/articles/12529.identity-manager-run-profiles-resource-wiki.aspx Troubleshooting FIM 2010: https://technet.microsoft.com/en-us/library/gg607341(v=ws.10).aspx [INFO-SYNCSERVICE] Export with Exchange Provisioning Enabled: http://blogs.technet.com/b/iamsupport/archive/2016/02/17/info-syncservice-export-with-exchange-provisioning-enabled.aspx [INFO-SYNCSERVICE] Run Profile Optimization: http://blogs.technet.com/b/iamsupport/archive/2015/08/27/info-run-profile-optimization.aspx