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

Client machine not showing status on SEC

Hey,

Server: MS Server 2003 32-bit

SEC: v5.0.0.8

Client: v10.0.3

Client OS: Windows 7 Pro 64-bit

I have a client machine that for some reason is not showing a status for the following categories:

Up to date

On-access

Application Control on-access

Data control scanning

Device control scanning

Tamper protection

It is showing status for the following categories:

Firewall

Patch assessment

I can't seem to pinpoint what is causing the issue.

I have had problems with the same client in the past but have somehow been successful in getting the status to show up again. This time around I am unable to get the status to come. I have tried reinstalling the client software with no luck.

I have followed the advice given in this post: No Status for On-access

I know there is communication between the client and the SEC because when I stop the "Sophos Message Router" service on the client machine the status of the client's machine shows offline on the SEC.

Is there anything further that I can do to try and figure out why the status keeps dropping out on this client machine?

Cheers

:24407


This thread was automatically locked due to age.
Parents
  • Hi,

    E SAVXP Adapter: Failed to create instance of SAVXP Component Manager

    is definitely the problem, the adapter can't speak to SAV to find out its state.

    I assume if SAV is working on the client the component manager component is working?  You may want to check the Event log for errors when starting the SAV Service just to check nothing is thrown in there.  You can open the SAV GUI and makes changes to the config locally?

    The component manager is a COM component served up by the componentmanager.dll as hosted by the SAVService, you can check it's installed by running dcomcnfg.  If it exists there, it's odd the ManagementAgentNt.exe process, which is running as system can't create an instance of the object. 

    You mentioned you tried uninstalling and reinstalling SAV first but that didn't help?  This is quite suprising and makes me think some old registry keys relating to the components registration are left behind and are the problem.  

    Maybe running Process Monitor while starting the Sophos Agent service, will show the COM based lookups taking place.  Maybe you could compare this machine with another (running the same version) at that point.

    The other option is to remove everything Sophos from the machine, reboot and traul through HKCR for references to Sophos and delete them.  Once complete attempt a reinstall.

    Tricky one.

    Regards,

    Jak

    :24445
Reply
  • Hi,

    E SAVXP Adapter: Failed to create instance of SAVXP Component Manager

    is definitely the problem, the adapter can't speak to SAV to find out its state.

    I assume if SAV is working on the client the component manager component is working?  You may want to check the Event log for errors when starting the SAV Service just to check nothing is thrown in there.  You can open the SAV GUI and makes changes to the config locally?

    The component manager is a COM component served up by the componentmanager.dll as hosted by the SAVService, you can check it's installed by running dcomcnfg.  If it exists there, it's odd the ManagementAgentNt.exe process, which is running as system can't create an instance of the object. 

    You mentioned you tried uninstalling and reinstalling SAV first but that didn't help?  This is quite suprising and makes me think some old registry keys relating to the components registration are left behind and are the problem.  

    Maybe running Process Monitor while starting the Sophos Agent service, will show the COM based lookups taking place.  Maybe you could compare this machine with another (running the same version) at that point.

    The other option is to remove everything Sophos from the machine, reboot and traul through HKCR for references to Sophos and delete them.  Once complete attempt a reinstall.

    Tricky one.

    Regards,

    Jak

    :24445
Children
No Data