Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 1879 views
  • Users 0 members are here
Options
Suggested
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

SOPHOS Enterprise Console

Shariar

Hi,

Can't start the SOPHOS Enterprise Console.

Failed to open connection.
----- [outer exception] -----
   -- error: 0x80040603
   -- facility: Custom (Defined by the interface)

   at class ATL::CComPtr<struct IDispatch> __thiscall bl::CReusingManagementServiceClientBroker::logIn(void)
   at int __cdecl Run(int,enum bl::ConsoleType::Type)
   at int __stdcall wWinMain(struct HINSTANCE__ *,struct HINSTANCE__ *,wchar_t *,int)

Regards,

Shariar

:26245


This thread was automatically locked due to age.
Parents
  • 0

    HI.

    If you look in services (services.msc) is the "Sophos Management Service" started?

    If not, try and start it, if it fails take a look in the application event log, you should see a entry from the management service for that last start attempt, that should help understand the problem, as might: http://www.sophos.com/en-us/support/knowledgebase/111898.aspx in interpreting the message.

    Also, was it working before but you get this following an upgrade?  If so from which version to which?  E.g. SEC 4.7 to SEC 5.1 for example?

    If the above fails and the Sophos Management Service can start, It might also be worth:

    1. Closing down SEC if open.
    2. Stopping the Sophos Management Service.
    3. Stop the SQL Server Service responsible for the instance being used by Sophos.
    4. Start the SQL Server Service
    5. Start the Mnagament service
    6. Start the Console, do you get the same problem?

    Is this a one off or something that comes up everytime?  Also what version of SEEC are you running?

    Hope it's useful.

    Regards,

    Jak

    :26247
Reply
  • 0

    HI.

    If you look in services (services.msc) is the "Sophos Management Service" started?

    If not, try and start it, if it fails take a look in the application event log, you should see a entry from the management service for that last start attempt, that should help understand the problem, as might: http://www.sophos.com/en-us/support/knowledgebase/111898.aspx in interpreting the message.

    Also, was it working before but you get this following an upgrade?  If so from which version to which?  E.g. SEC 4.7 to SEC 5.1 for example?

    If the above fails and the Sophos Management Service can start, It might also be worth:

    1. Closing down SEC if open.
    2. Stopping the Sophos Management Service.
    3. Stop the SQL Server Service responsible for the instance being used by Sophos.
    4. Start the SQL Server Service
    5. Start the Mnagament service
    6. Start the Console, do you get the same problem?

    Is this a one off or something that comes up everytime?  Also what version of SEEC are you running?

    Hope it's useful.

    Regards,

    Jak

    :26247
Children
No Data