Skip to main content
  1. CloudM
  2. Migrate
  3. Errors & Troubleshooting
  4. Logs & Diagnostics

How to Capture a Fiddler Trace for Troubleshooting

Updated

The following information relates to CloudM Migrate Self Hosted only.

This article provides a step-by-step guide on using Fiddler Classic, a third-party debugging tool, to capture HTTPS traffic from CloudM Migrate. Our support team may request this information for in-depth investigation of complex connectivity or API issues.

Overview

The process involves five main stages:

  1. Isolating the Migration: Ensuring the migration runs specifically on the server where Fiddler is active (crucial for multi-server environments).
  2. Configuring Fiddler: Setting up the tool to decrypt and capture secure traffic.
  3. Configuring CloudM Migrate: Routing the migration tool's traffic through the Fiddler proxy.
  4. Capturing and Saving: Reproducing the error and exporting the trace file.
  5. Reverting Settings: Restoring the original configuration to resume normal migrations.

Step 1: Isolate the Migration (Multi-Server Environments Only)

If you are running a multi-server environment with secondary servers, you must force the migration to run on the Primary Server (the machine where you will install Fiddler). If you only have one server, you can skip to Step 2.

  1. On your Primary Server, open the CloudM Migrate Service Manager application from the Windows Start menu.
  2. Select the Service tab.
  3. Under the Services section, ensure both Run Primary Service and Run Secondary Service are set to True.
  4. Next, open the CloudM Migrate Web Application (Browser UI) and navigate to Settings > Remote Connections.
  5. Stop all listed secondary migration services to prevent items from being processed by other machines.

Step 2: Configure Fiddler Classic

  1. Download and install Fiddler Classic from the official Telerik website.
  2. Open Fiddler and navigate to Tools > Options.
  3. Select the HTTPS tab.
  4. Check the box for Decrypt HTTPS Traffic.
  5. Accept all subsequent prompts to trust and install the Fiddler root certificate. This is required to inspect secure traffic.
  6. Return to the main Fiddler window. In the bottom-left corner, click the process filter dropdown (usually defaults to "All Processes") and change it to Non-Browser. This reduces noise from your web browser.

Step 3: Configure CloudM Migrate to Use Fiddler

You must now direct CloudM Migrate to send its network traffic through the Fiddler proxy (localhost).

  1. In CloudM Migrate, navigate to your project configuration.
  2. Go to Configuration > Advanced Settings > Proxy.
  3. Set the Proxy Type to Explicit.
  4. In the Address field, enter: http://127.0.0.1:8888
    • Note: 8888 is the default Fiddler port, and 127.0.0.1 refers to the local machine. Ensure you use http:// and not https://.

Step 4: Reproduce the Issue and Save the Trace

  1. With Fiddler running and the proxy configured, run the migration for the specific user or item that is failing.
  2. Wait for the error to occur/reproduce.
  3. Return to the Fiddler window and navigate to File > Save > Save All Sessions....
  4. Save the file (it will have a .SAZ extension).
  5. Attach this .SAZ file to your support ticket.
Important: A Fiddler trace is not enough on its own. Please also provide the corresponding Trace-Level Migration Log covering the same timeframe.

Step 5: Revert CloudM Migrate Settings

Once the trace is captured, you must revert your settings to allow normal migration operations.

  1. Navigate back to Advanced Settings > Network Settings.
  2. Set Proxy Type back to Default.
  3. Clear the Address field.
  4. Crucial: If you stopped secondary services in Step 1, navigate to Settings > Remote Connections and restart them.

Troubleshooting During Fiddler Capture

Running a migration through a proxy can sometimes trigger specific errors.

  • Issue: Migration fails with "User does not exist and has not been created".
    • Cause: Fiddler can interfere with the Google Directory API connection.
    • Solution: Temporarily disable the Check Users setting in your project configuration while capturing the trace.
  • Issue: Error "The ServicePointManager does not support proxies with the https scheme."
    • Cause: You entered https:// in the proxy address field.
    • Solution: Change the address to http://127.0.0.1:8888.
  • Issue: License check fails or "License (Validity)" is empty.
    • Cause: Fiddler is not running, or the network cache is stale.
    • Solution: Ensure Fiddler is capturing. Then, go to Tools > Clear WinINET cache in Fiddler and retry.
Was this article helpful?
3 out of 3 found this helpful