Sophos Management Service fails to start with error: 0x80040154 - Class not registered

  • Article ID: 117638
  • Rating:
  • 4 customers rated this article 3.0 out of 6
  • Updated: 06 Jan 2015


The Management Service fails to start with the error 0x80040154.

There are many reasons why you may see this error code when trying to start the Management Service. For further details, check the event viewer and look for event ID 8004:  

Error: Runtime error Data: 0x80040154 - Class not registered
Event Type: Error
Event Source: Sophos Management Service
Event Category: (2)
Event ID: 8004
Date: 01/01/2012
Time: 09:00:00
Initialization failed.
Step: Initializing the Spring.NET Application object

In this case the issue occurs when 'Initializing the Spring.NET Application object' though the error code 0x80040154 does not necessarily mean that this is always the case and so the event log should always be checked. 

To confirm the issue further check the Sophos-Management-Services.log located in the following path (dependent on version);

Version OS Path
5.1 2003 C:\Documents and Settings\All Users\Application Data\Sophos\Sophos Endpoint Management\log
  2008 C:\ProgramData\Sophos\Sophos Endpoint Management\log
5.0 2003 C:\Documents and Settings\All Users\Application Data\Sophos\Sophos Endpoint Management\5.0\log
  2008 C:\ProgramData\Sophos\Sophos Endpoint Management\5.0\log
4.7 2003 C:\Documents and Settings\All Users\Application Data\Sophos\Sophos Endpoint Management\4.7\log
  2008 C:\ProgramData\Sophos\Sophos Endpoint Management\4.7\log
4.5 2003  C:\Documents and Settings\All Users\Application Data\Sophos\Sophos Endpoint Management\4.5\log
  2008 C:\ProgramData\Sophos\Sophos Endpoint Management\4.5\log

The following error may be found:

2012-01-01 09:00:00,317 [1] INFO {Sophos.Management.Services.Com.Application..ctor} ==> Sophos.Management.Application Created
2012-01-01 09:00:00,442 [1] ERROR {Sophos.Management.Services.Com.Application..ctor} ==> Caught exception from Spring
System.TypeInitializationException: The type initializer for 'Spring.Context.Support.ContextRegistry' threw an exception. ---> Common.Logging.ConfigurationException: Could not configure Common.Logging from configuration section 'common/logging'. ---> System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.Configuration.ConfigurationErrorsException: Unrecognized configuration section system.serviceModel. (c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\machine.config line 146)
at System.Configuration.ConfigurationSchemaErrors.ThrowIfErrors(Boolean ignoreLocal)
at System.Configuration.BaseConfigurationRecord.ThrowIfParseErrors(ConfigurationSchemaErrors schemaErrors)
at System.Configuration.BaseConfigurationRecord.ThrowIfInitErrors()
at System.Configuration.ClientConfigurationSystem.EnsureInit(String configKey)
--- End of inner exception stack trace ---
at System.Configuration.ConfigurationManager.PrepareConfigSystem()
at System.Configuration.ConfigurationManager.GetSection(String sectionName)
at System.Configuration.ConfigurationSettings.GetConfig(String sectionName)
at Common.Logging.ConfigurationReader.GetSection(String sectionName)
at Common.Logging.LogManager.BuildLoggerFactoryAdapter()
--- End of inner exception stack trace ---
at Common.Logging.LogManager.BuildLoggerFactoryAdapter()
at Common.Logging.LogManager.get_Adapter()
at Common.Logging.LogManager.GetLogger(Type type)
at Spring.Context.Support.ContextRegistry..cctor()
--- End of inner exception stack trace ---
at Spring.Context.Support.ContextRegistry.GetContext()
at Sophos.Management.Services.Com.Application..ctor()

First seen in
Enterprise Console


The cause of this issue is a corrupt .Net Framework installation. 

Please note, the error 0x80040154 does not imply .Net Framework corruptions and if this error is encountered the logs should be checked as described at the beginning of this article.


What To Do

Attempt to repair .Net using the Microsoft .NET Framework Repair Tool which can be found here:

If no repairs can be made then reinstall .Net Framework on the Enterprise Console server. The version required will be dependent on the versions installed (there may be multiple versions installed) and each will require re-installation.

If the version number is not specified in Add and Remove programs (Start | Run | Type: appwiz.cpl | Press Return) you can navigate to the following location:

(Start | Run | Type the following:)


Make a note of which Framework specific folders are present. This should give you an idea of the version that is installed.

To download any required files go to

If you need more information or guidance, then please contact technical support.

Rate this article

Very poor Excellent