Troubleshoot Synchronization Errors

Note

Error details are stored with the run history in Operations. You can then view details of a run history to see if and when a change occurs. Run histories in Operations are retained until they are manually cleared by using Clear Runs on the Actions menu. Use caution when clearing runs. Clearing an excessively large number of runs at once can cause Synchronization Service Manager to become unresponsive.

Note

You can use Preview to view steps in the synchronization process leading up to a synchronization error. This can be helpful when you want to diagnose errors or test synchronization prior to running an actual synchronization with the metaverse. For more information, see See Also.

Note

For Retry Errors, Initial occurrence and Error retry count will not appear in Error information in the Object Error Details dialog box.

Note

You can also output error information for the most previous run of a management agent to an XML file. This file can then be viewed in Internet Explorer or used with the Windows Management Instrumentation (WMI) provider. To output to an XML file, in Operations, in Management Agent Operations, click a management agent, then on the Actions menu, click Save to file, and then type a name and location for the file. For more information about using the WMI provider with FIM, see the FIM Developer Reference.