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

Full Scan will not complete

I have tried many times to complete a full scan and each time it stops at about a third left to go with the following error:

"Scan cannot be completes.  An error occured running the scan."

I have tried redownloading, removing and reinstalling Sophos, and get the same result.  In case it was an issue with the bootcamp partition I excluded it in a custom scan and the same error still appears.

It is running on an iMac 3.06GHz intel core i3, which has been upgraded from Snow Leopard to Lion.  I had no problems running the full scan prior to upgrading to Lion.  I am running the latest version of Sophos (7.3.2c with threat detection engine 3.22.0), so it should be a Lion compatible version.

Another problem that has developed since the upgrade is the shield icon on the top bar intermitently disappears and the setting to display in status bar needs to be rechecked to enable it again.

Any help with this would be much appreciated as until now I've had no problems at all with this great free tool!

:1003679


This thread was automatically locked due to age.
Parents
  • I have now run the full scan with archive scanning disabled, and it has completed successfully.  However, the problem has only occured after the upgrade to Lion, and as far as I'm aware there are no new archive files that could cause the problem.  Prior to the Lion update the full scan worked fine with archive scanning enabled.  I will try scanning the excel documents seperately to see if there is a particular one that is tripping it up.

    :1003705
Reply
  • I have now run the full scan with archive scanning disabled, and it has completed successfully.  However, the problem has only occured after the upgrade to Lion, and as far as I'm aware there are no new archive files that could cause the problem.  Prior to the Lion update the full scan worked fine with archive scanning enabled.  I will try scanning the excel documents seperately to see if there is a particular one that is tripping it up.

    :1003705
Children
No Data