This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Installation Failing With Error 142

I am getting an error when attempting to install the endpoint agent about not being able to register with the server. Looking over the log:

12/15/2016,3:24:38 PM,Information,------------------ Beginning installation of Sophos Anti-Virus and AutoUpdate ------------------,
12/15/2016,3:24:38 PM,Information,Setup version 3.3.1.430,
12/15/2016,3:24:38 PM,Information,Command line: c:\users\snix\appdata\local\temp\sophos_bootstrap\setup.exe -server dzr-mcs-amzn-us-west-2-fa88.upe.p.hmr.sophos.com -token ***************** -edxtimestamp 20161215T194606Z,
12/15/2016,3:24:38 PM,Information,Process security set successfully,
12/15/2016,3:24:38 PM,Information,Setup program was run from C:\Users\snix\AppData\Local\Temp\sophos_bootstrap,
12/15/2016,3:24:38 PM,Information,Checking system TMP paths.,
12/15/2016,3:24:38 PM,Information,Checking TMP...,
12/15/2016,3:24:38 PM,Information,Temp path for System found: 'C:\WINDOWS\TEMP'.,
12/15/2016,3:24:38 PM,Information,Tamper protection is not installed,
12/15/2016,3:24:38 PM,Information,Sophos Endpoint Defense is not installed,
12/15/2016,3:24:38 PM,Information,Checking if Sophos Anti-Virus or Sophos AutoUpdate are installed...,
12/15/2016,3:24:38 PM,Information,Sophos AutoUpdate is already installed on your computer.,
12/15/2016,3:24:38 PM,Information,Starting wizard to collect information from user...,
12/15/2016,3:24:40 PM,Information,Checking for internet connectivity...,
12/15/2016,3:24:40 PM,Information,Discovered the automatic proxy 192.168.99.1:8080.,
12/15/2016,3:24:40 PM,Success,Successfully connected to the URL http://dci.sophosupd.com/ through the proxy 192.168.99.1:8080.,
12/15/2016,3:24:40 PM,Information,Checking for internet connectivity...,
12/15/2016,3:24:40 PM,Information,Discovered the automatic proxy 192.168.99.1:8080.,
12/15/2016,3:24:45 PM,Success,Successfully connected to the URL dzr-mcs-amzn-us-west-2-fa88.upe.p.hmr.sophos.com/.../ep through the proxy 192.168.99.1:8080.,
12/15/2016,3:24:51 PM,Information,Starting the install sequence.,
12/15/2016,3:24:51 PM,Information,Checking for local third-party software...,
12/15/2016,3:24:51 PM,Information,Sending data back to Sophos...,
12/15/2016,3:24:51 PM,Information,Discovered the automatic proxy 192.168.99.1:8080.,
12/15/2016,3:24:51 PM,ERROR,Failed to open a WinHttp session. The error code was 87 (The parameter is incorrect.).,
12/15/2016,3:24:51 PM,Success,Successfully connected to the URL d1.sophosupd.com/.../x.xml.,
12/15/2016,3:24:51 PM,Information,Done.,
12/15/2016,3:24:51 PM,Information,Installing MSI...,
12/15/2016,3:24:51 PM,Information,Remove old SAU...,
12/15/2016,3:25:02 PM,Information,Uninstallation of Sophos AutoUpdate returned exitcode: 0,
12/15/2016,3:25:02 PM,Information,SAU uninstalled.,
12/15/2016,3:25:02 PM,Information,Remove old MCS...,
12/15/2016,3:25:08 PM,Information,Uninstallation of Sophos Management Communications System returned exitcode: 0,
12/15/2016,3:25:08 PM,Information,MCS uninstalled.,
12/15/2016,3:25:08 PM,Information,Copying ESCDP.dat...,
12/15/2016,3:25:08 PM,Information,SAV not present, skipping install.,
12/15/2016,3:25:08 PM,Information,Registering SAV with AutoUpdate...,
12/15/2016,3:25:08 PM,Information,Installing MCS...,
12/15/2016,3:25:08 PM,Information,Started installing C:\Users\snix\AppData\Local\Temp\sophos_bootstrap\mcsep\Sophos Management Communications System.msi ...,
12/15/2016,3:25:08 PM,Information,Registering MCS with AutoUpdate...,
12/15/2016,3:25:08 PM,Information,Successfully enabled Endpoint Defense for MCS.,
12/15/2016,3:25:09 PM,Information,Installing sau_xg,
12/15/2016,3:25:09 PM,Information,Started installing autoupdate ...,
12/15/2016,3:25:11 PM,Information,Sucessfully enabled Endpoint Defense for SAU.,
12/15/2016,3:25:11 PM,Information,Register with MCS...,
12/15/2016,3:25:46 PM,ERROR,There was an unexpected problem with the installation of Sophos Endpoint Security and Control. Details: The MCS endpoint was rejected by the server during registration, the token is invalid.,
12/15/2016,3:26:21 PM,Information,Sending EBS feedback to Sophos...,
12/15/2016,3:26:21 PM,Information,Sending data back to Sophos...,
12/15/2016,3:26:21 PM,Information,Discovered the automatic proxy 192.168.99.1:8080.,
12/15/2016,3:26:21 PM,ERROR,Failed to open a WinHttp session. The error code was 87 (The parameter is incorrect.).,
12/15/2016,3:26:21 PM,Success,Successfully connected to the URL d1.sophosupd.com/.../x.xml.,
12/15/2016,3:26:21 PM,Information,------------------ Found errors during installation: 142 ------------------,
12/15/2016,3:26:21 PM,Information,------------------ Installation program finishing with code 142 ------------------,



This thread was automatically locked due to age.
Parents
  • It will not solve the matter himself, but i found an articles in relation with : 

     

    https://community.sophos.com/kb/en-us/120449

     

    142 Cause

    Sophos Management Communication System (MCS) has been unable to register with Sophos Central servers.

    What To Do

    There are a number of reasons for this return code and state, the most common of which include:

    • A non ASCII character in the computer name. E.g. ü.
    • A trailing . (dot) in the FQDN name. For example, the primary DNS suffix of the computer has been updated to include a trailing . (dot).

     

    Hope it help, if not you can always call technical support and request a session. to solve it

           

     http://www.adnstudio95.be
    Adnstudio95.be - Nicolas L.     TEL : 0032/470.34.44.92
Reply
  • It will not solve the matter himself, but i found an articles in relation with : 

     

    https://community.sophos.com/kb/en-us/120449

     

    142 Cause

    Sophos Management Communication System (MCS) has been unable to register with Sophos Central servers.

    What To Do

    There are a number of reasons for this return code and state, the most common of which include:

    • A non ASCII character in the computer name. E.g. ü.
    • A trailing . (dot) in the FQDN name. For example, the primary DNS suffix of the computer has been updated to include a trailing . (dot).

     

    Hope it help, if not you can always call technical support and request a session. to solve it

           

     http://www.adnstudio95.be
    Adnstudio95.be - Nicolas L.     TEL : 0032/470.34.44.92
Children
No Data