Error 80040155 'Interface not registered' is displayed when you try to edit a policy

  • Article ID: 23743
  • Updated: 14 Feb 2013

Upon editing a policy within your Sophos console an error occurs stating 'Interface not registered', this can sometimes occur following an upgrade from a previous version.

When you click 'Advanced', an error similar to the following is displayed:

The error as reported by Sophos Control Center:

Failed with the HRESULT: 80040155
The context of the failure is:

1, class ATL::CComPtr __thiscall AL::PolicyData::retrievePolicyFromServer(void), 1, void __thiscall AL::AUConfig::LoadConfiguration(void), __thiscall AL::PNCWizardData::PNCWizardData(bool), __w64 long __thiscall MainFrameMessageHandler::OnProtectNewComputers(unsigned short,unsigned short,struct HWND__ *,int &), int __cdecl Run(unsigned short *,int), 1, int __stdcall wWinMain(struct HINSTANCE__ *,struct HINSTANCE__ *,unsigned short *,int)

The error as reported by Sophos Enterprise Console:

Interface not registered
----- [outer exception] -----
-- error: 0x80040155
-- facility: Custom (Defined by the interface)
at 1
at class ATL::CComPtr __thiscall AL::PolicyData::retrievePolicyFromServer(void)
at bool __thiscall CSavConfigDlg::LoadConfigData(void)
at __w64 long __thiscall CSavConfigDlg::OnInitDialog(unsigned int,__w64 unsigned int,__w64 long,int &)
at void __thiscall PolicyDialogViewer::ShowPolicy(struct ISMT_Policy *,class ATL::CWindow,const class bl::UIPermissions &,unsigned long,const class ProductReleaseData &,const class TranslationService &)
at __w64 long __thiscall CPolicyTreeCtrl::OnEditPolicy(unsigned int,__w64 unsigned int,__w64 long,int &)
at int __cdecl Run(int,class bl::CommandLine,enum bl::ConsoleType::Type)
at int __stdcall wWinMain(struct HINSTANCE__ *,struct HINSTANCE__ *,wchar_t *,int)

First seen in

Sophos Control Center
Enterprise Console 4.0.0

What to do

  1. Open a command prompt and navigate to C:\WINDOWS\SYSTEM32.
  2. Type the command regsvr32 ole32.dll and press return.
  3. Open the Sophos console and attempt to edit the policy as before, you should no longer see the error.

Technical information

The problem refers to the IStream interface (a component of the Windows 2000/XP/2003/Vista operating system) not being registered. To resolve the issue you must re-register ole32.dll, as described in the 'What to do' section above.

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

Rate this article

Very poor Excellent