PLEASE READ Advisory: Kernel memory issue affecting multiple OS (aka F**CKWIT, KAISER, KPTI, Meltdown & Spectre) for the latest updates.
This article explains how to enable the trace logging feature for the Sophos Management Service.
This logging captures errors and warnings from the core of the Sophos Management Service and Enterprise Console. This trace logging is not just for the management service failing to start but also for a lot of issues that occur inside the console. Some of the more common reasons for enabling management service trace logging are listed below.
Note: The steps below involve the use of the Microsoft tool DebugView to show the output as the trace output is not saved to a file on disk. For more information on DebugView see article 119577.
Known to apply to the following Sophos product(s) and version(s) Enterprise Console
Depending on the issue being investigated the Sophos Management Service may or may not be started. In scenarios where the service is able to start, it is important that the service is restarted (step 2 below) after trace logging is enabled (step 1) in order to activate the trace logging. It is not necessary to stop the service before enabling trace logging, but only to restart the service after the registry key has been added.
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. If you need technical support please post a question to our community. Alternatively for licensed products open a support ticket.