Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 26 replies
  • Subscribers 6 subscribers
  • Views 31652 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

On Access Scanner Disabled on Computer Start-UP

oberndorfr

When I start up my MacBook Pro OS X 10.7.4, the Sophos icon is gray.  Sophos opens upon start up (it is a start up item), but the icon is gray because the on-access scanner is not running.

If I go into preferences, the on-access scanner page has the security lock in the unlocked position, and it indicates the on-access scanner is not running, with no option for turning it on.  I do not know how the lock is being authenticated to unlock it, because I am not doing it.

The solution is to turn on my wi-fi and start the update process.  This immediately makes the on-access scanner start running.  Problem is when there are no wi-fi networks handy.  I work in the field quite a bit, so I do not always have wi-fi access.

When I check the console log, i am getting an almost continuous error message in my system log that reads as follows:

SophosAntiVirus: Error in SMTP Client, domain: 12, Code 8.

Something is clearly wrong.

:1009186


This thread was automatically locked due to age.
  • 0

    But however the sophos shield has dissapeared from the desktop

    :1010094
  • 0
    pennbank wrote:

    But however the sophos shield has dissapeared from the desktop

    That's strange; the installer and uninstaller don't touch the desktop -- the user-visible portions are in the menu bar, the dock, and the Applications folder.

    :1010236
  • 0

    I had the same problem. On-access was disabled with no option to turn it back on. Sophos AV would stop running all of a sudden. Scanning would not start. Reinstalling did not fix it. Testing my patience.

    I finally deleetd the Sophos caches and all Sophos prefs, and it started working again. Phew!

    It is disconcerting however, that it reported "one threat found", but the quarantine manager had no data in it. I have not been able to locate that "one threat".

    :1010344
  • 0

    That "one threat" was likely in the browser cache... which is now blown away.

    :1010348
  • 0

    same here, can you elaborate on what exactly you deleted ? where can I find the cahe ?

    :1010360
  • 0

    ok just to share my aproach (Im on a Macbookpro running 10.7.5)

    I used the uninstaller app to uninstall the sophos-mac-home-edition

    then I re-downloaded the newest sophos-mac-home-edition for 10.7.x

    then went to ~/library/preferences/ and deleted everything containing "sophos" in its name

    then went to ~/library/caches/ and deleted everything containing "sophos" in its name

    then I reinstalled the mac-home-edition and everything is now back to normal...

    not the minor reset I was hoping for...  but at least it worked.

    J

    :1010366
  • 0

    The cache I was talking about is your web browser cache (Safari, Firefox, etc) -- you can usually clear those from within the preferences of the individual program.  However, clearing the Sophos plists and caches is exactly what you need to do for this sort of situation -- so well done :)

    Hopefully others will see this thread and also try these recovery steps.

    :1010390
  • 0

    I agree with others. This problem has only occurred in last few days. I shall try uninstalling and then install latest version. But if the automatic update is working, which it seems to be, shouldn't I already have the latest version?

    :1010402
  • 0
    Chris63 wrote:

    I agree with others. This problem has only occurred in last few days. I shall try uninstalling and then install latest version. But if the automatic update is working, which it seems to be, shouldn't I already have the latest version?

    Updates happen approximately every four hours.  If the cache is corrupted or the plists are damaged during that time, the next update and subsequent reload of the software can fail.

    :1010430
  • 0

    I am having a similar problem.  I had been without wifi--came home, and logged onto my wifi network. I got a message that Sophos wasn't running. Started it up--updated it, then looked at preferences--on-access scanning is shut down, but there's no option to start it. I tried "restore defaults," but get a message "On-access Scanner failed to set preference"--so I'm concerned that I'm not properly protected.

    When I look at the scans I see a "fatal" error on start up...

    Any ideas would be greatly appreciated. 

    :1010552