Monitor folder import traffic using Fiddler Classic
In case of an issue with the Azure File/Azure Container import, you can troubleshoot the issue by inspecting the web traffic from Fiddler traces.
Fiddler settings
Configure the following settings in Fiddler Classic.
-
Open Fiddler Classic.
The Get Started page is displayed.
-
Go to
.
The Options dialog box is displayed.
-
On the
HTTPS tab, do the following:
- Select Capture HTTPS CONNECTs.
-
Select Decrypt HTTPS traffic and on the list, select from all processes.
-
Select Ignore server certificate errors (unsafe).
-
On the
Connections tab, do the following:
- Enter port number 8888 in the Fiddler Classiclistens on port box.
-
Select Act as system proxy on startup.
-
Select Monitor all connections.
-
Accept default settings for the rest of the options.
-
On the
Gateway tab, ensure
Use System Proxy (recommended) is selected.
- Click Ok to save the settings.
- On the menu, select .
- Close Fiddler Classic.
-
Press Windows + R to open the Windows Run command.
-
Enter services.msc and click
OK.
The Services screen appears with the list of services running on the system.
- On the services list, right-click Tungsten Message Connector service, and select Stop.
Message Connector settings
Configure the settings in the MC_File.exe.config file.
-
In a text editor, open the MC_File.exe.config file available at the following location:
C:\Program Files (x86)\Tungsten\Import Connector\MC\bin
-
Uncomment the lines between the following tags in the configuration file:
<system.net>…</system.net>
To uncomment lines, remove <!-- and --> included before and after the tags, respectively.
-
After uncommenting, the configuration lines looks as follows:
<!-- Uncomment this configuration if you want to capture the https traffic with Fiddler --> <system.net> <defaultProxy> <proxy bypassonlocal="false" usesystemdefault="false" proxyaddress="http://127.0.0.1:8888"/> </defaultProxy> </system.net>
- Save the changes and close the file.
- Restart theTungsten Message Connector service from Windows Services.
- Open Message Connector Monitor and wait for the passive inputs to appear.
-
Open Fiddler Classic.
You should be able to see the traffic between MC and the Azure File/Azure Container storage.