Logging and troubleshooting

The MA uses extensive tracing throughout the code. You can get at this information in different manners. So, when configuring and creating/testing script, you can use a tool like DebugView to catch tracing information from this MA.

Make sure 'Capture Global Win32' is ticked in the Capture menu of and for a more readable tracelog in DebugView, you should remove the tickmark at "Force Carriage Returns" under Options in DebugView.

Other errors and warnings that are not caught by the MA and the logging mechanics can be found in the Application Event Log on your Synchronization Server.

Also, you can add the listener below to the miiserver.exe.config.xml in the Bin subdirectory of the Synchronization Service installation directory (typically C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin)

<source name="SQL.MA" switchValue="Verbose">
    <remove name='Default' />
    <add name="SQL.MA" type="System.Diagnostics.TextWriterTraceListener"  initializeData="c:\temp\SQL.MA.log" />

Last edited Nov 8, 2015 at 8:36 AM by Granfeldt, version 7