Migrating to IntelliTrace Collector for Visual Studio: What Developers Need to Know

Troubleshooting the IntelliTrace Collector for Visual Studio: Common Issues

Overview

This article covers common problems when using the IntelliTrace Collector for Visual Studio and practical steps to diagnose and fix them. Follow the sections below in order: verify environment, collect diagnostic data, fix configuration and permissions, address performance and storage issues, and validate results.

1. Verify prerequisites and environment

• Visual Studio version: Ensure Visual Studio supports the chosen IntelliTrace Collector version. Older VS releases may require older collector builds.
• Collector compatibility: Use the matching IntelliTrace Collector for the targeted .NET runtime (e.g., .NET Framework vs .NET Core/.NET 5+).
• OS and permissions: Collector runs require administrative privileges for system-level collection on machines (especially for .NET Framework IIS/Windows Services). Confirm OS version is supported.

2. Collector fails to start

• Symptoms: No .iTrace/.zip created; collector process not visible.
• Quick checks:
  • Run the collector from an elevated command prompt.
  • Confirm the collector executable path and working directory are correct.
  • Check that required runtime frameworks (e.g., .NET Framework, .NET runtime) are installed.
• Logs: Inspect collector log files (collector diagnostics/log*.txt). Look for exceptions or “failed to initialize” messages.
• Common fixes:
  • Reinstall or repair the collector package.
  • Unblock the downloaded executable (Properties → Unblock) if blocked by Windows SmartScreen.
  • Ensure antivirus or endpoint protection isn’t quarantining the collector.

3. No IntelliTrace events or incomplete traces

• Symptoms: Trace file exists but contains few or no events; missing call stacks or snapshots.
• Causes & fixes:
  • Wrong collection mode: If using “Events Only” you’ll miss snapshots and call stacks. Use “Events and Call Stacks” or “Debugging and Performance” modes depending on needs.
  • Sampling configuration: High sampling interval reduces captured events. Lower the sampling interval or disable aggressive sampling.
  • Target process not instrumented: Attach collector to the correct process ID or start the target under the collector.
  • 64-bit vs 32-bit mismatch: Use the correct collector bitness to match the target process.
  • Symbol issues: Missing or misconfigured symbols limit call stack resolution. Ensure symbol paths include Microsoft symbol servers and your private symbol server if applicable.

4. Collector crashes or throws exceptions during collection

• Symptoms: Collector process exits with error; trace incomplete.
• Diagnosis steps:
  • Review collector log and Windows Event Viewer Application/System logs for crash details.
  • Enable verbose logging for the collector to capture stack traces.
• Fixes:
  • Update collector to latest patch.
  • If crash occurs on specific code paths, try excluding problematic modules or reduce instrumentation scope.
  • Run collector and target under a debugger to capture exception info if safe.

5. Trace file too large or storage issues

• Symptoms: Disk fills up; trace file size unexpectedly large; collection aborted.
• Mitigations:
  • Limit duration and events: Reduce collection duration and switch to a less verbose collection level.
  • Use filters: Configure event/module filters to capture only relevant data.
  • Rotate outputs: Script rotating collections and remove old traces automatically.
  • Compress results: Ensure collector output is compressed (the collector often produces zipped outputs); if not, compress manually.

6. Performance impact on target application

• Symptoms: Target app slowdown, increased latency or throughput drop during collection.
• Actions:
  • Use lighter-weight collection modes (events-only or sampling).
  • Collect for shorter periods and only during reproductions.
  • Offload heavy tracing to a staging environment when possible.
  • Monitor CPU, memory, and I/O during collection to identify bottlenecks.

7. Problems opening .iTrace or trace import errors in Visual Studio

• Symptoms: Visual Studio fails to open the trace or shows import/parsing errors.
• Checks & fixes:
  • Confirm Visual Studio version supports the trace format produced by the collector.
  • Ensure the trace file is fully written and not corrupted (compare file size to expected; re-run collection if partial).
  • Install required Visual Studio components (Diagnostic Tools, IntelliTrace feature).
  • If symbols are missing, configure symbol servers in Visual Studio and re-open the trace.

8. Networked/remote collection issues

• Symptoms: Remote collection fails; collector cannot reach symbol servers or upload results.
• Troubleshooting:
  • Verify network connectivity and proxy settings for the collector host.
  • Ensure TLS/proxy settings allow access to Microsoft symbol servers or other configured servers.
  • For remote attachment, confirm firewall rules and remote debugging ports are open.
  • Use local symbol cache to avoid repeated remote fetches.

9. Security and permissions-related failures

• Symptoms: Access denied errors when attaching or collecting from protected processes.
• Resolution:
  • Run collector with administrative privileges.
  • For IIS: ensure application pool identity and collector permissions allow instrumentation.
  • On Windows with UAC: disable UAC prompts or run an elevated session for unattended runs.

10. When to collect additional diagnostic data and escalate

• Collect: verbose collector logs, Windows Event Viewer entries, process dumps of collector and target, environment details (OS, VS version, collector version), sample trace files.
• Escalate to: internal platform/diagnostics team or Microsoft support when logs show internal collector errors, crashes, or data corruption you cannot resolve.

Quick troubleshooting checklist

1. Run elevated and verify bitness match.
2. Check logs (collector log, Event Viewer).
3. Confirm collection mode and sampling settings.
4. Validate symbols and symbol paths.
5. Reduce scope to isolate offending modules.
6. Update/reinstall the collector and Visual Studio components.
7. Capture dumps and escalate if collector crashes.

Conclusion

Most IntelliTrace Collector issues stem from mismatched configurations (bitness, collection mode), missing symbols, or permission and environment constraints. Use the checklist and targeted fixes above to resolve common problems quickly; collect verbose logs and dumps when escalating.

If you want, I can produce a short diagnostic script (PowerShell) to gather logs and environment info for troubleshooting.