Troubleshooting

Debug Mode on Windows 10+ / Server 2019+

1. Install CICB.
2. Make sure server.exe and client.exe are not running.
3. Create the configured debug trigger file. The default trigger filename is debug.txt.
4. Place the file in the expected debug-trigger location for your deployment.
5. Launch the components you want to troubleshoot and reproduce the issue.
6. Review the generated debug.log output and provide relevant errors or logs for support review.

IMPORTANT: Use one debug trigger filename consistently in the instructions and deployment process. Do not mix debug.on and debug.txt in the same procedure.

Proxy Issue

Check your system-level and user-level proxy and bypass settings. On Windows, environment inspection through a command prompt can help confirm active proxy-related variables.

Trace Mode on Windows 10+ / Server 2019+

Run Command Prompt as Administrator and use sxstrace.exe when investigating side-by-side or runtime dependency issues.

Example workflow:

sxstrace.exe trace -logfile:"C:\Users\<your-user-name>\Desktop\sxstrace.etl"

Launch the affected CICB component and reproduce the issue, then stop tracing and parse the result:

sxstrace.exe parse -logfile:"C:\Users\<your-user-name>\Desktop\sxstrace.etl" -outfile:"C:\Users\<your-user-name>\Desktop\sxstrace.txt"

Review the parsed trace file for runtime dependency details.