Fidler2setup.exe /S fai;les with RC=4444 on machines with .NET 2 Installed!

2 posts, 0 answers
  1. Dennis
    Dennis avatar
    2 posts
    Member since:
    Jul 2014

    Posted 01 Jul 2014 Link to this post

    The latest (and previous versions) of Fidler2setup.exe /S (for Silent) fail to install with Return Code 4444.

    If there is a log I don't know where to find it and as NSIS is used there is no logging command line switch (a good enough reason to switch I'd have thought). A windows installer version would be much better (you could look at my free MAKEMSI tool, for easy command line msi building).

    The required dot net version is installed:

    ASoft .NET Version Detector Report
    Download latest version at http://www.asoft.be

    ==== INFO ====
    Created :2014/07/02 - 08:08:57
    Computer:XD77038345AA0C

    ==== FOLDERS ====
    <32Bit>
    2.0.50727.42
      ->C:\WINNT\Microsoft.NET\Framework\v2.0.50727

    ==== Installed .NET Frameworks ====
    .NET FW 2.0
    ==== END REPORT ====

    Any ideas? Any other ways of installing it? I don't want to manually do it, has to be automated.
  2. Dennis
    Dennis avatar
    2 posts
    Member since:
    Jul 2014

    Posted 02 Jul 2014 in reply to Dennis Link to this post

    Got this reply on the google group:

    >From: "EricLaw" <bayden@gmail.com>
    >Date: 03/07/2014 1:45 am
    >Subject: [Fiddler] - 4717 Re: FIDDLER 2 SETUP (/S for silent mode) not Installing on Workstations with Dot Net 2 (RC=4444)!
    >To: <httpfiddler@googlegroups.com>

    >Fiddler requires .NET2.0 Service Pack 1 (v2.0.50727.1433) or preferably later. 
    > For security and reliability reasons, you should always install the latest service packs.

    Thanks for that response. I have no control over the environment and can't install updates etc to it so I probably won't be able to use fiddler....
     
    The download page "http://www.telerik.com/download/fiddler" doesn't correctly list the requirements, could this be updated?
     
    Does the installer log anywhere? How do I know why it fails?
     
    I did notice that although the installer returns 4444, all the files seem to have been installed....





Back to Top