Capture trace for Random Issue in windows client/server agent

Some issues happen randomly. In this case, we'll need to keep DebugView running to catch the trace when the issue happens. Please follow the instruction here, to minimize the impact on the system when keep dbgview running.

• Enable the trace via registry
  

  1. Save this text in a file named TraceLevel.reg:

  Windows Registry Editor Version 5.00
  
  [HKEY_LOCAL_MACHINE\SOFTWARE\Gladinet]
  "TraceLevel"=dword:00000065
  [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Gladinet]
  "TraceLevel"=dword:00000065

  2. Double click the .reg file created.
  Answer Yes to the User Account Control Warning:
  
  3. Answer Yes to this warning:
  
  Exit the windows client if it is running. Start it again. The registry will enable windows client trace.
  
• Download Dbgview and unzip it on the PC. (https://docs.microsoft.com/en-us/sysinternals/downloads/debugview)
• Start debugview.exe. If the issue is on server agent side, start dbgview as Administrator
  
  • Under Options, uncheck 'Force Carriage Returns'
    
    
    Select 'History Depth...', set to 20000 (20K).
    
    
    Enable 'Hide When Minimized'
    
  • Under 'Capture', make sure 'Capture Win32' is checked. If debugview is running as Administrator,  check 'Capture Global Win32' too.
    
    
    
  • Under 'File', select 'Log to File...'. Choose a local file to write the trace to.
    
    
  • Minimize dbgview. The dbgview icon shows under Systray area. Can click it to open the window again.
    
• Run the daily operation.
• When hit the issue, stop DebugView window. The traces collected are stored in the log file.
• Take a screenshot of the error
• collect C:\Users\<windows login id>\AppData\Local\gteamclient\gsettings.db (for windows client) or C:\ProgramData\gteamclient\gsettings.db (for server agent)
• Collect the latest audit trace. See the instruction here: https://support.triofox.com/hc/en-us/articles/360046218033-How-to-Collect-Audit-Trace-in-Triofox-Windows-Clients
• Send everything collected to support, with exact file/folder name which hits the issue.
• If possible, provide a detailed description of what operations were done, right before the problem was detected.