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

[Solved]Cannot instal on Windows 2003

Hi All,

 

I have trouble to install Endpoint Server on Windows server 2003, i launch SophosSetup.exe, the setup launch and immediately after the setup stop with the message "failed to download installer"

 

 

I dont have à proxy or Firewall enabled on this server, the other programme or Website works fine (even XXX sites),

 

thanks by advance,

 

Great regards,



This thread was automatically locked due to age.
Parents
  • Hello Pierre-Marie Lombaerts,

    I'm afraid, Server 2003 is no longer a supported Windows platform.

    Christian

  • but my licence for endpoint are valide until 21 Apr. 2019

     

     

    It's only for already installed Server ?

  • Hello Pierre-Marie Lombaerts,

    I see - you have an Extended Support license.
    The Installer log should be in %ProgramData%\Sophos\CloudInstaller\Logs\, this might have some detail.

    Christian

  • Thanks i have the logs file

     

    Started C:\DOCUME~1\COMPUT~1\LOCALS~1\Temp\sfl-14570800\Setup.exe
    2018-05-02T12:28:19.9311591Z INFO : SophosInstall command line: "C:\\DOCUME~1\\COMPUT~1\\LOCALS~1\\Temp\\sfl-14570800\\Setup.exe"
    2018-05-02T12:28:19.9467843Z INFO : Command line: Quiet mode on: 0
    2018-05-02T12:28:19.9467843Z INFO : Command line: Automatic Proxy detection disabled: 0
    2018-05-02T12:28:19.9467843Z INFO : Command line: No feedback mode on: 0
    2018-05-02T12:28:19.9467843Z INFO : Command line: Dump feedback enabled: 0
    2018-05-02T12:28:19.9467843Z INFO : Command line: Bypass competitor removal: 0
    2018-05-02T12:28:19.9467843Z INFO : Command line: Using CRT catalog file path: --
    2018-05-02T12:28:19.9467843Z INFO : Command line: Only register endpoint with Central: 0
    2018-05-02T12:28:19.9467843Z INFO : Command line: Using custom server: --
    2018-05-02T12:28:19.9467843Z INFO : Command line: Using custom stage 2 filename: --
    2018-05-02T12:28:19.9467843Z INFO : Command line: Using cloud user: --
    2018-05-02T12:28:19.9467843Z INFO : Command line: Using cloud group: --
    2018-05-02T12:28:19.9467843Z INFO : Command line: Overriding computer name: --
    2018-05-02T12:28:19.9467843Z INFO : Command line: Overriding computer description: --
    2018-05-02T12:28:19.9467843Z INFO : Command line: Overriding domain name: --
    2018-05-02T12:28:19.9467843Z INFO : Command line: Language will be set to: --
    2018-05-02T12:28:19.9467843Z INFO : Command line: Using message relays: --
    2018-05-02T12:28:19.9467843Z INFO : Command line: Proxy address: --
    2018-05-02T12:28:19.9467843Z INFO : Command line: Proxy user name: --
    2018-05-02T12:28:19.9467843Z INFO : Command line: Using custom customer token: --
    2018-05-02T12:28:19.9467843Z INFO : Command line: Using specified products: --
    2018-05-02T12:28:19.9467843Z INFO : Command line: Using certificates from the MCS app data folder: 0
    2018-05-02T12:28:19.9624095Z INFO : Sending HTTP 'GET' request to: full/central/windows/business/installer/latest.tar.gz
    2018-05-02T12:28:40.9158027Z WARNING : WinHttpGetProxyForUrl returned: 12167
    2018-05-02T12:28:40.9158027Z INFO : Attempting to connect using proxy '' of type 'Empty Proxy'.
    2018-05-02T12:28:40.9158027Z INFO : Set security protocol: 00000080
    2018-05-02T12:28:40.9158027Z INFO : Opening connection to downloads.sophos.com
    2018-05-02T12:28:40.9158027Z INFO : Opened connection to downloads.sophos.com
    2018-05-02T12:28:40.9158027Z INFO : Request content size: 0
    2018-05-02T12:28:41.0095539Z ERROR : WinHttpSendRequest failed with error 2148074278
    2018-05-02T12:28:41.0095539Z INFO : Failed to connect using proxy '' with error: WinHttpSendRequest failed
    2018-05-02T12:28:41.0095539Z INFO : Cleaning up extracted files

  • Hello Pierre-Marie Lombaerts,

    there's one thread that mentions 2148074278 and it suggests a missing Root Certificate as the cause (but it could be some other TLS error). Can't say if it applies and whether the suggested solution is still valid.

    Christian

  • Hi,

    To use the thin installer on 2003 machines you need to make sure that the server has installed patches related to SHA256 support. Otherwise you might be able to use the old installer; i'll send you a PM.

    Stephen

  • i have the same problem with xp

  • Hi Paolo,

    The same requirement for patches applies to XP; i will send you a PM.

    Stephen

  • Hi,

     

    I have the same issue on Windows Server 2003 SP2.

    Can you send me a link to the old installer.

    I've just started to service this client and want to get this server protected as soon as possible.

     

    Many thanks,

     

    Bart

  • Hi Bart,

    I've sent you a PM; did you check that you had the required patches installed?

    Regards,

    Stephen

  • Hi Stephen,

    I have the exact same issue on Windows Server 2003 SP2.

    Can you send me a link to the old installer or tell me what patches are needed to be installed. I have found those 2 patches (WindowsServer2003-KB938397-x86-FRA.exe and WindowsServer2003-KB968730-x86-FRA.exe) but still does not install.

    I have 3 win 2003 servers to protect.

    Many thanks,

    Thierry

Reply
  • Hi Stephen,

    I have the exact same issue on Windows Server 2003 SP2.

    Can you send me a link to the old installer or tell me what patches are needed to be installed. I have found those 2 patches (WindowsServer2003-KB938397-x86-FRA.exe and WindowsServer2003-KB968730-x86-FRA.exe) but still does not install.

    I have 3 win 2003 servers to protect.

    Many thanks,

    Thierry

Children