Some issues happen randomly. In this case, we'll need to keep DebugView running to catch the trace when the issue happens. Follow the instruction here, to minimize the impact on the system when keep dbgview running.
- Turn on Trace Level in the registry on Windows.
- Download Dbgview and unzip it on the PC. (https://docs.microsoft.com/en-us/sysinternals/downloads/debugview)
- Start DebugView 'As Administrator'.
- Under 'Options', uncheck 'Force Carriage Returns'.
- Under 'Options', select 'History Depth...', set to 20000 (20K).
- Under 'Capture', make sure 'Capture Win32' is checked and check 'Capture Global Win32'.
- Under 'File', select 'Log to File...', to write the trace to a file.
- Under 'Options', select 'Hide When Minimized'
- Minimize dbgview. The dbgview icon shows under systray. Can click it to open dbgview windows again.
- Run the daily operation.
- Once you hit the issue, stop DebugView.
- 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://gladinet.zendesk.com/hc/en-us/articles/235742687-Collect-Audit-Trace
- Send the Audit Trace and DebigView log files to Gladinet support, with the exact file/folder name which hits the issue.
- Please also include a detailed description of what operations were done, right before the problem was detected.
Comments
0 comments
Please sign in to leave a comment.