Guest User!

You are not Sophos Staff.

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

"Could not contact primary server" error for last 2 days

my last sophos update was on Mar 11, 2015 0720 PDT. Sophos 8.0.25C/engine 3.50.1 on mac OS X 10.5.8

found sophos Article ID: 118209, but its instructions for dealing with this error do not match the version I have, which has only the options "update now",  "show auto-update window" (which just shows the error) and a couple of local scanning options

I see that there were a spate of complaints about this error from a year ago, with the advice "it will just clear itself", but in my case, it's been 2 days and another more modern mac on my same lan has no such problem: a mac 10.10.2 running sophos 9.2.4.

I recall something a year ago about sophos ending support for mac 10.5, but since my updates continued until 2 days ago, I figured I had misunderstood.

Can someone clarify for me the situation? Is my 10.5.8 mac still supported by sophos? Should I just wait for it "to clear itslef', or is there something else I should do? (please spare me flip remarks to the effect "update your os"--I do not like the newer OS Xs--10.6 lacks a number of nice built-in functions like dictionary, later ones lack the 2-dim expose' and my 10.10.2 crashes every week, like a pc).  --thanks

:1020375


This thread was automatically locked due to age.
Parents
  • My own Mac OSX.5.8 Core Duo machine running Leopard also started to get the same error report at what must have been the same date. Last year when my other machine running Mountain Lion had problems with sophosAV not updating, I solved it by uninstalling the program and then installing the latest version from Sophos on the web. But when trying it today on the older Leopard machine, I saw the new version says you must have 10.6 Snow Leopard, So I think i'm finally going to be forced to upgrade, which I fear probably means having to replace the CD player as it has had a CD jammed in it for at least a year!

    :1020384
Reply
  • My own Mac OSX.5.8 Core Duo machine running Leopard also started to get the same error report at what must have been the same date. Last year when my other machine running Mountain Lion had problems with sophosAV not updating, I solved it by uninstalling the program and then installing the latest version from Sophos on the web. But when trying it today on the older Leopard machine, I saw the new version says you must have 10.6 Snow Leopard, So I think i'm finally going to be forced to upgrade, which I fear probably means having to replace the CD player as it has had a CD jammed in it for at least a year!

    :1020384
Children
No Data
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?