How to enable Debug logging for Filesync

Follow

Version Affected: FileSync v4.0 and higher

Description:  

How to enable debug logging for FileSync and export the logs to a text file.

 

Cause:  

Standard logging levels for FileSync are very low and not particularly useful when troubleshooting an issue.  They also write to the event log which is not as easy to review as a text log.

 

Resolution:  

1.  Enable debug logging for FileSync by opening this file:
D:\MFCApp_Bin\Appliance_Sync\FileSyncService\FileSyncService.exe.config

and changing the Debug setting to True:




2. Restart the SecureAuth FileSync service and wait 10 minutes for some logs to be generated.

3. Run this Powershell command to export the Event Log entries to a text file called FileSync.log:

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

3. That should generate a log file called FileSync.log in the current directory.

4. There will also likely be a separate file now in D:\FileSyncLog which will contain additional information.

5. Repeat for remaining nodes.

6. When troubleshooting is complete turn off Debug logging because it can consume a lot of disk space, by repeating step 1 but setting to False, then restart the service.  

 

 

 

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.

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.