Periodically On Access Scanner turns itself (?) off. Is there some way to force it to restart other than rebooting?
This thread was automatically locked due to age.
Periodically On Access Scanner turns itself (?) off. Is there some way to force it to restart other than rebooting?
miked4680 wrote:I'm having the same issue. Can update, can't turn on-access scanning on.
Here's what happens when I try.
1. Open Preferences, go to On-access Scanning, authenticate, Click Restore Defaults.
2. Click Yes to "Are you sure that you want to set the on-access scanning preferences to defaults?"
3. Error message: "On-access Scanner failed to set preference. The preferences option specified has not taken effect in the on-access Scanner."
I'm running OS X 10.6.8, Sophos 8.0.14C
Yup. That's exactly what happens.
I too am having the same problem.
Currently I can not find any way to re-activate the access scanner. I am considering re-intallation however from reading other peoples atempts, that seems unlikely to help.
I have however found the exact time in the logs where the situation occured. It seems to have happened alongside an update check/update.
com.sophos.intercheck: espion-f.ide
com.sophos.intercheck: vbdro-ag.ide
com.sophos.intercheck: age-abqa.ide <--- Here it was finishing up a normal scan
com.sophos.intercheck:
com.sophos.intercheck: Info: On-access scanner started at 22:09 on 07 May 2013
com.sophos.intercheck:
com.sophos.autoupdate: Update completed at 22:10:00 07 May 2013
com.sophos.autoupdate: Info: Checked primary server at 22:10 on 07 May 2013
com.sophos.autoupdate: Sophos Anti-Virus was updated
com.sophos.autoupdate:
com.sophos.autoupdate: Updating catalogue information at 23:10:00 07 May 2013
com.sophos.autoupdate: Catalogue updated at 23:10:01 07 May 2013
com.sophos.autoupdate: Download started at 23:10:01 07 May 2013
com.sophos.autoupdate: Download completed at 23:11:41 07 May 2013
com.sophos.autoupdate: Software is up-to-date at 23:12:13 07 May 2013
com.sophos.autoupdate: Info: Checked primary server at 23:12 on 07 May 2013
com.sophos.autoupdate: Sophos Anti-Virus is up to date
com.sophos.autoupdate:
com.sophos.autoupdate: Updating catalogue information at 13:04:01 08 May 2013
com.sophos.autoupdate: Catalogue updated at 13:04:07 08 May 2013
com.sophos.autoupdate: Error: Failed to get remote version at 13:04:07 08 May 2013 <---- First error
com.sophos.autoupdate: Failed to authenticate at 13:04:07 08 May 2013
com.sophos.autoupdate: Error: Could not contact primary server at 13:04 on 08 May 2013<- Something blocking access to home server?
com.sophos.autoupdate: URL is invalid
com.sophos.autoupdate:
com.sophos.autoupdate: Updating catalogue information at 17:18:36 08 May 2013
com.sophos.autoupdate: Catalogue updated at 17:18:38 08 May 2013
com.sophos.autoupdate: Download started at 17:18:38 08 May 2013
com.sophos.autoupdate: Download completed at 17:19:18 08 May 2013
com.sophos.autoupdate: Update started at 17:19:18 08 May 2013
com.sophos.intercheck: Fatal Error: Unable to initialise virus detection engine [0x0010b500] <---- Big problem
com.sophos.intercheck: Sophos Anti-Virus cannot continue
com.sophos.intercheck:
com.sophos.autoupdate: Update completed at 17:20:16 08 May 2013
com.sophos.autoupdate: Info: Checked primary server at 17:20 on 08 May 2013
com.sophos.autoupdate: Sophos Anti-Virus was updated
com.sophos.autoupdate:
com.sophos.intercheck: Fatal Error: Unable to initialise virus detection engine [0x00401480]
com.sophos.intercheck: Sophos Anti-Virus cannot continue
The last two lines are continueously repeated. Clearly something is stopping the virus detection engine.
Update.....was considering removing and reinstalling but, for unknown reasons, scanning is now on. If anyone has any more info about this issue, please post. Makes me question reliability of Sophos. For those tech-savvy enough to understand it (I, unfortunately, do not fall into that category), here's an article I found on Sophos:
The article is months old and even the author acknowledges that many of the issues had been addressed at the time of the writing. I won't comment on the whether or not the issues should have been caught in design, development and testing because that is not really the issue at this point; at this point the only issue is that those issues appear to have been addressed and this current issue does not appear to be related to those issues -- at least on the surface. Also, it is interesting that the individual who reported the vulnerabilities criticised Sophos for the speed at which they responded, yet Microsoft has been far more lax in responding to security issues so I am not sure of the true motivations behind those comments, particularly coming from a Googlite.
Just my 2-cents (now worth 1.25-cents on the open currency market)
Try a fix from bobcook about uninstallin kext on page 4 or 5 of this thread below. It worked for me, but it appears there may be variations on the problem.
Mine has started doing the same; no scanning, and scanning option grayed out. I even deleted the sophos app I had and reinstalled it. I am running OS 10.8.3, and this only started in the last day or so. I get a window popup that sophos scanner is not running, but can't figure out how to restart it. Bug is either in sophos or OS 10.8.3 is my guess.
I very much appreciate the info. My understanding of such things is, to put it mildly, limited. Just knowing that you, as a computer-literate being, have faith in Sophos is very reassuring. I'm beginning to feel like we are completely at the mercy of hackers. At my age (57), the odds of me ever catching up to technology are pretty slim. I depend heavily on people like you who are generous enough to share your knowledge of such mysterious things! So, thank you for your 2 cents
($1.25) worth. To me, it's priceless.
Mine appears to be running ok now after restart. I saw on another similar thread in this forum that after several restarts, was running again. Fortunately mine was on ONE restart. I did, earlier, uninstall the version I had, and installed new one, although was same version.