Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 18 replies
  • Subscribers 8 subscribers
  • Views 52716 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

Full Scan will not complete

jshoughton

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
  • 0

    Same problem here, starting with the upgrade to OS X 10.7 Lion:  Sophos Anti-Virus (a non-free version provided by my workplace, but the free version behaved identically) has never completed a scan under Lion, it always stops with the 'Scan cannot be completed' dialog box, and this problem never occurred before Lion.

    About 'Corrupt File' notifications:  There are lots of files that Sophos considers corrupt even though they work perfectly when opened/unarchived/executed/treated-in-whatever-way-suitable-for-that-type-of-file, so I would recommend that you ignore this type of notification unless it is a mainstream file format such as *.pdf or *.html --- presumably Sophos just thinks that it knows what the correct format is (based on the file name and/or other hints), and then it complains if that assumption is wrong.

    As others have noted, there is no problem if 'Scan inside archives and compressed files' is disabled.

    However, I do not think that it is caused by a disk full problem.  It is in fact a PDF related activity that creates the problem, and the problem is in fact a low-level crash, SIGBUS, not just normal termination of the program with a programmer-specified error message.  In all cases that I have logs for, it stops as follows with a SIGBUS error:

    Thread 4 Crashed:

    0   com.sophos.sav.savi           0xc00639c5 analyse_pdf_object + 160

    1   com.sophos.sav.savi           0xc00644bf process_xref_table + 225

    2   com.sophos.sav.savi           0xc0067124 pdfAutomataParse + 5682

    3   com.sophos.sav.savi           0xc008634d SARCpdfInit + 854

    It is possible that the unarchiving process creates ill-formatted PDF documents (otherwise, how come we only see the problem in archives?), but analyse_pdf_object+160 should of course have checked for format errors rather than naively using a bad pointer.

      best regards, Erik

    :1003767
Reply
  • 0

    Same problem here, starting with the upgrade to OS X 10.7 Lion:  Sophos Anti-Virus (a non-free version provided by my workplace, but the free version behaved identically) has never completed a scan under Lion, it always stops with the 'Scan cannot be completed' dialog box, and this problem never occurred before Lion.

    About 'Corrupt File' notifications:  There are lots of files that Sophos considers corrupt even though they work perfectly when opened/unarchived/executed/treated-in-whatever-way-suitable-for-that-type-of-file, so I would recommend that you ignore this type of notification unless it is a mainstream file format such as *.pdf or *.html --- presumably Sophos just thinks that it knows what the correct format is (based on the file name and/or other hints), and then it complains if that assumption is wrong.

    As others have noted, there is no problem if 'Scan inside archives and compressed files' is disabled.

    However, I do not think that it is caused by a disk full problem.  It is in fact a PDF related activity that creates the problem, and the problem is in fact a low-level crash, SIGBUS, not just normal termination of the program with a programmer-specified error message.  In all cases that I have logs for, it stops as follows with a SIGBUS error:

    Thread 4 Crashed:

    0   com.sophos.sav.savi           0xc00639c5 analyse_pdf_object + 160

    1   com.sophos.sav.savi           0xc00644bf process_xref_table + 225

    2   com.sophos.sav.savi           0xc0067124 pdfAutomataParse + 5682

    3   com.sophos.sav.savi           0xc008634d SARCpdfInit + 854

    It is possible that the unarchiving process creates ill-formatted PDF documents (otherwise, how come we only see the problem in archives?), but analyse_pdf_object+160 should of course have checked for format errors rather than naively using a bad pointer.

      best regards, Erik

    :1003767
Children
No Data
Unfiltered HTML