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

How to Capture a Fiddler Trace for Troubleshooting

Updated

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 issues.

Overview

The process involves five main parts:

  1. Isolating the Migration (For Multi-Server Environments): Ensuring the migration runs on the primary server where Fiddler is active.

  2. Configuring Fiddler: Setting up Fiddler to decrypt and capture the correct traffic.

  3. Configuring CloudM Migrate: Telling the migration tool to route its traffic through Fiddler.

  4. Capturing and Saving: Running the migration to reproduce the issue and saving the trace file.

  5. Reverting Settings: Restoring your original configuration so migrations can run normally.

 

Step 1: For Multi-Server Environments - Isolate the Migration

If you are running more than one secondary server, you must first force the migration to run only on the primary machine where you will be running Fiddler. If you only have one server, you can skip to Step 2.

  1. Open the CloudM Migrate Service Manager from the Windows Start menu on your primary server.

  2. Select the Service tab.

  3. Under the Services section, ensure both Run Primary Service and Run Secondary Service are set to True.

  4. Open the CloudM Migrate web application and navigate to Settings > Remote Connections.

  5. Stop all listed secondary migration services.

This ensures that when you run the migration, all processing happens on the primary server that you are monitoring.

image__20_.png

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. Go to the HTTPS tab.

  4. Tick the checkbox for Decrypt HTTPS Traffic.

  5. Accept all subsequent prompts to trust and install the Fiddler root certificate. This is necessary to decrypt the traffic.

  6. Return to the main Fiddler window. In the bottom-left corner, click the dropdown that says All Processes and change it to Non-Browser. This filters out noise from your web browsers.

Step 3: Configure CloudM Migrate to Use Fiddler

Next, you need to direct CloudM Migrate to send its network traffic through the Fiddler proxy.

  1. In the CloudM Migrate, navigate to your batch configuration 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 port that Fiddler listens on. 127.0.0.1 refers to the local machine.

Step 4: Reproduce the Issue and Save the Trace

  1. With Fiddler still running and all settings configured, run the migration for the user or item that is failing.

  2. Once the issue has been reproduced, go back to the Fiddler window.

  3. Navigate to File > Save > Save All Sessions....

  4. Save the resulting file. It will have a .SAZ extension.

  5. Provide our support team with this .SAZ file as an attachment.

Important: You must also provide the corresponding trace-level migration trace file from CloudM Migrate for the same session. A Fiddler trace without the migration log is not sufficient.

Step 5: Revert CloudM Migrate Settings

After you have successfully captured and saved your trace, you must revert your settings to allow normal operation.

  1. In CloudM Migrate, return to Advanced Settings > Network Settings.

  2. Set the Proxy Type back to Default.

  3. Clear the text from the Address field.

  4. If you disabled secondary services in Step 1, remember to re-enable them.

 

Troubleshooting During Fiddler Capture

Running a migration through a proxy can sometimes cause specific, temporary errors.

  • Issue: Migration to Google Workspace fails with "User does not exist and has not been created".

    • Cause: Fiddler can sometimes interfere with the Google Directory API connection.

    • Solution: Temporarily disable the Check Users setting in your project configuration while capturing the trace.

  • Issue: The migration fails with the error "The ServicePointManager does not support proxies with the https scheme."

    • Cause: You have incorrectly entered https:// in the proxy address field in CloudM Migrate.

    • Solution: Ensure the proxy address begins with http:// (e.g., http://127.0.0.1:8888).

  • Issue: The migration fails on a license check or the "License (Validity)" field is empty.

    • Cause: Fiddler is not running, or its network cache is stale.

    • Solution: First, ensure Fiddler is open and capturing. If it is, go to Tools > Clear WinINET cache in Fiddler and try again.

Was this article helpful?
3 out of 3 found this helpful