Problems running fiddler on Windows server core?

6 posts, 0 answers
  1. Mike
    Mike avatar
    1 posts
    Member since:
    Nov 2017

    Posted 06 Nov 2017 Link to this post

    Hello, With recent updates of fiddler it seems as if there are issues running on Windows server core.  (See below for exception from the JIT.)  This hasn't always been the case; I have an installer for an older version that runs just fine.  Is this a known limitation?  any workarounds (besides using an outdated version that I only have access to accidentally)?

    Thanks!

    Mike

     

    See the end of this message for details on invoking 
    just-in-time (JIT) debugging instead of this dialog box.

    ************** Exception Text **************
    System.Runtime.InteropServices.COMException (0x80040154): Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG))
       at System.Windows.Forms.UnsafeNativeMethods.CoCreateInstance(Guid& clsid, Object punkOuter, Int32 context, Guid& iid)
       at System.Windows.Forms.WebBrowserBase.TransitionFromPassiveToLoaded()
       at System.Windows.Forms.WebBrowserBase.TransitionUpTo(AXState state)
       at System.Windows.Forms.WebBrowser.get_AxIWebBrowser2()
       at System.Windows.Forms.WebBrowser.set_AllowWebBrowserDrop(Boolean value)
       at .Š.›–() in C:\JenkinsHome\jobs\FiddlerReleaseBuild\workspace\Fiddler2\Report.cs:line 449
       at .Š..ctor() in C:\JenkinsHome\jobs\FiddlerReleaseBuild\workspace\Fiddler2\Report.cs:line 82
       at Fiddler.frmViewer.š(Object , EventArgs ) in C:\JenkinsHome\jobs\FiddlerReleaseBuild\workspace\Fiddler2\Viewer.cs:line 9741
       at System.Windows.Forms.Form.OnLoad(EventArgs e)
       at System.Windows.Forms.Form.OnCreateControl()
       at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
       at System.Windows.Forms.Control.CreateControl()
       at System.Windows.Forms.Control.WmShowWindow(Message& m)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.Form.WmShowWindow(Message& m)
       at Fiddler.frmViewer.WndProc(Message& m) in C:\JenkinsHome\jobs\FiddlerReleaseBuild\workspace\Fiddler2\Viewer.cs:line 12356
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


    ************** Loaded Assemblies **************
    mscorlib
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2117.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
    ----------------------------------------
    Fiddler
        Assembly Version: 4.6.20173.38786
        Win32 Version: 4.6.20173.38786
        CodeBase: file:///C:/Fiddler/Fiddler.exe
    ----------------------------------------
    System
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
    ----------------------------------------
    System.Core
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2117.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
    ----------------------------------------
    System.Windows.Forms
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2114.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    ----------------------------------------
    System.Drawing
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2053.0 built by: NET47REL1
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    ----------------------------------------
    System.Configuration
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2053.0 built by: NET47REL1
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ----------------------------------------
    System.Xml
        Assembly Version: 4.0.0.0
        Win32 Version: 4.7.2102.0 built by: NET47REL1LAST
        CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
    ----------------------------------------
    Xceed.Zip.v5.4
        Assembly Version: 5.4.13572.13590
        Win32 Version: 5.4.13572.13590
        CodeBase: file:///C:/Fiddler/Xceed.Zip.v5.4.DLL
    ----------------------------------------
    Xceed.Compression.Formats.v5.4
        Assembly Version: 5.4.13572.13590
        Win32 Version: 5.4.13572.13590
        CodeBase: file:///C:/Fiddler/Xceed.Compression.Formats.v5.4.DLL
    ----------------------------------------
    Xceed.FileSystem.v5.4
        Assembly Version: 5.4.13572.13590
        Win32 Version: 5.4.13572.13590
        CodeBase: file:///C:/Fiddler/Xceed.FileSystem.v5.4.DLL
    ----------------------------------------
    Xceed.Compression.v5.4
        Assembly Version: 5.4.13572.13590
        Win32 Version: 5.4.13572.13590
        CodeBase: file:///C:/Fiddler/Xceed.Compression.v5.4.DLL
    ----------------------------------------
    Telerik.Analytics
        Assembly Version: 4.0.104.0
        Win32 Version: 4.0.104
        CodeBase: file:///C:/Fiddler/Telerik.Analytics.DLL
    ----------------------------------------

    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.

    For example:

    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>

    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.

  2. Stefan
    Stefan avatar
    2 posts
    Member since:
    Jul 2018

    Posted 27 Jul in reply to Mike Link to this post

    I also see this problem with the chocolatey package 'fiddler'.

     

    iwr -useb https://chocolatey.org/install.ps1

    choco install -y fiddler

    $env:USERPROFILE\AppData\Local\Programs\Fiddler\Fiddler.exe

     

    It worked fine with fiddler4 5.0.20173.50948

     

  3. Simeon
    Admin
    Simeon avatar
    116 posts

    Posted 03 Aug Link to this post

    Hello Mike,

    It seems that the COMException is thrown when a System.Windows.Forms.WebBrowser control is being set in the Statistics tab of Fiddler. AFAIK, WebBrowser internally is using the COM API of Internet Explorer which is not available for Windows Server Core.

    Could you, please, provide me with the version number of Fiddler which works, so that I could compare what have changed.

    Hello Stefan,

    Could you please, check if v5.0.20173.50948 works when you open the Statistics tab of Fiddler and no sessions are selected in the Session list of Fiddler.

    Regards,
    Simeon
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  4. Stefan
    Stefan avatar
    2 posts
    Member since:
    Jul 2018

    Posted 03 Aug in reply to Simeon Link to this post

    Hello Simeon,

     

    I've downloaded the latest version from your site and tried it in my Vagrant box StefanScherer/windows_2016_docker which is a Server Core edition.

     

    Even at installation time I get an error message, see first screenshot.

     

    After starting Fiddler.exe I see another error. I don't have a chance to enter any GUI/Menus etc.

    I should be very easy for you to replicate the problem using a Windows Server Core VM.

    With Vagrant it is very simple.

     

    vagrant init StefanScherer/windows_2016_docker

    vagrant up

    vagrant rdp

    then in the cmd prompt install you latest Fiddler version.

     

    Thanks,

    Stefan

     

     

     

  5. Simeon
    Admin
    Simeon avatar
    116 posts

    Posted 09 Aug Link to this post

    Hello Stefan,

    Thank you for the advice how to reproduce the problem. It was really easy with Vagrant. Both errors - after the installation and during the Fiddler startup, are due to the fact that IE is missing from Server Core and Fiddler depends on it.

    If you only want to capture some traffic to inspect it, you could use FiddlerCap. It is a lightweight tool build on top of FiddlerCore, which allows you to capture web traffic, save it into Fiddler .saz file and open it in Fiddler for inspection.

    Regards,
    Simeon
    Progress Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  6. ดิว
    ดิว avatar
    1 posts
    Member since:
    Aug 2018

    Posted 17 Aug in reply to Simeon Link to this post

    Thank my friend [url=http://ufa007.com/ufabet][size=1px]ยูฟ่าเบท[/size][/url]:d
Back to Top