Sometimes an esync issue may require deeper logs than what the Ektron Windows Service provides. In those cases, the Sync Framework Trace logs will be useful for gaining extra information during eSync errors, such as: System.Exception
This is a much higher level of logging so ensure there is sufficient space on the drive before doing this. It will also increase CPU usage on the next sync.
To enable sync framework logging add the below tags just before the </system.diagnostics> tag in the Ektron.ASM.EktronServices40.exe.config on both sides. Also remove the contents of the EktronWindowsService40\logs folder on both sides. After adding the tag, you'll need to restart the Ektron Windows Service to initiate the change. You may want to do this during a slow period as the tracing will increase resource usage.
EWS config location
"C:\Program Files (x86)\Ektron\EktronWindowsService40\Ektron.ASM.EktronServices40.exe.config"
<!-- 0-off, 1-error, 2-warn, 3-info, 4-verbose. -->
<add name="SyncTracer" value="4" />
<add name="TestListener" type="System.Diagnostics.TextWriterTraceListener" initializeData="c:\TraceSampleLevel5.txt"/>
If the EWS doesn't start after adding the above entry…
Remove the added <trace> entry from the EWS config. Above the <switches> tag should be another trace entry that is commented out. Uncomment out that entry and modify it to have the initializeData field go to C:\trace.log. Leave everything else the same. Restart EWS.
Remember to remove the trace after testing as a drive can fill up quickly with that configuration and please send the trace files to the ticket.