How To: Enable Debug Logging for FileSync

Version Affected: All

 

Overview

This article explains how to enable debug-level logging for FileSync and export the logged events to a text file for troubleshooting. FileSync's standard logging level is low and writes only to the Windows Event Log, which is harder to review than a plain text file.

Enable Debug Logging for FileSync

1. On the FileSync server, open D:\MFCApp_Bin\Appliance_Sync\FileSyncService\FileSyncService.exe.config in a text editor.
2. Change the Debug setting's value to True.

3. Restart the SecureAuth FileSync service, then wait about 10 minutes for it to generate log entries.
4. Export the logged events to a text file by running this PowerShell command:

get-eventlog -LogName application -Source FileSyncServiceAllinOne | Select-Object -First 10000 TimeGenerated, Message | Sort-Object TimeGenerated | Export-CSV -Path FileSync.log -NoTypeInformation

5. This creates a file named FileSync.log in the current directory. A separate file with additional detail is also generated in D:\FileSyncLog.
6. Repeat these steps on every remaining FileSync node.
7. When troubleshooting is complete, turn debug logging back off by repeating step 2 with the Debug value set to False, then restart the service again — debug logging can consume a large amount of disk space if left on.

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.