Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    OVPN Client Export installer error

    pfSense Packages
    2
    2
    1111
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K
      kitdavis last edited by

      I have just updated 4 systems from RC3 to the final release of 2.0.    On all of these systems, when I create a Windows Installation executable from the OVPN Client Export package, the resulting exe is corrupt.  I can successfully generate the same package from a system that is still on the release candidate.

      The executables are all the same size but the one generated from the production version only briefly opens a command prompt on an XP system and generates a message: "The version of this file is not compatible with the version of Windows you're running.  Check your compter's system information to see whether you need an x86 (32bit) or x64(64bit) version of the program, and then contact the software publisher." with Windows7.

      1 Reply Last reply Reply Quote 0
      • L
        limecat last edited by

        Apparently this is a recent issue.  There is a fix over here:
        http://forum.pfsense.org/index.php/topic,41180.0.html

        For those who dont feel like reading the thread (Please DO though– and COMMENT so that it gets fixed :D ), or for those from google:
        @gusdvg:

        Ok so I added an error handler to the openvpn-client-export.inc file such that warnings are not printed to the exe. Tried and it works again!

        If you want to try this, edit /usr/local/pkg/openvpn-client-export.inc and add these lines after the require_once lines at the beginning of the file:

        function ignoreError($errno, $errstr) {
          //does nothing...
        }
         
        set_error_handler("ignoreError",E_WARNING);
        

        I guess the problem still remains if you need to add additional options, but I have little time at the moment and this patch will do for now.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post