Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 1 subscriber
  • Views 2575 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

Enterprise Console 3.1 Will not start

Syrinx2112

Hi,

Had to revert back to Enterprise Console 3.1 as V4 simply wouldn't work, even after 5 weeks of assistance from support.

EM library appears to be ok and has updated successfully ( I think).

When I try to start the console I get the following error message;

'The procedure entry point ??0CFunctionTrace@trace@@QAA@ABU_GUID@PB_WZZ could not be located in the dynamic link library EmTrace.dll'

Have repaired installation then fully reinstalled but still getting this message.

Any suggestions welcomed.

Thanks

David

:4383


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

    What SEC tells you and what actually happens on the clients can be two different things - as SEC can only display what is reported by the clients. So if they update correctly (check by visiting one of them and viewing the updating log) but can't contact the management server the status is of course stale. Wonder why the icons don't time out but it looks like SEC also can't talk to your clients. As I said - check the Network Connections Report.

    The most important thing - IMO - is the healthy up-to-date client. If EM Library is downloading and deploying - fine. Do the clients download the updates? Yes - fine, then you can concentrate on SEC. No - bad, but what's the reason? Once you have them updating you have at least some time to resolve the issues with SEC. Recently I'd "lost" one of my management servers but fortunately (you could call it foresight) the affected clients had a secondary (working) update location defined. So no need to panic.  

    If it's not a SOPHOS3 database SEC refuses to start up (and connect). The registry value HKLM\SOFTWARE\Sophos\EE\Management System\\DatabaseConnectionMS shows the instance (Source=) and database (Initial Catalog=) used.

    Christian

    Note:

    If the clients are updating correctly I'd try the following: Save the contents of the EMLibInstaller share (just in case) and backup the Certification Manager registry keys and the database. Uninstall all Sophos components, drop the database. Reboot. If necessary restore the registry keys.  Install SEC3.1. Restore the EM Library settings. Question is whether to restore the database - as it's contents might have caused (some of) the problems. 

    :4433
Reply
  • 0

    What SEC tells you and what actually happens on the clients can be two different things - as SEC can only display what is reported by the clients. So if they update correctly (check by visiting one of them and viewing the updating log) but can't contact the management server the status is of course stale. Wonder why the icons don't time out but it looks like SEC also can't talk to your clients. As I said - check the Network Connections Report.

    The most important thing - IMO - is the healthy up-to-date client. If EM Library is downloading and deploying - fine. Do the clients download the updates? Yes - fine, then you can concentrate on SEC. No - bad, but what's the reason? Once you have them updating you have at least some time to resolve the issues with SEC. Recently I'd "lost" one of my management servers but fortunately (you could call it foresight) the affected clients had a secondary (working) update location defined. So no need to panic.  

    If it's not a SOPHOS3 database SEC refuses to start up (and connect). The registry value HKLM\SOFTWARE\Sophos\EE\Management System\\DatabaseConnectionMS shows the instance (Source=) and database (Initial Catalog=) used.

    Christian

    Note:

    If the clients are updating correctly I'd try the following: Save the contents of the EMLibInstaller share (just in case) and backup the Certification Manager registry keys and the database. Uninstall all Sophos components, drop the database. Reboot. If necessary restore the registry keys.  Install SEC3.1. Restore the EM Library settings. Question is whether to restore the database - as it's contents might have caused (some of) the problems. 

    :4433
Children
No Data