Table of Contents

  

Overview

This document will provide the steps necessary to work enable FIM Service Management Agent Tracing.

FIM Service Management Agent Tracing is an advanced way of troubleshooting issues concerning the FIM Service Management Agent.

FIM Service Management Agent Tracing is enabled/disabled via the Synchronization Service Engine Configuration File

(%programfiles%\Microsoft Forefront Identity Manager\2010\Synchronization Service\miiserver.exe.config ).

  

Steps to enable tracing

  1. Prior to making any changes to this file, it is very important to make a backup copy of this file. You can do this by very simply copying, and pasting the file in the same directory, or placed into a backup directory.
  2. Once you have made the backup copy of the Synchronization Service Configuration File, then let's edit the Synchronization Service Configuration File.
    1. *NOTE* You can use editors such as Notepad, Visual Studio, or any text file editor.
  3. Set the log file location
    1. In this wiki, we will be using "C:\Logs" as the place to put our log files. By default, "C:\Logs does not exist. If you do not have a "C:\Logs" folder, then please create one at this time.
      1. The FIM Synchronization Service Account must have access to the folder that you are placing the trace files.
  4. In the Synchronization Service Configuration File, look for the </startup> tag. If you have a default Synchronization Service Configuration File, then you will see the <runtime> tag right underneath the </startup> tag.
  5. Insert the below text between the </startup> tag and the <runtime> tag.
<system.diagnostics>
<sources>
<source name="System.ServiceModel" switchValue="Verbose,ActivityTracing"
propagateActivity="true">
<listeners>
<add type="System.Diagnostics.DefaultTraceListener" name="Default">
<filter type="" />
</add>
<add name="ServiceModelTraceListener">
<filter type="" />
</add>
</listeners>
</source>
<source name="System.ServiceModel.MessageLogging" switchValue="Warning, ActivityTracing">
<listeners>
<add type="System.Diagnostics.DefaultTraceListener" name="Default">
<filter type="" />
</add>
<add name="ServiceModelMessageLoggingListener">
<filter type="" />
</add>
</listeners>
</source>
<source name="Microsoft.ResourceManagement" switchValue="Verbose,ActivityTracing">
<listeners>
<add type="System.Diagnostics.DefaultTraceListener" name="Default">
<filter type="" />
</add>
<add name="ServiceModelMessageLoggingListener">
<filter type="" />
</add>
<add name="ServiceModelTraceListener">
<filter type="" />
</add>
<add name="text" />
</listeners>
</source>
</sources>
<sharedListeners>
<add initializeData="C:\logs\miiserver_tracelog.svclog"
type="System.Diagnostics.XmlWriterTraceListener, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
name="ServiceModelTraceListener" traceOutputOptions="LogicalOperationStack, DateTime, Timestamp, ProcessId, ThreadId, Callstack">
<filter type="" />
</add>
<add initializeData="C:\logs\miiserver_messages.svclog"
type="System.Diagnostics.XmlWriterTraceListener, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
name="ServiceModelMessageLoggingListener" traceOutputOptions="LogicalOperationStack, DateTime, Timestamp, ProcessId, ThreadId, Callstack">
<filter type="" />
</add>
<add name="text"
type="System.Diagnostics.TextWriterTraceListener"
initializeData="C:\logs\TextWriterOutput.log" traceOutputOptions="DateTime, ThreadId" />
</sharedListeners>
<trace autoflush="true" />
</system.diagnostics>
  • Save the Synchronization Service Configuration File
  • Stop and Start the FIM Synchronization Service

  

Disable Tracing

If you made the backup copy of the Synchronization Service Configuration File, then you can rename the tracing file to miiserver.exe.config._TracingEnabled. Once you do that, then rename the backup copy back to miiserver.exe.config. If you do this, then you should be able to easily toggle back forth to enable/disable tracing.

Anytime you change the Synchronization Service Configuration File, then you will need to restart the FIM Synchronization Service.

 

Related

 

See Also