Sophos Cloud installer return codes

  • Artikel-ID: 120449
  • Aktualisiert: 11 Jul 2014

The table below details a number of possible return codes from the Sophos Cloud installer ('SophosInstall.exe').  The return code for an installation can be found at the end of the 'Sophos Endpoint Bootstrap_[Timestamp].txt' log, typically in the user's temp location, i.e. %temp%.

Note: When running the installer interactively, many of the return codes result in the message in article 120448 being displayed at the end of the installation.

Applies to the following Sophos product(s) and version(s)

Sophos Cloud Managed Endpoint

Table of SophosInstall.exe return codes

At the end of the log file, each return code is preceded by the text: 'Installation program finishing with code'. 

Return code Cause and resolution
0 Cause

The Sophos Cloud installer has completed successfully.

What To Do

No action is required, the computer should show correctly in Sophos Cloud.

101 Cause

The Sophos Cloud installer has been cancelled.

What To Do

No action is required, this is expected if the installation was cancelled.

107 Cause

The Sophos Cloud installer has detected other Sophos products that will need to be removed before installation.

What To Do

See article 119726 for more information on which products need to be uninstalled.

112 Cause

The Sophos Cloud installer has been run without administrative rights.

What To Do

SophosInstall.exe requires administrative rights over the computer to install.

120 Cause

The Sophos Cloud installer has failed to install Sophos AutoUpdate.

What To Do

There are various reasons why Sophos AutoUpdate may fail to install.  The MSI log file: '%temp%\Sophos AutoUpdate Install log.txt' should be analysed to find the exact cause for the failure.  

Tip: Searching the MSI log file for the text:

Return value 3

should help you identify a custom action that is failing and provide more details on the failure.  Failing which please supply this log to Sophos Technical Support.

133 Cause

The Sophos Cloud installer has failed to remove an existing directory of Sophos Remote Management System (RMS).

What To Do

See article 119669.

134 Cause

The Sophos Cloud installer has failed to install Sophos Management Communication System (MCS).

What To Do

The MSI installation logs of the MCS package should be checked to identify an issue with the installation.  For example, the log file: 'Sophos MCS Install Log.txt' under %temp% or 'C:\windows\temp\'

Tip: Searching the MSI log file for the text:

Return value 3

should help you identify a custom action that is failing and provide more details on the failure.  Failing which please supply this log to Sophos Technical Support.

136 Cause

The installation has failed to register with Sophos servers within the registration period (5 minutes).

What To Do

There are various reasons why the endpoint may fail to register. E.g.
2014: The server certificate could not be checked.

The 'MCSClient.log' file should be analysed to find the exact cause for the failure.  

Tip: Searching the log file for the text:

ERROR

should help you identify the failure.  In addition to that the MCS server being accessed will also be listed, e.g.: 'https://mcs-amzn-eu-west-1-9af7.upe.p.hmr.sophos.com/sophos/management/ep', for the above example, can the Sophos certificate be obtained from this URL.

Failing which please supply this log to Sophos Technical Support.

141 Cause

AutoUpdate has failed to update.

What To Do

For a high level error message check the Alc.log as viewable via Sophos Endpoint Security and Control by clicking on 'View updating log'.

For a more detailed log regarding the update failure, check the SophosUpdate.log which can be found under the logs directory of Sophos AutoUpdate.

  • Windows 7/8/8.1: 'C:\ProgramData\Sophos\AutoUpdate\Logs\'
  • Windows XP/2003: 'C:\Documents and Settings\All Users\Application Data\Sophos\AutoUpdate\Logs\'

Note: There are various reasons why Sophos AutoUpdate failed to update, these include:

  • No credentials or invalid credentials.
  • Errors downloading files.
  • The installation of one or more products has failed.
142 Cause

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

What To Do

There are a number of reasons for this return code and state, see article 120452 for guidance.

143 Cause

SophosInstall.exe is unable to access dci.sophosupd.com as part of a Internet connectivity check.

What To Do

Ensure that the account SophosInstall.exe is running as can access the URLs referenced in the log file Sophos Endpoint Bootstrap_[TimeStamp].txt.

E.g:  
http://dci.sophosupd.com/
https://mcs-amzn-eu-west-1-9af7.upe.p.hmr.sophos.com/sophos/management/ep

Note: if SophosInstall.exe is run as SYSTEM, in the case of GPO start-up script then ensure that the SYSTEM user has access to the Internet and any proxy information is correct.

144 Cause

A reboot is required to complete the installation.

What To Do

Reboot the computer.




 
Wenn Sie weitere Informationen oder Unterstützung benötigen, wenden Sie sich bitte an den technischen Support.

Artikel bewerten

Ungenügend Hervorragend

Anmerkungen