This project has moved and is read-only. For the latest updates, please go here.

Troubleshooting MA operation

The SSH MA outputs a detailed log file that contains information on any errors encountered. The log file path is specified on the connectivity page when configuring the MA.
Error messages are clearly identified along with information that can be used for troubleshooting purposes. If any errors occur while processing an object operation, these will be returned to FIM and can be examined in the Synchronization Service client. If an error occurs during a non-object operation, the error will only be found in the log file.


10/09/2013 1:15:12 PM: PerformCSEntryExportAdd: ExportAdd on object 'cn=ylii0001,ou=users' returned: 
10/09/2013 1:15:12 PM: ExecuteSyncCommand: Executing command: /usr/local/bin/sudo /usr/sbin/groupmod -g 418 its
10/09/2013 1:15:12 PM: ExecuteSyncCommand: Command returned exit code 4
10/09/2013 1:15:12 PM: GetExportChangeResultFromException: An unexpected exception occured for csentry attributeChange 43eb48fe-3a19-e311-8dd1-005056b50bb9 with DN cn=its,ou=groups
An exception has occured in GetExportChangeResultFromException
Type: Microsoft.MetadirectoryServices.ExtensibleExtensionException
Message: The command returned an exit code that was not in the list of successful exit codes: 4
Source: Lithnet.SshMA
TargetSite: Void ExecuteSyncCommand(Lithnet.SshMA.OperationResult, Lithnet.SshMA.SyncCommand, Renci.SshNet.SshCommand)

Turning on debug logging

Extra information can be obtained from the log file by turning on debug logging. This is not recommended for production use, as a large amount of information may be logged. This can be achieved by creating the following registry key
Create a new value of type DWORD and assign it the value 16 (decimal).

Last edited Sep 21, 2013 at 6:33 AM by ryannewington, version 5