Logging

MRE 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 (http://technet.microsoft.com/en-us/sysinternals/bb896647) to catch tracing information from MRE.

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

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

DEPRECATED FUNCTIONALITY

You can also redirect logging information to a file. Create and specify the following registry key to set the file name for debugging information.

Registry Hive: HKEY_LOCAL_MACHINE\SOFTWARE\Granfeldt\FIM\MRE

• Key name: DebugLogFilename (REG_SZ)
• Value: , i.e. C:\Temp\FIM.MRE-{0:ddd}.log

Also, you can use date time format string to have multiple log files created, i.e. if you want a new log file to be started every day, you could specify the value of DebugLogFilename as C:\Temp\FIM.MRE-{0:ddd}. For more information of specifying date formats, please refer to this article http://msdn.microsoft.com/en-us/library/8kb3ddd4.aspx. Just make sure that you construct the date time format in a way that is a valid file name. If the registry key is not present, no log file will be created.

Errors that are not caught by MRE and the built-in logging mechanics can be found in the Application Event Log.